I'm doing all these things now with Mandrake 6.0 and diald 0.16.5. Nettime
(I think is the name) has an RPM on the RedHat distribution and it works
like a champ.
Bill
----- Original Message -----
From: Jake Colman <[EMAIL PROTECTED]>
To: Edward Doolittle <[EMAIL PROTECTED]>
Cc: Jim Hague <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, August 25, 1999 12:01 PM
Subject: Re: is diald the only/best game in town?
>
> Ed and Jim,
>
> Thanks for the comprehensive replies.
>
> My private network is a home office network with a linux box and two win98
> boxes for the kids. I want the link brought up whenever the kids or I
need
> to access the internet (e.g., www, ftp, irc, AIM, icq). There will be no
> restrictions on that.
>
> As Ed is doing, I'd like to configure the link so that it does NOT come up
> for named or netbios packets or any other kind of routing packet. Once
the
> link is up, I don't mind if my internal DNS server (not running yet) gets
> configured with packet traffic. I also would not mind doing time
> synchronization once the link is established for regular internet access.
>
> Would it make sense, then, to go with diald and forgo pppd's more limited
> control? Also, I'd appreciate a copy of Ed's diald configuration script
> since I think it matches what I am going to try to do.
>
> Thanx!
>
> ...Jake
>
>
> >>>>> "ED" == Edward Doolittle <[EMAIL PROTECTED]> writes:
>
> ED> 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.
>
> ED> I'm not sure that this argument is really persuasive. Those
NetBIOS
> ED> packets shouldn't leave your local network at all, so you should
have
> ED> firewall rules that block them, in which case they will not bring
up
> ED> the link with pppd.
>
> ED> More important for diald are packets that shouldn't bring up the
link
> ED> but should be passed over the link once it's up. BIND and NTP are
> ED> two protocols that I have configured that way. Once the link is
up,
> ED> I want to sync my network's clocks with the correct time, but I
don't
> ED> think that's important enough to bring the link up. Similar
> ED> reasoning applies to the name resolution service: once the link is
> ED> up, I want named to have access to all the information it needs to
> ED> keep its cache up to date, but when the link is down that is a low
> ED> priority for me.
>
> ED> diald gives a finer level of control over when to bring the
network
> ED> up and down, and it likely also gives finer control over the
sequence
> ED> of events used to establish the link (routing changes, etc.). It
> ED> also seems to work better when IP numbers are assigned dynamicly.
I
> ED> don't know for sure because I haven't tried pppd demand dialing.
> ED> Does anyone else know?
>
> ED> Ed
>
>
> ED> - To unsubscribe from this list: send the line "unsubscribe
> ED> linux-diald" in the body of a message to
[EMAIL PROTECTED]
>
> --
> Jake Colman
>
> Principia Partners LLC Phone: (201) 946-0300
> Harborside Financial Center Fax: (201) 946-0320
> 902 Plaza II Beeper: (800) 505-2795
> Jersey City, NJ 07311 E-mail: [EMAIL PROTECTED]
> E-mail: [EMAIL PROTECTED]
> web: http://www.ppllc.com
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
