Re: modem hangup problems continue
On 22/03/2014 18:04, Ron Leach wrote: On 21/03/2014 23:10, Mike McClain wrote: I'm running Squeeze on a P3 board and dialup. My modem gets hungup after 2.5 minutes about 30% - 40% of the time I connect. Being idle, in the middle of fetching email or loading a webpage seems to make no difference. Is there any way to log all transactions going to the modem which is on ttyS2? Something like script but for a serial port? If you can find a PPP conf file or, maybe, a dialup or chat conf file, perhaps even an LCP conf, and set logging to debug or verbose, then that might bring the first clues for whatever condition the link is getting into. I found some old notes from the time I had problems with dial-up links resetting. My Wheezy system seems to use /etc/ppp/options for various settings, including logging. I suggest you change the entry in /etc/ppp/options for logging, uncommenting the debugging logging level: #debug to become debug There are a number of other quite-powerful options in that file, but which shouldn't be touched (yet). Once the reason that PPP is dropping the link becomes clear, then it is possible that a settings change in this file might fix it. See what that ppp log now tells you about the link reset or disconnection. Further checks will then be needed. If you're feeling you need to understand more, man pon, and man pppd expose you to a lot of detail. regards, Ron -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/532ec1fb.7070...@tesco.net
Re: modem hangup problems continue
On Sat, Mar 22, 2014 at 06:04:48PM +, Ron Leach wrote: On 21/03/2014 23:10, Mike McClain wrote: I'm running Squeeze on a P3 board and dialup. My modem gets hungup after 2.5 minutes about 30% - 40% of the time I connect. Being idle, in the middle of fetching email or loading a webpage seems to make no difference. Is there any way to log all transactions going to the modem which is on ttyS2? Something like script but for a serial port? I don't know about *all* the transactions going to the modem, nor whether that (yet) has been narrowed to the cause of the problem. I've had similar problems with dial-up on another linux distro, caused by LCP negotiation/connections failures. My dial-up PPP process was not receiving the correct state of the connection, even though the connection was transmitting/receiving user data perfectly. So, a minute or two after connection, LCP (I think, though it may have been PPP that commanded it) would disconnect, due to a timeout for something expiring. snip Hi Ron, In /etc/ppp/options lcp-echo-interval 30 and lcp-echo-failure is unset. I've got ppp error logging going to tty12 and /var/log/debug and often see entries such as this: Mar 22 16:03:23 playground pppd[20465]: sent [LCP EchoReq id=0x2 magic=0x84f3fde5] Mar 22 16:03:23 playground pppd[20465]: rcvd [LCP EchoRep id=0x2 magic=0x0] Mar 22 16:03:53 playground pppd[20465]: sent [LCP EchoReq id=0x3 magic=0x84f3fde5] Mar 22 16:03:53 playground pppd[20465]: rcvd [LCP EchoRep id=0x3 magic=0x0] Mar 22 16:04:23 playground pppd[20465]: sent [LCP EchoReq id=0x4 magic=0x84f3fde5] Mar 22 16:04:49 playground pppd[20465]: Modem hangup Mar 22 16:04:49 playground pppd[20465]: Connect time 2.5 minutes. Mar 22 16:04:49 playground pppd[20465]: Sent 124 bytes, received 261 bytes. In this case the hangup occurred 26 Seconds after the EchoReq was sent but I've seen it hangup as little as 2 seconds after sending EchoReq or receiving EchoRep. When I intentionally disconnect (poff) I see this in the logs: Mar 22 17:27:33 playground pppd[20546]: Script /etc/ppp/ip-down started (pid 20641) Mar 22 17:27:33 playground pppd[20546]: sent [LCP TermReq id=0x2 User request] Mar 22 17:27:33 playground pppd[20546]: rcvd [LCP TermAck id=0x2] Mar 22 17:27:33 playground pppd[20546]: Script /etc/ppp/ip-down finished (pid 20641), status = 0x0 I've seen times in the logs where the ISP quit sending EchoReq for several minutes at a time but my system didn't disconnect until I told it to. I don't know what's causing the hangup either that's why I want to log all traffic to the modem to see if I can spot what's happening. If you have other ideas that might help troubleshoot this problem I'm all ears. I've been dealing with this for months and am stumped. Let me say again this doesn't happen every time. If I get past the 2.5 minute mark I may stay online all night. Thanks, Mike -- It's not always polite to speak your mind. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140323004315.GD20400@playground
Re: modem hangup problems continue
On 23/03/2014 00:43, Mike McClain wrote: In /etc/ppp/options lcp-echo-interval 30 and lcp-echo-failure is unset. I've got ppp error logging going to tty12 and /var/log/debug and often see entries such as this: Mar 22 16:03:23 playground pppd[20465]: sent [LCP EchoReq id=0x2 magic=0x84f3fde5] Mar 22 16:03:23 playground pppd[20465]: rcvd [LCP EchoRep id=0x2 magic=0x0] Mar 22 16:03:53 playground pppd[20465]: sent [LCP EchoReq id=0x3 magic=0x84f3fde5] Mar 22 16:03:53 playground pppd[20465]: rcvd [LCP EchoRep id=0x3 magic=0x0] Mar 22 16:04:23 playground pppd[20465]: sent [LCP EchoReq id=0x4 magic=0x84f3fde5] Mar 22 16:04:49 playground pppd[20465]: Modem hangup Mar 22 16:04:49 playground pppd[20465]: Connect time 2.5 minutes. Mar 22 16:04:49 playground pppd[20465]: Sent 124 bytes, received 261 bytes. In this case the hangup occurred 26 Seconds after the EchoReq was sent but I've seen it hangup as little as 2 seconds after sending EchoReq or receiving EchoRep. [.] I've seen times in the logs where the ISP quit sending EchoReq for several minutes at a time but my system didn't disconnect until I told it to. Good start. Could you also post the LCP setup/connection entries in the log, for a case where the connection subsequently fails? I would suggest checking to be sure that the link is coming up correctly, so that, perhaps, the setup phase can be ruled out, and concentrate on the traffic transfer states. I can see why you want to have the modem commands/statuses but I think the only thing they will very clearly show will be whether the modem hangup is occurring as a response to carrier removal by the ISP (including a poor line, in fact), or as an own-initiative decision by your own pppd (or LCP) to drop the connection. In either case, the modem hangup is a symptom, I think, and the events prior to that, at the protocol level, will be the causes, and where clues will be found. Nevertheless, the data can probably be logged, but I've never tried to do so; sadly, I can't explain how to do that. The LCP link establishment log (the earlier section of what you've already posted) will be worth checking, to be sure that all is well. If you don't want to post it, then just get two of them, one for a working session, and one for a session that fails, and very carefully compare them; post back any differences you find. Could you also look at man pppd again, and check whether the additional config files that it describes contain anything that alters settings in /etc/ppp/options? The other thing to check would be the command line calling pon because parameters given pon can override the standard options, as well. On options: Is crtscts set in 'options'? Though you said you've redirected the log to /var/log/debug, did you set the debug option? The dump option will place all the option settings that are in use, irrespective of which file or command line they are sourced from, into the log; I suggest you do that. kdebug option will list the packets sent/received by the kernel driver. As a last resort you could do this, but I fear it will be pages of hexadecimal. kdebug 7 will list general driver debug, sent, and received packets. regards, Ron -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/532f3351.3010...@tesco.net
Re: modem hangup problems continue
On Sun, Mar 23, 2014 at 12:00:55PM +1300, Chris Bannister wrote: snip Are you sure the line is OK? Check the Carrier Detect( CD) LED on the modem. If it's off, it can't see the modem at the other end. Thanks for the thought Chris I'll check the light next time it happens. Mike -- When is it appropriate to call a Linux user a Linutic? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140324002016.GA7618@playground
Re: modem hangup problems continue
On Sun, Mar 23, 2014 at 11:14:03AM +, Ron Leach wrote: snip I found some old notes from the time I had problems with dial-up links resetting. My Wheezy system seems to use /etc/ppp/options for various settings, including logging. I suggest you change the entry in /etc/ppp/options for logging, uncommenting the debugging logging level: #debug to become debug I set debug in options months ago but get little help from it. root@/deb73:~ grep -v ^#\|^$ /etc/ppp/options asyncmap 0 auth crtscts lock hide-password modem debug kdebug 1 mtu 1492 lcp-echo-interval 30 noipx And I've read the man pages several times but don't see a solution or even a hint to what's happening. The latest instance in the logs looks like this: Mar 23 17:31:51 playground pppd[7752]: sent [LCP EchoReq id=0x4 magic=0x295e1973] Mar 23 17:32:11 playground pppd[7752]: Modem hangup Mar 23 17:32:11 playground pppd[7752]: Connect time 2.4 minutes. As you can see there is no clue to why the modem got hung up. Even if lcp-echo-failure were set which it's not it should have tried again before disconnecting. Thanks for your thoughts, Mike -- When is it appropriate to call a Linux user a Linutic? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140324005116.GA7866@playground
Re: modem hangup problems continue
On Fri, Mar 21, 2014 at 04:10:42PM -0700, Mike McClain wrote: I'm running Squeeze on a P3 board and dialup. My modem gets hungup after 2.5 minutes about 30% - 40% of the time I connect. Being idle, in the middle of fetching email or loading a webpage seems to make no difference. Is there any way to log all transactions going to the modem which is on ttyS2? Something like script but for a serial port? Thanks, Mike -- Education is a man's going from cocksure ignorance to thoughtful uncertainty. Moin mitnanner, until recently, I was using a modem myself (now it is being substituted by LTE). With my old 9/11 clunker, I am still running Lenny (kernel 2.6). My usb modem, undressed to it's electronic plate to keep it cool, worked reliably except for one aspect: When I disconnected it from the internet after a certain amount of data transfer, the modem was blocked and I had to pull it's usb plug in order to restore it to working condition. Then it worked reliably again. (This problem did not show up when I connected it to a jounger laptop running Wheezy.) Killing and restarting it's drivers had no effect. So, I just lived with it suspecting some usb idiosycrasy. In Your case, I would remove the modem's box, as serial modems don't seem to be sufficiently ventilated, and hang it's electronic plate vertically to cool it even more: = minus one construction site. Another delicate spot is the serial interrupts, due to poor hardware design, if you work with old hardware: Your modem could interfere with e.g. a serial mouse etc.: Try running your modem with another interrupt, w/out X, disconnect your mouse.. Look into your BIOS. I reduced my serial modem speed from 115200 to 57600, as the phone line needs only 56 Kbit. If that helps, you have probably found the culprit: rearrange your serial interrupts. Try plugging your serial modem cable to another computer outlet, + rearrange your driver's configuration. If everything fails, buy an ELSA usb modem (they work with Linux and should be cheaper by now), plug it in and look into '/var/log/messages'; my driver was '/dev/ACM0'. ELSA modems have worked well for me, so I'll keep my for reverence and as a backup. Good luck! Wilko -- Dialectic of truth: Were she is being possessed, she will be lost; where she is being sought, she may be found. (Hagia Sophia) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140322121943.ga3...@fok01.laje.edewe.de
Re: modem hangup problems continue
On 21/03/2014 23:10, Mike McClain wrote: I'm running Squeeze on a P3 board and dialup. My modem gets hungup after 2.5 minutes about 30% - 40% of the time I connect. Being idle, in the middle of fetching email or loading a webpage seems to make no difference. Is there any way to log all transactions going to the modem which is on ttyS2? Something like script but for a serial port? I don't know about *all* the transactions going to the modem, nor whether that (yet) has been narrowed to the cause of the problem. I've had similar problems with dial-up on another linux distro, caused by LCP negotiation/connections failures. My dial-up PPP process was not receiving the correct state of the connection, even though the connection was transmitting/receiving user data perfectly. So, a minute or two after connection, LCP (I think, though it may have been PPP that commanded it) would disconnect, due to a timeout for something expiring. It was difficult to find, in part because I had no previous experience with LCP. I was able to turn on debug level logging on the PPP process, which helped give the first indications of why links were being taken down, and whether LCP was returning all the status conditions that are needed to avoid the timeout expiring. If you can find a PPP conf file or, maybe, a dialup or chat conf file, perhaps even an LCP conf, and set logging to debug or verbose, then that might bring the first clues for whatever condition the link is getting into. In my case, though I would not expect this is your problem, LCP 'required' a far-end IP address even though none was offered by the ISP; the solution was to set the conf file to always assume a certain address in the absence of receiving one. (Without receiving the far-end address, LCP never moved into a stable connected state, and a PPP timeout expired, if I recall.) Try and find some PPP, chat, or LCP conf files, and set some logging. I'm strongly of the opinion it could be an LCP state problem, though exactly what won't be clear, yet. regards, Ron -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/532dd0c0.2050...@tesco.net
Re: modem hangup problems continue
On Fri, Mar 21, 2014 at 04:10:42PM -0700, Mike McClain wrote: I'm running Squeeze on a P3 board and dialup. My modem gets hungup after 2.5 minutes about 30% - 40% of the time I connect. Being idle, in the middle of fetching email or loading a webpage seems to make no difference. Is there any way to log all transactions going to the modem which is on ttyS2? Something like script but for a serial port? Are you sure the line is OK? Check the Carrier Detect( CD) LED on the modem. If it's off, it can't see the modem at the other end. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140322230055.GE6165@tal
Re: modem hangup problems continue
On Sat, Mar 22, 2014 at 01:19:43PM +0100, Wilko Fokken wrote: On Fri, Mar 21, 2014 at 04:10:42PM -0700, Mike McClain wrote: I'm running Squeeze on a P3 board and dialup. My modem gets hungup after 2.5 minutes about 30% - 40% of the time I connect. Being idle, in the middle of fetching email or loading a webpage seems to make no difference. Is there any way to log all transactions going to the modem which is on ttyS2? Something like script but for a serial port? Thanks, Mike snip In Your case, I would remove the modem's box, as serial modems don't seem to be sufficiently ventilated, and hang it's electronic plate vertically to cool it even more: = minus one construction site. In my case it's an internal PCI USR 5610 modem. Another delicate spot is the serial interrupts, due to poor hardware design, if you work with old hardware: Your modem could interfere with e.g. a serial mouse etc.: Try running your modem with another interrupt, w/out X, disconnect your mouse.. Look into your BIOS. I reduced my serial modem speed from 115200 to 57600, as the phone line needs only 56 Kbit. It's my understanding that the 115200 is between the CPU and the modem while the 57600 is negotiated between the modems and they settle on what speed they both can handle over the link but I'm not an expert or I wouldn't be asking for help. snip Thanks for your thoughts. Mike -- It's not always polite to speak your mind. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140323000246.GC20400@playground
modem hangup problems continue
I'm running Squeeze on a P3 board and dialup. My modem gets hungup after 2.5 minutes about 30% - 40% of the time I connect. Being idle, in the middle of fetching email or loading a webpage seems to make no difference. Is there any way to log all transactions going to the modem which is on ttyS2? Something like script but for a serial port? Thanks, Mike -- Education is a man's going from cocksure ignorance to thoughtful uncertainty. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140321231042.GA442@playground
