OT: pppd dying on trying to connect
Hi all, I need to find out why my pppd daemon is dying when the modem is doing its handshaking ritual. I would like to look in the logs but I do not know where to look other than /var/log. Any ideas why the pppd is dying? I am using kppp on an internal ISA USR modem that is certified to work under linux by linmodems.org. suggestions, asides from buying a new external modem? -- ======================================================================== Hylton Conacher - Licenced Windows user Registered Linux user # 229959 Using Linux Mandrake 9.0 with KDE 3 on a 2.4.19-16mdk kernel ========================================================================
The 03.09.24 at 11:15, Hylton Conacher (ZR1HPC) wrote:
I need to find out why my pppd daemon is dying when the modem is doing its handshaking ritual. I would like to look in the logs but I do not know where to look other than /var/log.
/var/log/messages /var/log/localmessages Go to /etc/ppp/options and enable "debug". -- Cheers, Carlos Robinson
Tnx Carlos, Carlos E. R. wrote:
The 03.09.24 at 11:15, Hylton Conacher (ZR1HPC) wrote:
I need to find out why my pppd daemon is dying when the modem is doing its handshaking ritual. I would like to look in the logs but I do not know where to look other than /var/log.
/var/log/messages
How can I get the system to NOT assume ppp0 is already up, as this would seem to be the problem, I think?Below is an excerpt from my mesages file so that the double try can be seen in trying to connect. Output of /var/log/messages below: pppd 2.4.1 started by hylton, uid 501 Sep 24 11:09:09 localhost pppd[2173]: Using interface ppp0 Sep 24 11:09:09 localhost pppd[2173]: Connect: ppp0 <--> /dev/tts/2 Sep 24 11:09:09 localhost /etc/hotplug/net.agent: assuming ppp0 is already up Sep 24 11:09:18 localhost pppd[2173]: Hangup (SIGHUP) Sep 24 11:09:18 localhost pppd[2173]: Modem hangup Sep 24 11:09:18 localhost pppd[2173]: Connection terminated. Sep 24 11:09:18 localhost pppd[2173]: Exit. Sep 24 11:09:19 localhost /etc/hotplug/net.agent: NET unregister event not supported Sep 24 11:09:55 localhost pppd[2192]: pppd 2.4.1 started by hylton, uid 501 Sep 24 11:09:55 localhost pppd[2192]: Using interface ppp0 Sep 24 11:09:55 localhost pppd[2192]: Connect: ppp0 <--> /dev/tts/2 Sep 24 11:09:55 localhost /etc/hotplug/net.agent: assuming ppp0 is already up Sep 24 11:09:59 localhost kernel: PPP BSD Compression module registered Sep 24 11:09:59 localhost kernel: PPP Deflate Compression module registered Sep 24 11:09:59 localhost pppd[2192]: local IP address 155.239.124.22 Sep 24 11:09:59 localhost pppd[2192]: remote IP address 155.239.125.254 Sep 24 11:09:59 localhost pppd[2192]: primary DNS address 196.25.1.11 Sep 24 11:09:59 localhost pppd[2192]: secondary DNS address 196.43.1.14
Also go to /etc/ppp/options and enable "debug".
How do I enable 'debug' in the below file of /etc/ppp/options? lock noauth noipdefault usepeerdns -- ======================================================================== Hylton Conacher - Licenced Windows user Registered Linux user # 229959 Using Linux Mandrake 9.0 with KDE 3 on a 2.4.19-16mdk kernel ======================================================================== -- ======================================================================== Hylton Conacher - Licenced Windows user Registered Linux user # 229959 Using Linux Mandrake 9.0 with KDE 3 on a 2.4.19-16mdk kernel ========================================================================
/var/log/localmessages
Go to /etc/ppp/options and enable "debug".
-- ======================================================================== Hylton Conacher - Licenced Windows user Registered Linux user # 229959 Using Linux Mandrake 9.0 with KDE 3 on a 2.4.19-16mdk kernel ========================================================================
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 25 September 2003 06:31, Hylton Conacher (ZR1HPC) wrote:
Tnx Carlos,
Carlos E. R. wrote:
The 03.09.24 at 11:15, Hylton Conacher (ZR1HPC) wrote:
I need to find out why my pppd daemon is dying when the modem is doing its handshaking ritual. I would like to look in the logs but I do not know where to look other than /var/log.
/var/log/messages
How can I get the system to NOT assume ppp0 is already up, as this would seem to be the problem, I think?Below is an excerpt from my mesages file so that the double try can be seen in trying to connect.
Output of /var/log/messages below: pppd 2.4.1 started by hylton, uid 501 Sep 24 11:09:09 localhost pppd[2173]: Using interface ppp0 Sep 24 11:09:09 localhost pppd[2173]: Connect: ppp0 <--> /dev/tts/2 Sep 24 11:09:09 localhost /etc/hotplug/net.agent: assuming ppp0 is already up Sep 24 11:09:18 localhost pppd[2173]: Hangup (SIGHUP) Sep 24 11:09:18 localhost pppd[2173]: Modem hangup Sep 24 11:09:18 localhost pppd[2173]: Connection terminated. Sep 24 11:09:18 localhost pppd[2173]: Exit. Sep 24 11:09:19 localhost /etc/hotplug/net.agent: NET unregister event not supported Sep 24 11:09:55 localhost pppd[2192]: pppd 2.4.1 started by hylton, uid 501 Sep 24 11:09:55 localhost pppd[2192]: Using interface ppp0 Sep 24 11:09:55 localhost pppd[2192]: Connect: ppp0 <--> /dev/tts/2 Sep 24 11:09:55 localhost /etc/hotplug/net.agent: assuming ppp0 is already up Sep 24 11:09:59 localhost kernel: PPP BSD Compression module registered Sep 24 11:09:59 localhost kernel: PPP Deflate Compression module registered Sep 24 11:09:59 localhost pppd[2192]: local IP address 155.239.124.22 Sep 24 11:09:59 localhost pppd[2192]: remote IP address 155.239.125.254 Sep 24 11:09:59 localhost pppd[2192]: primary DNS address 196.25.1.11 Sep 24 11:09:59 localhost pppd[2192]: secondary DNS address 196.43.1.14
Also go to /etc/ppp/options and enable "debug".
It sounds like ppp0 is already up what does 'ifconfig' say
How do I enable 'debug' in the below file of /etc/ppp/options?
lock noauth noipdefault usepeerdns debug
- -- A child of five would understand this. Send someone to fetch a child of five. Groucho Marx - ---------------------------------------------------- This mail has been scanned for virus by AntiVir for UNIX Copyright (C) 1994-2003 by H+BEDV Datentechnik GmbH. PGP ID: 589F8449 Fingerprint: EB1C FACF 6BEB 540E 8AC0 F04E 2A25 A2F1 589F 8449 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE/daowKiWi8VifhEkRAmHdAKCjPu7qT1DkXCXtRQLn8SdI31nCEACdGpNh q9gNtbP/QHmB4D+vbLm7lE0= =0yPK -----END PGP SIGNATURE-----
Ian David Laws wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thursday 25 September 2003 06:31, Hylton Conacher (ZR1HPC) wrote:
Tnx Carlos,
Carlos E. R. wrote:
The 03.09.24 at 11:15, Hylton Conacher (ZR1HPC) wrote:
I need to find out why my pppd daemon is dying when the modem is doing its handshaking ritual. I would like to look in the logs but I do not know where to look other than /var/log.
/var/log/messages
How can I get the system to NOT assume ppp0 is already up, as this would seem to be the problem, I think?Below is an excerpt from my mesages file so that the double try can be seen in trying to connect.
Output of /var/log/messages below: pppd 2.4.1 started by hylton, uid 501 Sep 24 11:09:09 localhost pppd[2173]: Using interface ppp0 Sep 24 11:09:09 localhost pppd[2173]: Connect: ppp0 <--> /dev/tts/2 Sep 24 11:09:09 localhost /etc/hotplug/net.agent: assuming ppp0 is already up Sep 24 11:09:18 localhost pppd[2173]: Hangup (SIGHUP) Sep 24 11:09:18 localhost pppd[2173]: Modem hangup Sep 24 11:09:18 localhost pppd[2173]: Connection terminated. Sep 24 11:09:18 localhost pppd[2173]: Exit. Sep 24 11:09:19 localhost /etc/hotplug/net.agent: NET unregister event not supported Sep 24 11:09:55 localhost pppd[2192]: pppd 2.4.1 started by hylton, uid 501 Sep 24 11:09:55 localhost pppd[2192]: Using interface ppp0 Sep 24 11:09:55 localhost pppd[2192]: Connect: ppp0 <--> /dev/tts/2 Sep 24 11:09:55 localhost /etc/hotplug/net.agent: assuming ppp0 is already up Sep 24 11:09:59 localhost kernel: PPP BSD Compression module registered Sep 24 11:09:59 localhost kernel: PPP Deflate Compression module registered Sep 24 11:09:59 localhost pppd[2192]: local IP address 155.239.124.22 Sep 24 11:09:59 localhost pppd[2192]: remote IP address 155.239.125.254 Sep 24 11:09:59 localhost pppd[2192]: primary DNS address 196.25.1.11 Sep 24 11:09:59 localhost pppd[2192]: secondary DNS address 196.43.1.14
Also go to /etc/ppp/options and enable "debug". Done
It sounds like ppp0 is already up what does 'ifconfig' say
DEVICE="ppp0" ONBOOT="no" USERCTL="no" MODEMPORT="/dev/modem" LINESPEED="115200" PERSIST="yes" DEFABORT="yes" DEBUG="yes" INITSTRING="ATZ" DEFROUTE="yes" HARDFLOWCTL="yes" ESCAPECHARS="no" PPPOPTIONS="" PAPNAME="hylton@global.co.za" REMIP="" NETMASK="" IPADDR="" MRU="" MTU="" DISCONNECTTIMEOUT="5" RETRYTIMEOUT="60" BOOTPROTO="none" PEERDNS="yes" DNS1=196.41.128.254 DNS2=196.25.1.1 Comments anyone as this is still unresolved? -- ======================================================================== Hylton Conacher - Licenced Windows user Registered Linux user # 229959 Using Linux Mandrake 9.0 with KDE 3 on a 2.4.19-16mdk kernel ========================================================================
The 03.09.25 at 06:31, Hylton Conacher (ZR1HPC) wrote:
How can I get the system to NOT assume ppp0 is already up, as this would seem to be the problem, I think?Below is an excerpt from my mesages file so that the double try can be seen in trying to connect.
More info required :-)
Output of /var/log/messages below: pppd 2.4.1 started by hylton, uid 501 Sep 24 11:09:09 localhost pppd[2173]: Using interface ppp0 Sep 24 11:09:09 localhost pppd[2173]: Connect: ppp0 <--> /dev/tts/2 Sep 24 11:09:09 localhost /etc/hotplug/net.agent: assuming ppp0 is already up Sep 24 11:09:18 localhost pppd[2173]: Hangup (SIGHUP)
What happened in those 9"? What shows there after "debug" enabled? What of modem do you have? -- Cheers, Carlos Robinson
Carlos E. R. wrote:
The 03.09.25 at 06:31, Hylton Conacher (ZR1HPC) wrote:
How can I get the system to NOT assume ppp0 is already up, as this would seem to be the problem, I think?Below is an excerpt from my mesages file so that the double try can be seen in trying to connect.
More info required :-)
What type, log info or hardware info? Which directory can I find the necessary log info? Hardware info: Modem is 3Com internal ISA dialup modem on AMD Athlon mobo with no jumpers enabled to specify com port or IRQ. Chips info available on request as I see there are several.
Output of /var/log/messages below: pppd 2.4.1 started by hylton, uid 501 Sep 24 11:09:09 localhost pppd[2173]: Using interface ppp0 Sep 24 11:09:09 localhost pppd[2173]: Connect: ppp0 <--> /dev/tts/2 Sep 24 11:09:09 localhost /etc/hotplug/net.agent: assuming ppp0 is already up Sep 24 11:09:18 localhost pppd[2173]: Hangup (SIGHUP)
What happened in those 9"? Using X(being an 'ex'-Windows user) I start up kppp and click on connect. Modem dials Call is accepted (Awaiting CONNECT) Modem handshaking Modem hangsup with signal 15
What shows there after "debug" enabled? After adding debug into the relevant file, if I click on Details to see why the connection failed the error report comes back and says it can't help me here.
What of modem do you have? 3Com internal ISA modem (ooopps I thought it was a USR, although I think they are one and the same, almost) Chip details on request
Enough info? Is there perhaps a separate modem log file to /messages that might tell us more? -- ======================================================================== Hylton Conacher - Licenced Windows user Registered Linux user # 229959 Using Linux Mandrake 9.0 with KDE 3 on a 2.4.19-16mdk kernel ========================================================================
The 03.10.05 at 12:49, Hylton Conacher (ZR1HPC) wrote:
More info required :-)
What type, log info or hardware info?
Good question :-)
Which directory can I find the necessary log info?
Most would be in file /var/log/messages, but also in /var/log/localmessages
What shows there after "debug" enabled? After adding debug into the relevant file, if I click on Details to see why the connection failed the error report comes back and says it can't help me here.
No. Edit file /etc/ppp/options. You will find this text: # Increase debugging level (same as -d). The debug output is written # to syslog LOG_LOCAL2. #debug remove the comment mark (#) before the word 'debug'.
Enough info?
Not yet, because the reason for not connecting is not seen.
Is there perhaps a separate modem log file to /messages that might tell us more?
The detailed info is missing; I hope to find the reason for disconnect there. The syslog log files are all in '/var/log/', and what goes where is configured in '/etc/syslog.conf'. There is a line there: *.*;mail.none;news.none -/var/log/messages That means that almost everything (except mail and news logs) go to file '/var/log/messages' -- at least, that is the default configuration for SuSE 8.2. pppd messages use facility local2, which is included above; but also by this rules: local0,local1.* -/var/log/localmessages local2,local3.* -/var/log/localmessages local4,local5.* -/var/log/localmessages local6,local7.* -/var/log/localmessages they go to file '/var/log/localmessages'. In my system, they only go there. For more info on the above, read 'man syslog.conf -- Cheers, Carlos Robinson
Carlos E. R. wrote:
The 03.10.05 at 12:49, Hylton Conacher (ZR1HPC) wrote:
More info required :-)
What type, log info or hardware info?
Good question :-)
Which directory can I find the necessary log info?
Most would be in file /var/log/messages, but also in /var/log/localmessages
Mandrake does not have a /var/log/localmessages file but on venturing into the /var/log directory I saw a file called syslog. Opened it up and had a look for ip-down and lo and behold..... I was greeted with messages just prior to that of how my connection had been refused at various IP's, eventhough I had been given a dynamic IP address myself.
What shows there after "debug" enabled? After adding debug into the relevant file, if I click on Details to see why the connection failed the error report comes back and says it can't help me here.
No. Edit file /etc/ppp/options. You will find this text:
# Increase debugging level (same as -d). The debug output is written # to syslog LOG_LOCAL2. #debug
remove the comment mark (#) before the word 'debug'.
Oh it would be lovely to be running SuSe :| There seems to be so much more information available in the config files. Wishing 9.0 would hurry up, be released and get on its way to the RSA. Mandrake just lists the values ie lock usepeerdns debug #after I added it etc
Enough info?
Not yet, because the reason for not connecting is not seen.
It would seem from the syslog that as the smbd was denied access to a few IP's the pppd died with termination signal 15. I also, over the last couple of days, had to change my dial-in numbers to my ISP. After the change there is no more modem hangup, so I can only guess that the number I was dialling had some problems in authenticating me and therefore hanged up the modem connection. Who knew it would actually be my ISP's 'fault' that I couldn't connect? :)
rest of text snipped
-- ======================================================================== Hylton Conacher - Licenced Windows user Registered Linux user # 229959 Using Linux Mandrake 9.0 with KDE 3 on a 2.4.19-16mdk kernel ========================================================================
The 03.10.09 at 06:34, Hylton Conacher (ZR1HPC) wrote:
Most would be in file /var/log/messages, but also in /var/log/localmessages
Mandrake does not have a /var/log/localmessages file but on venturing
Mandrake? I thought this was a SuSE list :-p
into the /var/log directory I saw a file called syslog. Opened it up and had a look for ip-down and lo and behold..... I was greeted with messages just prior to that of how my connection had been refused at various IP's, eventhough I had been given a dynamic IP address myself.
See? Missing info. Nothing like having a crystal ball beside the monitor :-)
remove the comment mark (#) before the word 'debug'.
Oh it would be lovely to be running SuSe :| There seems to be so much more information available in the config files. Wishing 9.0 would hurry up, be released and get on its way to the RSA. Mandrake just lists the values ie
lock usepeerdns debug #after I added it etc
Agh. A friend of mine was trying to convince himself to try Linux, and he complained that installation was difficult. I told him to buy a distro, like SuSE: good manuals, easy installation, a handy cheap "guru" -- but he bought Mandrake, just to go against me ;-) Then, of course, he asked me for help, and... he finished buying SuSE some months later :-)
Who knew it would actually be my ISP's 'fault' that I couldn't connect? :)
Ah... -- Cheers, Carlos Robinson
Carlos E. R. wrote:
The 03.10.09 at 06:34, Hylton Conacher (ZR1HPC) wrote:
Most would be in file /var/log/messages, but also in /var/log/localmessages
Mandrake does not have a /var/log/localmessages file but on venturing
Mandrake? I thought this was a SuSE list :-p
a bit of cross pollination as it might be said and most definitely enough to convince me to swop to SuSe when 9.0 comes out.
into the /var/log directory I saw a file called syslog. Opened it up and had a look for ip-down and lo and behold..... I was greeted with messages just prior to that of how my connection had been refused at various IP's, eventhough I had been given a dynamic IP address myself.
See? Missing info. Nothing like having a crystal ball beside the monitor :-)
I knew I was missing something, asides from not having Suse :)
remove the comment mark (#) before the word 'debug'.
Oh it would be lovely to be running SuSe :| There seems to be so much more information available in the config files. Wishing 9.0 would hurry up, be released and get on its way to the RSA. Mandrake just lists the values ie
lock usepeerdns debug #after I added it etc
Agh. A friend of mine was trying to convince himself to try Linux, and he complained that installation was difficult. I told him to buy a distro, like SuSE: good manuals, easy installation, a handy cheap "guru" -- but he bought Mandrake, just to go against me ;-) Then, of course, he asked me for help, and... he finished buying SuSE some months later :-)
Your friend has had it easy :) . I started on RH 6 then moved to Mandrake 8 and now 9 only to discover that SuSe was probably the one I should have started off and stuck with right from the beginning. It would seem from this list that SuSe has far greater GUI functionality than Mandrake or even RH has, and that is what is swaying my opinion, especially since I was a M$ netadmin b4.
Who knew it would actually be my ISP's 'fault' that I couldn't connect? :) Ah...
I was dialling thru a congested national number(that was used by all ISP's) and didn't seem to be getting authenticated. since my ISP got their own number, np. Thanks for the help Carlos, and one or two others. It was certainly appreciated since I wasn't even running the 'correct' distribution :) -- ======================================================================== Hylton Conacher - Licenced Windows user Registered Linux user # 229959 Using Linux Mandrake 9.0 with KDE 3 on a 2.4.19-16mdk kernel ========================================================================
participants (3)
-
Carlos E. R.
-
Hylton Conacher (ZR1HPC)
-
Ian David Laws