Hi, Iljitsch,
I'm confused...
From: "Iljitsch van Beijnum" <iljitsch(_at_)muada(_dot_)com>
On 19 feb 2008, at 15:40, Dan York wrote:
Is this important? The external address(es) are still different.
Sure, but the home internal networks are identical. So Homeowner A
calls up the ISP support and is having a problem getting a machine
to work with the wireless router provided by the ISP. So the ISP
tech says "on a working machine, point your browser to 192.168.10.1
and...."
A while later Homeowner B calls in with a similar problem. The ISP
tech says "on a working machine, point your browser to 192.168.10.1
and..." Same with Homeowners C, D, E and so on.
I'm not buying that this is so important that it's worth having a box
rewrite EVERY address in EVERY packet for.
If you really want this, you can simply create a loopback interface
with address fc00::1 on it and users can type "http://[fc00::1]/"; (ok,
so the brackets are annoying, but no NAT helps against that) and the
users can connect to that address regardless of what the addresses
used on the LAN are.
Were you thinking that the loopback interface would be on the "working
machine" Dan mentioned, or the inner interface on the LAN router device (in
my case, 192.168.10.1 would be my wireless router plugged into my cable
modem) that is having connectivity issues on its outer interace?
Because I'm almost sure the second case is what Dan's talking about...
Thanks,
Spencer
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
http://www.ietf.org/mailman/listinfo/ietf