pppd doesn't run ip-down on disconnect
I'm running Slackware 9.1 straight off the CD right now, and I'm having an issue with PPP. I'm configuring PPP with the default pppsetup script using PAP on an ISA Jaton Communicator V.90 (Intel/Ambient MD5662 chipset) on ttyS1. This is on a VIA Apollo Pro 133a chipset motherboard, an Asus P3V4X to be exact. If any other hardware is relevant, let me know.
Anyway, PPP is running fairly well besides this: After I run ppp-stop I have to manually execute the ip-down script (or reboot) before I can run ppp-go again. If I try to connect without executing ip-down, it simply prints "connect script failed" after about 60 seconds. I know you probably need more information to help, but I'm a *nix newbie, so I don't know what this would be. Which file would it print the details on the connection attempt to? Is there another script which PPPd uses to execute the ip-down script which I can post here? Thanks for any help you can offer Michael Salivar |
|
Not sure it will help but try disconnecting using ppp-off. Otherwise edit the ppp-stop script and add a line that will force ip-down to run.
|
Thanks nazmin, it was an interesting read, but unfortunately didn't provide much insight on this matter, unless I'm just missing something
Gnashley: Ok, I found the ppp-stop and ppp-off scripts, and their results are identical. Upon further inspections, that's because the scripts are identical. Now, I'm getting decent at editing config files and such, but scripting is completely foreign to me. So, here's the script, and then what I'm guessing to include... but I figure I don't have a chance. Code:
#!/bin/bash Code:
# If the ppp0 pid file is present then the program is running. Stop it. |
That's it!
|
Wow, an operating system that makes sense! Be gone Microsoft!
Anyway, it's not working. I suspect that it's my modem being finicky, as it loves to do. I'm thinking the ip-down script is getting run before pppd has been fully killed, and my modem can't cope. Strangely, when ppp-stop executes ip-down, not only am I not able to connect, but running ip-down manually doesn't fix it. Instead, I have to reboot. I'm hoping the 'wait' command will solve my problems. I'm going to try to figure this out on my own though, so please, nobody explain it to me until I give up in a hateful fit of angry frustration :D |
All times are GMT -5. The time now is 12:47 AM. |