Re: Port Forwarding - Firewall Traversal
- From: Scott Baker <bakers@xxxxxxxxxxxx>
- Date: Wed, 07 Jun 2006 14:10:03 -0700
I don't know about THIS situation as I don't know Oracle but port
forwarding HTTP (port 80 or even 443) is TOTALLY ssh port forwarding
friendly. The ONLY problems you might have are DNS, where the server
expects the request to say "www.foo.com" instead of "localhost" but
even that can be hacked with an edit in your hosts file.
I've port forwarded port 80 lots of times with SSH with no problems.
Scott
Pierre Neyron wrote:
It's not working. I can see in the firewall log that it allows theThe HTTP protocol is not ssh port fwding friendly.
first packet to go to the app.server on port 9000 and it drops the
second packet that goes for some reason to the app.server on port 1810.
Am I missing anything?
Thanks,
- - - - - - - - - -
Henry
app.server being a linux (?), I think it may be worth trying to use an
iptables rule instead of ssh fwding (but needs root privileges):
# iptables -t nat -A PREROUTING -s your-work-station -d appserver -p tcp
--dport 9000 -j REDIRECT --to-port 1810
another idea:
on appserver:
# ssh -D 9000 -g appserver
then configure appserver:9000 as a socks proxy server in firefox on your
workstation.
Regards,
Pierre
--
Scott Baker - RHCE
Canby Telcom System Administrator
503.266.8253
- Follow-Ups:
- Re: Port Forwarding - Firewall Traversal
- From: Pierre Neyron
- Re: Port Forwarding - Firewall Traversal
- References:
- Port Forwarding - Firewall Traversal
- From: Henry Kupets
- Re: Port Forwarding - Firewall Traversal
- From: Pierre Neyron
- Port Forwarding - Firewall Traversal
- Prev by Date: Re: how to automate public key authentication when server dual-boots two linuxes
- Next by Date: Re: Port Forwarding - Firewall Traversal
- Previous by thread: Re: Port Forwarding - Firewall Traversal
- Next by thread: Re: Port Forwarding - Firewall Traversal
- Index(es):
Relevant Pages
|