lkml.org 
[lkml]   [1999]   [Aug]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectDiald and 2.3.13+ development kernels.
Good day, Mike,
Thanks very much for taking over the diald package. I and many
others appreciate your efforts to keep it updated.

Have you been following the "ppp and 2.3.13" discussion on
linux-kernel? If I might summarize, it appears that when the ppp code
moved to the new 2.3.9 pppd code in kernel 2.3.13, diald and the kernel
started fighting. My laptop, which had been able to successfully connect
via diald in 2.2.x and 2.3.12- kernels, lost the ability.
It doesn't appear to be solely the responsibility of pppd; pppd
actually goes so far as to get an IP address and runs the ip-up script,
but diald decides it's taking too long and kills it. I'm typing right now
on a machine that dialed using diald and made the connection. The only
reason I got more than a minute of connect time was the use of "killall -9
diald" before diald decided to abort the connection attempt. pppd stayed
in the background and is transferring packets just fine.
Tim Coleman summarized the problem even better than I:

I have found that diald works fine with pppd 2.3.9. The problem is that
diald does *not* seem to work with kernel version 2.3.1[34].
pppd 2.3.9 works for me with kernels 2.3.1[14], and diald+pppd 2.3.9
works with 2.2.x, but diald+pppd 2.3.9 with kernels 2.3.1[34] seems to
time out before completing the connection.
This has been tested with diald 0.16 and 0.99.1.

My experience and observations almost exactly match Tim's, except
I can add that the problem persists into kernel 2.3.15-pre3.
I attached the log entry from this laptop. The first attempt to
connect "timed out", even though pppd 2.3.9 had gotten an IP address. The
second attempt continued to live because, as I said, I killed -9 diald.
In a normal connect, the next line to show up after "pppd...Remote IP
address..." would be "diald...local ip...remote ip...".

Is there a chance that pppd is failing to return something to
diald that signals the connection is complete? Is anyone successfully
using diald with 2.3.13+ kernels?
Cheers,
- Bill

---------------------------------------------------------------------------
"Knowledge is of two kinds. We know a subject ourselves, or we
know where we can find information upon it."
- Dr Samuel Johnson (1775)
(Courtesy of David Cozzens, <dcozzens@ejhs.k12.vt.us>)
--------------------------------------------------------------------------
William Stearns (wstearns@pobox.com). Mason, Buildkernel, named2hosts,
and ipfwadm2ipchains are at: http://www.pobox.com/~wstearns/
--------------------------------------------------------------------------

Aug 23 22:39:05 sparrow apmd[112]: Charge: * * * (100% 3:28)
Aug 23 22:39:47 sparrow diald[2257]: Nonzero exit status (1) on command '/sbin/ifconfig tap0 192.168.211.2 pointopoint 192.168.211.3 netmask 255.255.255.0 metric 0 mtu 1500 up'
Aug 23 22:39:52 sparrow diald[2257]: Trigger: udp 192.168.211.2/1024 192.5.5.241/53
Aug 23 22:39:52 sparrow diald[2257]: Calling site 192.168.211.3
Aug 23 22:39:53 sparrow diald[2257]: Running connector (pid = 2268).
Aug 23 22:39:58 sparrow diald[2257]: Connected to site 192.168.211.3
Aug 23 22:39:58 sparrow diald[2257]: Running pppd (pid = 2272).
Aug 23 22:39:59 sparrow pppd[2272]: pppd 2.3.9 started by root, uid 0
Aug 23 22:39:59 sparrow pppd[2272]: Using interface ppp0
Aug 23 22:39:59 sparrow pppd[2272]: Connect: ppp0 <--> /dev/ttyS0
Aug 23 22:40:02 sparrow fan[2294]: cooling fan turned on by root
Aug 23 22:40:06 sparrow pppd[2272]: local IP address 209.91.2.5
Aug 23 22:40:06 sparrow pppd[2272]: remote IP address 204.97.123.242
#Diald would normally show a log line here showing the local and remote IP's again.
#[ ppp-up script jobs show output here ]
Aug 23 22:40:33 sparrow diald[2257]: FIFO: force request
Aug 23 22:40:36 sparrow pppd[2272]: CCP: timeout sending Config-Requests
Aug 23 22:40:37 sparrow named[397]: Err/TO getting serial# for "bascom.com"
Aug 23 22:40:58 sparrow diald[2257]: pppd startup timed out. Check your pppd options. Killing pppd.
Aug 23 22:40:58 sparrow diald[2257]: Nonzero exit status (1) on command '/sbin/ifconfig tap0 192.168.211.2 pointopoint 192.168.211.3 netmask 255.255.255.0 metric 0 mtu 1500 up'
Aug 23 22:40:58 sparrow diald[2257]: Nonzero exit status (7) on command '/sbin/route add 192.168.211.3 metric 0 window 4500 dev tap0'
Aug 23 22:40:58 sparrow diald[2257]: Nonzero exit status (7) on command '/sbin/route add default metric 0 window 4500 netmask 0.0.0.0 dev tap0'
Aug 23 22:40:58 sparrow pppd[2272]: Terminating on signal 2.
Aug 23 22:40:58 sparrow pppd[2272]: Connection terminated.
Aug 23 22:40:58 sparrow pppd[2272]: Connect time 1.0 minutes.
Aug 23 22:40:58 sparrow pppd[2272]: Sent 309 bytes, received 89 bytes.
Aug 23 22:40:58 sparrow pppd[2272]: Hangup (SIGHUP)
Aug 23 22:41:38 sparrow pppd[2272]: Exit.
Aug 23 22:41:38 sparrow diald[2257]: Nonzero exit status (1) on command '/sbin/ifconfig tap0 192.168.211.2 pointopoint 192.168.211.3 netmask 255.255.255.0 metric 0 mtu 1500 up'
Aug 23 22:41:39 sparrow diald[2257]: Running disconnector (pid = 2491).
Aug 23 22:41:47 sparrow diald[2257]: Delaying 7 seconds before clear to dial.
Aug 23 22:41:54 sparrow diald[2257]: Calling site 192.168.211.3
Aug 23 22:41:55 sparrow diald[2257]: Running connector (pid = 2495).
Aug 23 22:42:00 sparrow diald[2257]: Connected to site 192.168.211.3
Aug 23 22:42:00 sparrow diald[2257]: Running pppd (pid = 2496).
Aug 23 22:42:00 sparrow pppd[2496]: pppd 2.3.9 started by root, uid 0
Aug 23 22:42:01 sparrow pppd[2496]: Using interface ppp0
Aug 23 22:42:01 sparrow pppd[2496]: Connect: ppp0 <--> /dev/ttyS0
Aug 23 22:42:08 sparrow pppd[2496]: local IP address 209.91.2.94
Aug 23 22:42:08 sparrow pppd[2496]: remote IP address 204.97.123.242
#[ ppp-up script jobs show output here ]
#Diald killed here, remaining ppp daemon stays successfully connected.

\
 
 \ /
  Last update: 2005-03-22 13:53    [W:3.167 / U:0.008 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site