/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! */
On Mon, 19 Jul 1999, Frank Matthews wrote:
| well since the masq box puts it's own IP on packets as they go out I
| don't see why having non-private addresses behind the masq box is a
| problem since they don't go out on the net anyway.
Three reasons:
1) Applications that embed the internal IP addresses anywhere will leak
them, such as applications that make direct connections (IRC, ICQ,
games, etc.) and Web browsers. You can get around this with proxies
and the various ip_masq_* modules, but you may not catch all of them.
2) Say you're using 206.158.123.0/24 internally (one of my blocks). You
will be unable to reach the *real* 206.158.123.0/24 network, because
your Linux IPmasq machine will assume it to be local. It you happened
to choose a network used by a well-known site, you basically lock
yourself out of that well-known site.
3) It's impolite. :)
-James
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
Admin requests can be handled at http://www.indyramp.com/masq-list/
or email to [EMAIL PROTECTED]
PLEASE read the HOWTO and search the archives before posting.
You can start your search at http://www.indyramp.com/masq/
