F
Fred Marshall
It appears that IP addresses in the private ranges are routing - which seems
contrary to the rules. Maybe someone can explain how this might be
happening:
I'm working on a LAN (LAN#1) with a private IP address in the range
192.168.x.x.
LAN#1 is connected to the internet through a router with NAT.
I have set up a firewall computer whose "outside" is on LAN #1
and whose "inside" is LAN#2 using 10.0.0.x addresses.
I can ping from LAN#2 to addresses on LAN#1 but I'm not completely sure why.
The firewall computer is running WinProxy. Shouldn't the routing it is
doing prevent
routing private IP addresses?
Even more strange:
If I trace route to 10.0.0.2 from LAN#1 - trying to test routing through the
firewall in the other direction, instead of reaching the internal computer,
I get servers that are outside on the internet with the final IP address
being 10.0.0.2.
How in the heck can this be happening?
I thought such IP addresses would not route.
Not through a Linksys router.
Not through other servers on the internet.
Thanks,
Fred
contrary to the rules. Maybe someone can explain how this might be
happening:
I'm working on a LAN (LAN#1) with a private IP address in the range
192.168.x.x.
LAN#1 is connected to the internet through a router with NAT.
I have set up a firewall computer whose "outside" is on LAN #1
and whose "inside" is LAN#2 using 10.0.0.x addresses.
I can ping from LAN#2 to addresses on LAN#1 but I'm not completely sure why.
The firewall computer is running WinProxy. Shouldn't the routing it is
doing prevent
routing private IP addresses?
Even more strange:
If I trace route to 10.0.0.2 from LAN#1 - trying to test routing through the
firewall in the other direction, instead of reaching the internal computer,
I get servers that are outside on the internet with the final IP address
being 10.0.0.2.
How in the heck can this be happening?
I thought such IP addresses would not route.
Not through a Linksys router.
Not through other servers on the internet.
Thanks,
Fred