[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
Tom Potts wrote: > On Wednesday 03 September 2008 23:49, Grant Sewell wrote: > >> Simon Williams wrote: >> >>> Or use apache's nice proxying feature to port forward based on hostname >>> so that external requests for: >>> ssh.example.com:443 redirects to port 22 >>> mail.example.com:443 redirects to port 25 >>> www.example.com: 443 still works as an https server >>> > One thing to remember is a port is a port is a port. > If some stupid IPS tries to restrict your ports and you have an available > server you can do port 'redirects/tunneling' that one way or another. > ie > on your machine you redirect/tunnel port x to port 80 and go to your server on > port 80 and tell it (http:\\server\redirect.html?port=x&.....) and away you > go. > > Tom te tom te tom > I have had to redirect :443 to :22 on my router - the College only allow outbound traffic on :80 and :443. What I've been wondering for a while, though, is how to redirect traffic based on address... Grant. -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html