I'm having problems with diald bringing down the connection immediately,
as
seen by the snippet of the system log. It happens while I'm trying to
send
mail or pinging another machine, so there should be something ready to
go
across the wire. I am using the standard filter that came with 0.16.
Oct 5 20:50:32 localhost diald[451]: Running connect (pid = 549).
Oct 5 20:51:02 localhost diald[451]: Running pppd (pid = 550).
Oct 5 20:51:02 localhost pppd[550]: pppd 2.3.3 started by root, uid 0
Oct 5 20:51:02 localhost pppd[550]: Using interface ppp0
Oct 5 20:51:02 localhost pppd[550]: Connect: ppp0 <--> /dev/ttyS0
Oct 5 20:51:06 localhost pppd[550]: Remote message: Welcome
Oct 5 20:51:08 localhost pppd[550]: local IP address 47.190.16.135
Oct 5 20:51:08 localhost pppd[550]: remote IP address 47.190.16.23
Oct 5 20:51:08 localhost diald[451]: New addresses: local
47.190.16.135, remote 47.190.16.23.
Oct 5 20:51:31 localhost diald[451]: Closing down idle link.
Oct 5 20:51:31 localhost pppd[550]: Terminating on signal 2.
Oct 5 20:51:31 localhost pppd[550]: Connection terminated.
Oct 5 20:51:31 localhost pppd[550]: Hangup (SIGHUP)
Oct 5 20:51:31 localhost pppd[550]: Exit.
Any suggestions?
--
Vince Hamrick [EMAIL PROTECTED]
Software Designer
N@rtel /)/( ==+---
RTP, NC
What is it that the maker doesn't want, the buyer doesn't use,
and the user doesn't even see?
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
