diald interferes with pppd? (was: Re: Installing a kernel off CD-ROM)
I've had this sitting in my 'pending' folder while a bit of Real Life (TM)
happened, but it's time I got back to it -
my problem was that, with the bf2.4 kernel (loaded off boot floppy), Kppp and
pppd worked OK, but with the 2.4-18-k6 kernel on my hard drive, pppd just
doesn't communicate with Kmail or browsers.
I could find no difference in the ppp setups bertween the two kernels (I've
attached my replies to Andreas' questions at the end of this message for
completeness), except that the k6 kernel seems to start diald while bf2.4
doesn't.
With the bf24 kernel (under which Kppp/pppd works OK), /var/log/messages is
as follows:
Oct 10 22:06:59 alti kernel: PPP generic driver version 2.4.1
Oct 10 22:06:59 alti pppd[404]: pppd 2.4.1 started by cr, uid 1000
Oct 10 22:06:59 alti pppd[404]: Using interface ppp0
Oct 10 22:06:59 alti pppd[404]: Connect: ppp0 <--> /dev/ttyS0
Oct 10 22:07:15 alti kernel: PPP BSD Compression module registered
Oct 10 22:07:15 alti kernel: PPP Deflate Compression module registered
Oct 10 22:07:15 alti pppd[404]: local IP address 219.88.129.175
Oct 10 22:07:15 alti pppd[404]: remote IP address 210.55.12.201
Oct 10 22:07:15 alti pppd[404]: primary DNS address 210.55.12.205
Oct 10 22:07:15 alti pppd[404]: secondary DNS address 210.55.12.1
Oct 10 22:07:54 alti pppd[404]: Terminating on signal 15.
Oct 10 22:07:54 alti pppd[404]: Connection terminated.
Oct 10 22:07:54 alti pppd[404]: Connect time 1.0 minutes.
Oct 10 22:07:54 alti pppd[404]: Sent 5303 bytes, received 42981 bytes.
Oct 10 22:07:55 alti pppd[404]: Exit.
With the k6 kernel, (under which Kppp/pppd fails to communicate with apps),
this happens:
Oct 10 21:26:31 alti diald[212]: Delaying 1 seconds before clear to dial.
Oct 10 21:26:34 alti diald[212]: Calling site 192.168.0.2
Oct 10 21:26:34 alti diald[212]: No devices free to call out on.
Oct 10 21:26:35 alti diald[212]: Connect script failed.
Oct 10 21:26:35 alti diald[212]: Delaying 1 seconds before clear to dial.
Oct 10 21:26:59 alti pppd[485]: pppd 2.4.1 started by cr, uid 1000
Oct 10 21:26:59 alti pppd[485]: Using interface ppp0
Oct 10 21:26:59 alti pppd[485]: Connect: ppp0 <--> /dev/ttyS0
Oct 10 21:27:00 alti pppd[485]: local IP address 219.88.128.122
Oct 10 21:27:00 alti pppd[485]: remote IP address 210.55.12.201
Oct 10 21:27:00 alti pppd[485]: primary DNS address 210.55.12.205
Oct 10 21:27:00 alti pppd[485]: secondary DNS address 210.55.12.1
Oct 10 21:27:00 alti diald[212]: Trigger: udp 192.168.0.1/32778
210.55.12.205/53
Oct 10 21:27:00 alti diald[212]: Calling site 192.168.0.2
Oct 10 21:27:00 alti diald[212]: No devices free to call out on.
Oct 10 21:27:00 alti diald[212]: Connect script failed.
Oct 10 21:27:00 alti diald[212]: Delaying 1 seconds before clear to dial.
Oct 10 21:27:03 alti diald[212]: Calling site 192.168.0.2
Oct 10 21:27:03 alti diald[212]: No devices free to call out on.
Oct 10 21:27:04 alti diald[212]: Connect script failed.
Oct 10 21:27:04 alti diald[212]: Delaying 1 seconds before clear to dial.
Oct 10 21:27:06 alti diald[212]: Calling site 192.168.0.2
I assume it's diald that is interfering with pppd; but why would the k6
kernel start diald when bf2.4 doesn't? (Or is diald called by a start-up
file somewhere, but just not built in to the bf2.4 kernel so it fails to
start?)
I'll attach my answers to Andreas' helpful questions below, though I think
they just show that ppp is installing itself OK with both kernels.
On Thu, 09 Oct 2003 19:40, Andreas Janssen wrote:
> Hello
>
> cr (<cr@orcon.net.nz>) wrote:
> > On Mon, 06 Oct 2003 23:20, Andreas Janssen wrote:
> >> cr (<cr@orcon.net.nz>) wrote:
> >>> Is there any way to install a kernel on the hard drive off the
> >>> install
> >>> CD-ROMs (without going through the whole Install process)?
> >>>
> >>> Currently, I have the 2.4.18-k6 kernel installed on my hard drive,
> >>> but it doesn't seem to have ppp enabled (dmesg brings up no
> >>> mention of ppp). I'm a little surprised, I would've thought a
> >>> kernel I downloaded as a .deb off debian.org would have ppp
> >>> enabled, but still...
> >>> (did I do something wrong during the install, I wonder?)
> >>
> >> Check if the ppp support is built as modules. On my system (self
> >> compiled kernel with ppp support as modules), the following modules
> >> are loaded:
> >>
> >> [ppp modules]
> >
> > No, nothing for ppp (or PPP)
> >
> >> A quick search on <http://packages.debian.org> shows that your kernel
> >> package has the ppp_async.o module (I didn't check for the other
> >> ones).
> >>
> >> Try this to find out:
> >>
> >> cat /boot/config-2.4.18-k6 | grep PPP
> >
> > Yes....
> >
> > alti:/etc/modutils# cat /boot/config-2.4.18-1-k6 | grep PPP
> > [kernel seems to have ppp support]
> >
> >> On my system, these drivers are loaded automatically. There is a file
> >> /etc/modutils/ppp with the following lines:
> >>
> >> alias /dev/ppp ppp_generic
> >> alias char-major-108 ppp_generic
> >> alias tty-ldisc-3 ppp_async
> >> alias tty-ldisc-14 ppp_synctty
> >> alias ppp-compress-21 bsd_comp
> >> alias ppp-compress-24 ppp_deflate
> >> alias ppp-compress-26 ppp_deflate
> >>
> >> Please check your /etc/modutils/ppp file and your /etc/modules.conf
> >> to make sure it also has these lines (if not, try to run
> >> update-modules).
> >
> > Yes:
> >
> > [modules.conf is ok]
> >
> > What does this mean? I downloaded the kernel as a .deb from
> > debian.org. I installed it (IIRC) with Kpackage or with dpkg.
> > I can't recall whether it asked me any questions about what to include
> > when I installed it, or not.
> >
> > As a check, I just uninstalled my older 2.4.16-k6 kernel (which I
> > don't normally use any more) and reinstalled it with
> > dpkg -i /<path>/kernel-image-2.4.16-k6_2.4.16-1_i386.deb
> > the only questions it asked me were whether I wanted to use Lilo
> > (no). It gives exactly the same results for the ppp modules as the
> > 2.4.18 kernel (above).
>
> The module configuration file is part of the ppp package, not the kernel
> image packages.
OK, that's useful to know.
>
> > Kppp dials my ISP and makes connection as it should - just that it
> > isn't communicating with Kmail or browsers.
>
> What does the ppp output or log say? Does pinging ip addresses work (try
> ping 192.25.206.10 for www.debian.org)?
>
Launching Kppp from a Gnome terminal window - this is what shows in the
window:
With the bf2.4 kernel (off floppy) - this worked OK:
Opener: received SetSecret
Opener: received OpenLock
Opener: received OpenDevice
Opener: received ExecPPPDaemon
In parent: pppd pid 676
Couldn't find interface ppp0: No such device
Kernel supports ppp alright.
Couldn't find interface ppp0: No such device
Couldn't find interface ppp0: No such device
Opener: received OpenResolv
Opener: received OpenResolv
Opener: received OpenResolv
Opener: received RemoveSecret
Opener: received RemoveSecret
Opener: received KillPPPDaemon
In killpppd(): Sending SIGTERM to 676
Opener: received RemoveSecret
Opener: received RemoveSecret
Opener: received OpenResolv
Opener: received OpenResolv
Opener: received RemoveLock
It was pppd that died
pppd exited with return value 5
Sending 372 a SIGUSR1
(The above was successful, Kmail 'talked' to my ISP OK)
This is with the k6 kernel off the hard drive (unsuccessful):
Opener: received SetSecret
Opener: received OpenLock
Opener: received OpenDevice
Opener: received ExecPPPDaemon
In parent: pppd pid 424
Couldn't find interface ppp0: No such device
Couldn't find interface ppp0: No such device
Kernel supports ppp alright.
Couldn't find interface ppp0: No such device
...
Couldn't find interface ppp0: No such device
Opener: received OpenResolv
Opener: received OpenResolv
Opener: received OpenResolv
Opener: received RemoveSecret
Opener: received RemoveSecret
ioctl(SIOCGPPPSTATS): No such device
ioctl(SIOCGPPPSTATS): No such device
.....
ioctl(SIOCGPPPSTATS): No such device
It was pppd that died
pppd exited with return value 16
[I clicked 'Connect' on Kppp and restarted it...]
Sending 394 a SIGUSR1
Opener: received RemoveSecret
Opener: received RemoveSecret
Opener: received OpenResolv
Opener: received OpenResolv
Opener: received RemoveLock
Opener: received PPPDExitStatus
WARNING: KDE detected X Error: BadMatch (invalid parameter attributes) 8
Major opcode: 42
Opener: received SetSecret
Opener: received OpenLock
Opener: received OpenDevice
Opener: received ExecPPPDaemon
In parent: pppd pid 485
Couldn't find interface ppp0: No such device
Couldn't find interface ppp0: No such device
Kernel supports ppp alright.
Couldn't find interface ppp0: No such device
Couldn't find interface ppp0: No such device
Opener: received OpenResolv
Opener: received OpenResolv
Opener: received OpenResolv
Opener: received RemoveSecret
Opener: received RemoveSecret
Opener: received KillPPPDaemon
In killpppd(): Sending SIGTERM to 485
Opener: received RemoveSecret
Opener: received RemoveSecret
Opener: received OpenResolv
Opener: received OpenResolv
Opener: received RemoveLock
It was pppd that died
pppd exited with return value 5
Sending 394 a SIGUSR1
[The above was unsuccessful, i.e. ppp connected to my ISP, but Kmail
couldn't communicate with the modem, i.e. the lights don't flicker when they
should]
> > When I boot off the bf2.4 kernel on the floppy, I got no response to
> > lsmod | grep ppp before I tried dialling my ISP, but kppp dialled
> > OK and communicated with Kmail successfully and now I get :
> >
> > alti:/home/cr# lsmod | grep ppp
> > ppp_deflate 38944 0 (autoclean)
> > ppp_async 6464 0 (autoclean)
> > ppp_generic 18728 0 (autoclean) [ppp_deflate bsd_comp
> > ppp_async]
> > slhc 4432 0 (autoclean) [ppp_generic]
> >
> >
> > So, I'm a bit puzzled.
>
> The modules are automatically loaded when needed. That is what
> /etc/modules.conf is there for. Are they also loaded successfully when
> using the other kernel?
Yes - this is for the k6 kernel after the unsuccessful attempt listed above:
alti:/home/cr# lsmod | grep ppp
ppp_deflate 39040 0 (autoclean)
ppp_async 6048 0 (autoclean)
ppp_generic 18056 0 (autoclean) [ppp_deflate bsd_comp ppp_async]
slhc 4384 0 (autoclean) [ppp_generic]
ppp seems to be doing everything it should, just Kmail (and browsers) can't
communicate with it.
cr
Reply to: