Re: Application-specific networking

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 17Nov2020 09:00, William Oliver <vendor@xxxxxxxxxxxxx> wrote:
>I normally use a VPN that routes through another country.  This works
>fine.  However, a site I often use recently changed its security
>policies and now will only allow connection from networks that claim to
>be based in the US.  So, in order to connect, I either have to turn off
>my VPN or rout it through a US proxy or just my ISP -- which I can do,
>but I resent it a little.

My approach isn't app sepecific, it's domain/website specific.

I run a local proxy (squid in my case) and route everything through it.  
I've got a persistent ssh tunnel to a US VM etc, with a proxy on the VM.

Then I just configure the proxy rules to choose the appropriate upstream 
proxy for special domains (including "DIRECT" - no upstream proxy).

"What a PITA" I hear you say. But I actually drive the rules from a 
simple text file. AN upstream proxy is defined thus:

    UPSTREAM1=host:port

and a rule looks like:

    UPSTREAM *.wikipedia.org *.wikia.com

Obviously, pick memorable proxy nammes. The name "DIRECT" is special in 
my script and turns into "no proxy". Like any ACL, rules apply in the 
order in the file: first match is chosen.

I run squid via my svcd command, which accepts a signature argument - 
when the proxy rule file changes, the squid.conf ACLs get recomputed and 
squid is restarted. So adjusting the rule just means editing the file 
and waiting a few seconds for the restart.

The rule generation is done by my proxy-peerage script, which emits acl 
definitions and cache_peer directives. I patch the squid.conf from that.

My proxy-peerage script is here:

    https://hg.sr.ht/~cameron-simpson/css/browse/bin/proxy-peerage?rev=tip

along with everything else.

Cheers,
Cameron Simpson <cs@xxxxxxxxxx>
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux