Hi All!
I have been successfully running diald 0.99 and 2.1.131 for some time.
It works great, but I have one problem.
Sometimes pppd doesn't start up and gets killed by diald and leaves ppp0
up. The next pppd will bring up ppp1. If the same happens, the ppp number
can go up. Sometimes I have a connection with ppp5.
Then I manually do ifconfig ppp0-4 down, and it starts again with ppp0.
Does anybody have an idea how to tell pppd not to leave the ppp device
around if it is killed by diald, or diald to clean up after pppd?
Thanks,
Gerzson
This log shows pppd getting killed then next time starting with ppp1:
======================================================================
Aug 31 21:49:28 cph pppd[25650]: pppd 2.3.5 started by dialout, uid 0
Aug 31 21:49:28 cph pppd[25650]: Using interface ppp0
Aug 31 21:49:28 cph pppd[25650]: Connect: ppp0 <--> /dev/ttyS0
Aug 31 21:49:31 cph kernel: PPP BSD Compression module registered
Aug 31 21:49:31 cph kernel: PPP Deflate Compression module registered
Aug 31 21:50:27 cph diald[672]: pppd startup timed out. Check your pppd
options.
Killing pppd.
Aug 31 21:50:27 cph diald[672]: start tap0: SIOCSIFDSTADDR: Invalid
argument
Aug 31 21:50:27 cph diald[672]: start tap0: SIOCSIFMETRIC: Operation not
support
ed
Aug 31 21:50:27 cph diald[672]: start tap0: SIOCADDRT: File exists
Aug 31 21:50:27 cph diald[672]: start tap0: SIOCADDRT: File exists
Aug 31 21:50:27 cph diald[672]: stop ppp0: SIOCDELRT: No such process
Aug 31 21:50:27 cph pppd[25650]: Terminating on signal 2.
Aug 31 21:50:27 cph pppd[25650]: Connection terminated.
Aug 31 21:50:28 cph pppd[25650]: Hangup (SIGHUP)
Aug 31 21:50:28 cph pppd[25650]: Exit.
[....snip.....]
Aug 31 21:51:13 cph pppd[25699]: pppd 2.3.5 started by dialout, uid 0
Aug 31 21:51:13 cph pppd[25699]: Using interface ppp1
Aug 31 21:51:13 cph pppd[25699]: Connect: ppp1 <--> /dev/ttyS0
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
