On Wed, 25 Aug 1999, Jim Hague wrote:
> If you've got an internal network, and there are Windows machines on
> that network, you may well find they generate regular NetBIOS packets
> that they try to route onto the 'net. Diald can block these out; AIUI
> pppd can't and so you'll find your line coming up every couple of
> minutes.
I'm not sure that this argument is really persuasive. Those NetBIOS
packets shouldn't leave your local network at all, so you should have
firewall rules that block them, in which case they will not bring up the
link with pppd.
More important for diald are packets that shouldn't bring up the link but
should be passed over the link once it's up. BIND and NTP are two
protocols that I have configured that way. Once the link is up, I want to
sync my network's clocks with the correct time, but I don't think that's
important enough to bring the link up. Similar reasoning applies to the
name resolution service: once the link is up, I want named to have access
to all the information it needs to keep its cache up to date, but when the
link is down that is a low priority for me.
diald gives a finer level of control over when to bring the network up and
down, and it likely also gives finer control over the sequence of events
used to establish the link (routing changes, etc.). It also seems to work
better when IP numbers are assigned dynamicly. I don't know for sure
because I haven't tried pppd demand dialing. Does anyone else know?
Ed
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
