There is a cron.d entry which sweeps unneeded modules every 10 minutes. This is a long enough time interval to appear 'random' to someone looking at netstat outputs after a connection came down. $ more /etc/cron.d/kmod # rmmod -a is a two-hand sweep module cleaner */10 * * * * root /sbin/rmmod -as $ This sweeper probably causes the 2nd entry below in /var/log/messages: Jan 6 10:22:05 hoho0 PAM_pwdb[6474]: (login) session closed for user user1 Jan 6 10:30:00 hoho0 kernel: PPP: ppp line discipline successfully unregistered Perhaps it is this sweep of the ppp line discipline which is also triggering the disappearance of the routes? Clearly this needs a bit more sleuthing, but perhaps it is a start. FWIW BobG You wroted 06 Jan 2000 23:06:34 +0500 >I am also using ppp-2.3.11 and find that routes keep appearing and >disappearing. The only reference I have found is that if you run routed >then there is a time-out of some 3-4 minutes after the link is down after >which the routes are deleted. >I think the issue of routing is not covered well in the ppp-HowTo and the >man pages and I wonder if someone can point us in the right direction as to >how pppd handles routing and especially what is the default activity of >pppd when it comes to adding and deleting routes. I have seen one person on >this list recommending that always add and delete routes yourself and dont >take pppd for granted. Is that the recommended practice ? >Regards >Rajiv >At 09:44 PM 1/6/00 +1000, you wrote: >> >>Hi, >> >>I'm experiencing a strange problem using pppd on a dialin linux box >>(Mandrake 6.1, Kernel 2.2.13-22mdk, Mgetty 1.1.14-9mdk and ppp-2.3.11) >> >>I recompiled pppd fresh from the distribution tarball, and enabled PAM >>support - everything else was left at Linux defaults. >> >>It seems that when pppd terminates, it is leaving the interface active >>(sometimes but not every time). >> >>pppd itself does seem to by terminating ok. >> >>Here is some output from route/ifconfig: >> >>203.xx.xx.101 * 255.255.255.255 UH 0 0 0 ppp2 >>203.xx.xx.101 * 255.255.255.255.UH 0 0 0 ppp3 >> >> >>ppp2 Link encap:Point-to-Point Protocol >> inet addr:203.xx.xx.1 P-t-P:203.xx.xx.101 Mask:255.255.255.255 >> UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 >> RX packets:194 errors:1 dropped:0 overruns:0 frame:1 >> TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:10 >> >>ppp3 Link encap:Point-to-Point Protocol >> inet addr:203.xx.xx.1 P-t-P:203.xx.xx.101 Mask:255.255.255.255 >> UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 >> RX packets:12510 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:13558 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:10 >> >> >>Does anyone have any ideas? >> >>I've tried going back to pppd 2.3.8 and the problem still occurs. >> >>Is this a kernel bug? It seems unlikely as I'm using 2.2.13-22mdk which >>is meant to be stable. >> >>Could it be a bug on the 2.2.13-22 kernel? >> >>I'm yet to try 2.2.14 but I have my doubts that it is kernel related? >> >>Cheers, >> >>Matt >>=) >> >> >> >> >> >> >>- >>To unsubscribe from this list: send the line "unsubscribe linux-ppp" in >>the body of a message to [EMAIL PROTECTED] >> >> > >- >To unsubscribe from this list: send the line "unsubscribe linux-ppp" in >the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-ppp" in the body of a message to [EMAIL PROTECTED]
