[EMAIL PROTECTED] wrote:
Michael Fox wrote:
box with the flip up antenna in the 10.x.x.x range. And then it justCould be also that the 10.x.x.x address is on a network between the PC and the device,
works... So my guess is unwired do nat translation somewhere on the
and the device does simple routing to the outside world. That's what happens also with
some ADSL setups. What's the "default router" and what's the ping time to it?
Routing it and/or sharing it to the other machines on your lan viaI don't see a reason for double-NAT'ing not to work The whole point of NAT (and its
this Linux box might be tricky or not. I don't believe you can do
double NAT, however I am not exactly sure. So don't quote me on that.
elegance, IMHO) is that nobody except the NAT server know that it's a NAT box.
AFAIK double-NAT'ing does actually work. Someone else on this list for some reason which escapes me at the moment had a setup involving double-nat and it worked OK.
RE NAT, what I've been trying to figure out is is it possible to tell if a packet comes from behind a NAT'd interface - and if so what the presumably private IP address is? Skype (www.skype.com - peer-to-peer telephony) seems to do that. It works without ANY (literally) configuring or changing of the NAT'd firewall sitting between the client and the internet. I have personally tried it between two machines both sitting behind NAT firewalls. After both ends registered for a username it simply worked (exceedingly well I might add). The next time we tried it, one or both of the public IP addresses had changed - but made no difference to Skype. I can understand that (a simple registering of the IP address at a server somewhere), but how does it get through a NAT'd firewall to the correct destination client machine on a private IP?
Any ideas/suggestions on how this might work? I am a little concerned.
Fil -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
