Getting past *two* NAT routers
JAldrich "at" covista.com
Mon Jan 10 19:45:01 2005
From: PicaRules [mailto:picarules "at" earthlink.net]
Sent: Monday, January 10, 2005 2:23 PM
To: vnc-list "at" realvnc.com
Subject: RE: Getting past *two* NAT routers
The DSL/PPPoE "modem" itself is the one-port NAT "router." It has my account
info (DSL user ID & pw) stored in it, and currently gets the only "real" IP
when it's turned on, regardless of whether any computer is connected. The
Mac [not MAC! that's something else ;-) ] doesn't even know its real IP
when I just have the one machine and no LAN. (Sorry to rehash elementary
concepts, and correct me if I err.)
Yes, I can (and do, actually) manually tell the Mac it has a 192.168.x.x IP,
and turn off the modem's DHCP (from Server to None; can also be Relay, which
I haven't tried). Or did you mean to hard-code it into the modem? Even when
the modem is told to act as a DHCP server and the Mac's DHCP client status
is Automatic, I effectively assign an IP manually because of the modem's
one-user limitation I mentioned.
Still curious what the modem's setting for _bridge_ (is No, can be Yes)
means. Does it by any chance pass the public IP on to the Mac at the other
end of the Ethernet cable? Is it related to Relay in the DHCP mode?
Beyond these questions lie more about the modem. Besides Bridge and Relay I
can toggle Route IP (is On), Route IPX (is Off) and set IP Address
assignment to Static (with address 0.0.0.0) even though my account is
dynamic; set up and assign Ethernet Input and Output Filter Sets and IP
Policies (criteria/action sets)...
something tells me this last item, IP Policies, is the jackpot I've been
chasing, for assigning port 5900!
...and more, even go into a command line interface (and get out of it,
almost a miracle)!
I'm completely in the dark as to how to create an SSH tunnel, but I expect
that's beyond the scope of this discussion. The crystal ball is getting
Hmm... Wierd. What kind of DSL modem do you have? My DSL modem is a
SpeedStream and it connects to a separate router (Netgear DSL/Cable
router/firewall) which in itself is a network switch, and handles all the
DHCP stuff, else I'd be limited to one connection and have to do internet
connection sharing as well as have my systems exposed to the internet 24/7.
As for the SSH Tunnel, it should be similar to the idea expressed by the
Windows ->Linux tunnel since OS/X is essentially a BSD kernel, from what I'm
given to understand. You can look at the FAQ at http://faq.gotomyvnc.com for