Seems like your time outs are going wrong...
Please include ur diald script .....
I have had lot of success with it
Cheers
Jeelani
-----Original Message-----
From: Richard Parry [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, April 30, 1998 12:14 PM
To: [EMAIL PROTECTED]
Subject: DialD Closing Idle Link?
Hi All;
I'm having a bit of a problem with DialD closing down an idle link that is
not idle :)
Well, that's incorrect, but only partially. Let me explain.
I used to use DialD with a masquerading setup, and it worked 100%, and
beautifully. I've recently conned my ISP out of a /29, so I didn't need
masquerading. My LAN is a couple of machines, the diald machine is only
doing that - it's a router, nothing else.
Recompiled the kernel (Debian linux running 2.0.33, standard diald and ppp
packages) for IP Forwarding, Firewalling, etc, set up some ipfwadm
forwarding rules, and Bob's your uncle, it happily brings the link up and
forwards traffic.
Had a small hiccup when I forgot that named -> named transfers were
blocked, but now I allow that - my diald/router machine is just a caching
DNS server, so no problems there.
Now, when the link is up, it leaves it up for a staggering 30 seconds or
so, and then reports that it dropped the idle link.
It doesn't matter if the traffic was web, ftp, ping, whatever, that
initiated the link, it doesn't seem to respect the rules in
standard.filter (the one shipped with the product incidentally, suits me
fine). Now, it _used_ to work with masquerading - but not with a "real"
subnet.
If you keep some constant traffic generating task like ping going, it'll
leave the link up - but about five seconds after the ping has stopped, it
drops the link. So, it'll never drop the link on data in progress, or as
long as there's steady constant traffic, but doesn't seem to follow the
time rules in the filter.
I'm figuring that I've forgotten something small and stupid, but I can't
for the life of me figure out what it is. I've raked the examples and
FAQ, but can't seem to locate help there. Probably a mere configuration
issue, but I'm blowed if I know what's going on. I'm not a diald master
:)
Does anyone know what this could be, or how I could solve it? I'm
currently reading through the mailing list archives, which is slow with
over 2000 messages there, but I'll persevere :) Any help would be
appreciated.
Many thanks
Richard
--
Richard Parry Network Controller/Analyst
National Library of New Zealand [EMAIL PROTECTED]
Phone 64 4 474 3010 Mobile 021 664 655 Fax 64 4 474 3140
-
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]
