> On Thu, 16 Oct 2003 20:18:45 -0700, "James Newton, webhost" > wrote: > > >Yes, but that doesn't explain why I can't go from 192.168.1.6 to > >66.13.172.18 directly when anyone else outside the local network can. > > Lots of NAT boxes won't let you back in the WAN interface from the LAN > side. The one currently in use here (a Zyxel) behaves that way. To test > web server URLs, I put an entry for the server in the hosts file pointing > to the RFC1918 LAN address of the server. > > There are fairly good technical reasons for not permitting an outgoing > session that connects to an incoming session. FWIW some DO do this sort of thing. The feature is usually called "internal loopback". My DLink DI604 has this feature. I can't really think of a security reason for NOT allowing this sort of thing. TTYL -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email listserv@mitvma.mit.edu with SET PICList DIGEST in the body