Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have my own Linux server at home that I can access using ssh
I pay for web site hosting on a shared host
The web site allows configuration via the web browser
It uses at https connection to port 8443
My work location blocks just about every port, port 8443 is blocked.
What I would like to is use my home Linux server to bounce the traffic to the web site host. Port 80 is not being used for anything on my server and it is not blocked by work.
Would it be possible to create an iptables rule to redirect anything coming into port 80 from the external interface to my web host? Will the fact that it uses https make a difference?
yes, putty can do ssh port forwarding. It can be done either through plink or putty.
You'll have to get the ssh tunnel up before you try and use your firefox portable, but yes... configure the firefox portable proxy settings to the local side of the tunnel to get the traffic to your squid proxy at home.
You can configure firefox to only use the proxy settings for certain domains but once the request gets to the squid proxy, there isn't much choice but for it to handle the request.
Ha ha... it is even easier than I thought, here is how I did it:
Started putty
Loaded the 'home' session
Went to 'Connections -> SSH -> Tunnels'
Entered '8443' in the source port
Entered 'mydomain:8443' as the destination
Saved the putty session
Connected the ssh session
Entered 'https://localhost:8443' in Firefox
Any connection to port 8443 on the local host is tunneled by putty to my home server, this then connects to my web host on port 8443.
I could have used any port number in step 4 but decided to keep it easy to remember. The other good thing is that I do not need to change my proxy settings in Firefox.
Now I just need to figure out how to use this so I can use Pidgin to connect to all the IM networks....
same thing... create (another ??) tunnel to your proxy server and in pidgin, set the (http) proxy settings for the account - or you can change the global network settings to use the http proxy and all accounts will use that.
Hmmmm I tried that, in Putty I have port 8080 tunneled to localhost:3128. I have Pidgin using HTTP proxy 'localhost:8080' but I am getting en error message:
Quote:
Access denied HTTP Proxy server forbids port 5190 tunneling
My squid server has the following in it's conf file:
Quote:
http_port 3128 transparent
....
acl Safe_ports port 5190 # Pidgin
acl Safe_ports port 5222 # Pidgin
acl Safe_ports port 5050 # Pidgin
....
http_access deny !Safe_ports
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.