Date: Fri, 13 Jan 2017 10:46:02 +0000 From: Steve O'Hara-Smith <steve@sohara.org> To: freebsd-questions@freebsd.org Subject: Re: tunneling ports Message-ID: <20170113104602.61a37642564629a21f97362c@sohara.org> In-Reply-To: <C163417C-8640-4D45-A54C-002697B84F79@kukulies.org> References: <C163417C-8640-4D45-A54C-002697B84F79@kukulies.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 13 Jan 2017 11:13:07 +0100 Christoph Kukulies <kuku@kukulies.org> wrote: > I don't know if this could be easily achieved, but imagine the situation > that you are in a network and the only ports being allowed for outgoing > traffic into the Internet are ports 80 and 443. Sounds like a tightly controlled work network. > Now you would like to access mailservers in the Internet to read your > Email. Ports 993, 587, 465,25. 22 wiuld be desirable,too. Presumably not to the network admins or owners. > What I have is an outside server into which I could tunnel. > > Is there any piece of software allowing me to divert ports into the > outside server through some kind of server? You could run sshd on port 80 or port 443 on the server and use ssh -D to act as a SOCKS proxy. You could run a VPN on 80 or 443 on the server but you probably don't have permissions to run the client and even if you do you're almost certainly compromising network security and risking getting fired for it. However some companies proxy and re-encode HTTPS traffic on port 443 and block it on port 80 which will prevent a VPN or ssh tunnel from working. The best thing is not to attempt to use the restricted network for private purposes (which is almost certainly not permitted) but instead use your cellphone's data feed. OTOH if you think you should be allowed to do what you intend to do then get permission and access from the network admins. -- Steve O'Hara-Smith <steve@sohara.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170113104602.61a37642564629a21f97362c>