[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> 1) I don't have a static IP. Does that actually impact my configuration?
No. I ran masquerade on my system for about a year without any static
IP. I have one now, but, I'm not all that sure that there's a big
advantage. :)
> 2) My LAN is segmented by a switch instead of a hub. Is that going
> to cause a problem?
I doubt that any of your boxes can tell the difference between a switch
and a hub. All that a switch does is incrase performance. :)
> 3) Conceptually, I'm having problems with the idea of setting the linux
> server as the gateway for all LAN machines which are taking advantage
> of IP Masq. Do I need to set up some routing rules for packets which
> are actually being sent to other machines on the LAN, as opposed to
> the ones destined for the internet?
Routes are only needed to determine where traffic should go that is not
destined for a directly-connected net. Your machines already know how
to send directly to each other on the LAN. You only use a route to
teach your machines how to route to other networks, and in this case,
one default route will do the trick, directing foreign traffic through
the masq box.
> How are these routing rules affected by the fact that I have a dynamic
> IP on the internet side?
Your masq box has two IP addresses. One is dynamic, on the ppp0
interface; the other is static, and is the IP you choose for the box on
your local LAN. Your routes from the other boxes are directed to that
static eth0 address, and so the dynamic IP doesn't even matter to them.
They don't have to know or care. :)
In working with network troubleshooting over the years, I've come to
view routes and network addressing as rather simple, but apparently
there are lots of people out there who don't find it all that easy. I
try to help where I can. Hope this message helped, if just a little.
Here's a tip I found out much, much later than I wish I had: When you
have a dynamic IP on your Linux box, put this somewhere in your startup
scripts:
echo 1 > /proc/sys/net/ipv4/ip_dynaddr
This causes sockets bound on your ppp0 interface to re-bind when your IP
address changes on that interface. It won't solve problems for
connections that go down in mid-stream, but it can help connections that
get bound to the wrong address during startup. :)
--
[EMAIL PROTECTED] (Fuzzy Fox) || "Nothing takes the taste out of peanut
sometimes known as David DeSimone || butter quite like unrequited love."
http://www.dallas.net/~fox/ || -- Charlie Brown
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]
