Thanks for the link david. It looks like exactly what I need, but I
am
still having trouble getting it to work.
I am using this command:
ssh -l sam -L 1176:me.com:1176 me.com
I am able to authenticate to me.com on the other end no problem, but
when
I try to actually use the port its a no go.
I have tested the Indigo connection over 1176 to me.com from another
ISP
(no internal firewall) and it woks.
any tools I can use to test this further?
the address in the -L option is the target address from the machine
that is the ssh target. In this case, as the 1176 tcp service runs on
that same machine, it must be 127.0.0.1. It could work with me.com,
but if me.com is a public address of a machine behind a NAT, it might
not be possible to connect to it from that same machine! (A neat trick
in these cases is to add an alias on the machine external interface
with an address corresponding to me.com and netmask 255.255.255.255)
Clear as mud? Here is a diagram:
a.b.c.d is the public address of the server, taken by the ADSL router
10.0.0.1 is the internal address of the ADSL router
10.0.0.2 is the address of the natted server
INTERNET ~a.b.c.d|NAT-ADSL-router|10.0.0.1 -----
10.0.0.1/255.255.255.0 | internal
\__ a.b.c.d/
255.255.255.255| server
only the 10.0.0.1/24 has the gateway address set.
Doing so the internal server will be able to connect to itself also
using its own public address.
Giuliano
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
