For years, I've run my PPPoE over ADSL internet connection using the standard Slackware pppd and rp-pppoe packages.[snip]
For years, I've run my PPPoE over ADSL internet connection using the standard Slackware pppd and rp-pppoe packages. Recently, I noticed that, when shutting down the PPPoE connection, pppd neglects to run the /etc/ppp/ip-down script. I know that this used to work, and I've been trying to determine why it no longer works. Today, I discovered why.--- Synchronet 3.21d-Linux NewsLink 1.2
A couple of years ago, I upgraded to a faster machine, and (as I try to keep the PPPoE session up 24/7), I haven't had a lot of opportunity to exercise the PPPoE shutdown. There is a timing issue with the supplied pppoe-stop script
that causes pppd to terminate before it can successfully complete the ip-down script. Specifically, pppoe-stop
kills pppd, then
kills pppoe-connect, then
kills pppd again (kill -9) "in case it's still hanging around"
on an older machine, in the time it takes to kill pppoe-connect, pppd properly
executes the /etc/ppp/ip-down script and terminates. However, on this new, faster
system, that "kill pppoe-connect" step completes before pppd can complete it's
termination process. The /second/ "kill pppd" kills pppd completely, and it never
gets to run the ip-down script.
My immediate workaround for this is to patch the /usr/sbin/pppoe-stop script to
include a time delay before the second "kill pppd", to permit pppd to properly
shut down. However, I will look for a better solution, and post it here if anyone is interested in it.
HTH anyone with similar issues
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 65 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 01:47:33 |
| Calls: | 862 |
| Files: | 1,311 |
| D/L today: |
10 files (20,373K bytes) |
| Messages: | 264,321 |