Removed the phones, rewired the phone lines, changed pci slots, changed IRQ's in BIOS so the modem would be on its' own IRQ, pinged, echoed, set idle time to indefinite, removed idle time, changed AT commands to match those in windoze exactly, added additional AT commands to allow flex in line noise, verified windoze com port is same as linux ttyS (com5=ttyS4), on and on and on..................

It is sooo scary to me that my modem (USR PCI 56K FaxModem Model 5610 (rev 01)), which is fully supported in SuSE, works in windoze, yet I get a (SIGHUP) and get dumped in linux.

<snip>

Thanks again! Any other suggestions are greatfully appreciated!!!

MTIA

Bernd

Sounds like your ISP is using PAP or CHAP secrets. Every few seconds, it asks for the PWD/USERNAME again. If it doesn't get it, the ISP hangs up. Are you using Kinternet to dial in? If not, you need to... 1) Findout which one your ISP is using? 2) Edit pap/chap-secrets as appropiate, they are in /etc/ppp. You can setup both, and then it doesn't matter, ppp will use the appropiate one. I had this EXACT problem before I set up the files. -Daniel

The 03.09.15 at 10:22, Bernd wrote:

Thanks again! Any other suggestions are greatfully appreciated!!!

Ough. I thought you got rid of that problem by now... Ok. Somewhere in the _windows_ modem configuration, and/or internet configuration, there is a setting that creates a debug log of the connection. Do it. Then compare it to the debug log of pppd in linux, and try to see what goes different... -- Cheers, Carlos Robinson

On Monday 15 September 2003 16:18 pm, Bernd wrote:

I also have tested on 3 different telephone networks (ATT, QWest...) with my ISP, and have the same results (5 hours in windoze before the ISP drops me, and 30 seconds to no more than 59.4 minutes before getting a (SIGHUP) to pppd in SuSE).

The 5 hours is no doubt an ISP restriction. I pay for a 24/7 dialup but at one point my ISP made changes that caused a disconnect every 6 hrs. You should ask your ISP about that. As for the linux connection, I do now assume that you *do* get connected which is a steed of a different hue as compared to not able to login to the ISP at all. Not sure where to go with that. This isn't a 'winmodem' is it? (forgot what modem you have) -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 09/15/03 16:35 + +----------------------------------------------------------------------------+ "You cannot kill time without injuring eternity."

The 03.09.16 at 07:46, Joe Morris (NTM) wrote:

Something else to try is use ethereal on the ppp0 interface to rule out anything coming from outside. It should help in troubleshooting this.

Not completely. For example, it will not show LCP messages, because they belong to the ppp part only, not to tcp/ip or ethernet. For example, I see this: Sep 16 02:31:56 nimrodel pppd[7004]: sent [LCP EchoReq id=0xd7 magic=0x4654332 Sep 16 02:31:56 nimrodel pppd[7004]: rcvd [LCP EchoRep id=0xd7 magic=0x0] Sep 16 02:32:26 nimrodel pppd[7004]: sent [LCP EchoReq id=0xd8 magic=0x4654332 Sep 16 02:32:27 nimrodel pppd[7004]: rcvd [LCP EchoRep id=0xd8 magic=0x0] Sep 16 02:32:56 nimrodel pppd[7004]: sent [LCP EchoReq id=0xd9 magic=0x4654332 Sep 16 02:32:56 nimrodel pppd[7004]: rcvd [LCP EchoRep id=0xd9 magic=0x0] Every 30 seconds, there is one (a kind of ping). If there is no answer, connection will go down (my side). -- Cheers, Carlos Robinson

On Tuesday, 16 September, 2003 18:34, Bob S. wrote: <snip>

Bernd,

I have the exact same modem and have been using it since 7.1. It has been a PITA to set it up, but once done it works very well. Been through 4 upgrades since then 7.3, 8.0, 8,1, and now 8.2 Had to manually configure it every time even though Seems that SuSE is not very user friendly for PCI modems. YAST recognizes it but does not install it. It is ttyS4 It must be linked to /dev/modem. I have only been able to make it work with kinternet, never WVdial. Can't remember exactly but I had to make some changes in KPPP and peers. I missed the earliest part of the thread so Iam not sure exactly what your problem is.

Bob S., I TRULY appreciate your response! My first question to you is: Can you REALLY stay online as long as you want to??? My first thread started on 08/15 as "PPP connection keeps dropping, and another related problem." I learned a few things, and kept trying, yet without ultimate success. So you get an idea of what problem remains, here's the beginning of the thread dated 09/02, before (Revisited) was added: ********** pppd keeps receiving a (SIGHUP) (exit code = 16) and drops. I get dropped as quick as 30 seconds, and CANNOT get past 59.4 minutes, EVER. I'm using 8.1 with KDE 3.1.1, with a U.S. Robotics 56K Performance Pro V.92 PCI modem, which is fully supported (modem drivers are in kernel 2.3 and higher). I manually start/stop my connection with WVDial or KInternet. I rewired the phone line, put the modem in a new slot, removed nearby electrical equipment, contacted the ISP, tested on 3 different phone networks, used wvdialconf to setup the modem, added additional codes to the init string when the wvdialconf string didn't fix the problem, dropped my firewall, and the list goes on, and on. Then I remembered I still had a partition with WindozeME on it. Set up the modem in windoze. When I checked the configuration, I found the init string was different. I added two more codes to the string in windoze, and tested it out. - Strange thing - I started several small downloads (12M total), and let it run. I was able to download the files, then stayed idle for a total of 5 hours before my ISP dropped me!!! Tried it again in windoze (to see if I could do it again), this time with a 78M file. Again!!! 5 hours went by before my ISP dropped me, and before the whole file was downloaded, which meant no idle time. - Stranger thing - Great! (right?) So I booted into SuSE, changed the init string to the SAME one I had success with in windoze (because the previous one wvdialconf set didn't work). Then I tested it the same way I did in windoze. pppd received a (SIGHUP) at 33.1 minutes and died, and then again at 26.6 minutes and died. Afterward, I tried it again in windoze, and got the same 5 hours before my ISP dumped me. **********

You do need to know what protocol your ISP is using, PAP, CHAP, or whatever and make appropriate entries in those files. Mine uses PAP.

My ISP says that they are using neither PAP, or CHAP, but a straight login.

Make sure that your options file is edited properly, and that the line "plugin passwordfd.so" is in your /ppp/peers/kppp file.

It is, and is being loaded each time pppd starts.

Read the ppp HOWTO. It helped me get this thing going.

Where can I find the HOWTO? Is it a SuSE HOWTO or general linux? I scoured man pppd over and over in the past, and again today. I did find that according to the "Authentication" section of man pppd, that authentication must be satisfactorily completed before IPCP can be started. I am successfully sending and receiving IPCP transmissions to establish IP and DNS addresses. This is what's happening in the KInternet logs: *When I am dumped - We are connected. (2003-09-17 09:27:47 PDT) pppd: Hangup (SIGHUP) pppd: Modem hangup pppd: cbcp_lowerdown pppd: Script /etc/ppp/ip-down started (pid 14391) pppd: Connection terminated. pppd: Connect time 59.4 minutes. pppd: Sent 145015 bytes, received 1541806 bytes. pppd: Waiting for 1 child processes... pppd: script /etc/ppp/ip-down, pid 14391 pppd: Script /etc/ppp/ip-down finished (pid 14391), status = 0x0 We are disconnected. (2003-09-17 10:27:10 PDT) pppd died: A modem hung up the phone (exit code 16) *When I take myself down - We are connected. (2003-09-17 12:33:04 PDT) Stopping connection. (2003-09-17 13:04:27 PDT) pppd: Terminating on signal 15. pppd: cbcp_lowerdown pppd: Script /etc/ppp/ip-down started (pid 16331) pppd: sent [LCP TermReq id=0x2 "User request"] pppd: rcvd [LCP TermAck id=0x2] pppd: Connection terminated. pppd: Connect time 31.5 minutes. pppd: Sent 65550 bytes, received 601502 bytes. pppd: Hangup (SIGHUP) pppd: Waiting for 1 child processes... pppd: script /etc/ppp/ip-down, pid 16331 pppd: Script /etc/ppp/ip-down finished (pid 16331), status = 0x0 We are disconnected. (2003-09-17 13:04:28 PDT) pppd died: pppd received a signal (exit code 5) I'm not sure where to go from here!!! Bernd -- "If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea." Antoine de St. Exupery

On 09/18/2003 06:37 AM, Bernd wrote:

...

Make sure that your options file is edited properly, and that the line "plugin passwordfd.so" is in your /ppp/peers/kppp file.

It is, and is being loaded each time pppd starts.

Are you sure? You said you were using kinternet and wvdial. The above is ONLY used by kppp, a totally different program. If this were your problem, though, you couldn't connect at all. /etc/ppp/peers files are specific options for specific programs. Make sure you are checking the correct files for your particular program. On 8.2 I see kppp, ppp, and wvdial all have specific options for these particular programs. I just want to point this out to make sure you are checking the correct files. There is a command string to 'cat' the actual commands in /etc/ppp/options at the beginning of the file. Try this on options, peers/xxx (whichever program you are using), and if you have another options.ttySx file (I made this for different options for different ports, as per the ppp man page). Maybe this might give a clue, though if changing your modem string actually changed the behaviour, it does sound modem driver related, not ppp's problem. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.

On Wednesday 17 September 2003 18:37, Bernd wrote:

On Tuesday, 16 September, 2003 18:34, Bob S. wrote:

<snip>

...

Bernd,

I have the exact same modem and have been using it since 7.1. It has been a PITA to set it up, but once done it works very well. Been through 4 upgrades since then 7.3, 8.0, 8,1, and now 8.2 Had to manually configure it every time even though Seems that SuSE is not very user friendly for PCI modems. YAST recognizes it but does not install it. It is ttyS4 It must be linked to /dev/modem. I have only been able to make it work with kinternet, never WVdial. Can't remember exactly but I had to make some changes in KPPP and peers. I missed the earliest part of the thread so Iam not sure exactly what your problem is.

Bob S.,

I TRULY appreciate your response! My first question to you is: Can you REALLY stay online as long as you want to???

Yes, Many hours at a time. IE: using apt-get I will stay on line for 4 or 5 hours downloading and updating files.

My first thread started on 08/15 as "PPP connection keeps dropping, and another related problem." I learned a few things, and kept trying, yet without ultimate success.

So you get an idea of what problem remains, here's the beginning of the thread dated 09/02, before (Revisited) was added:

********** pppd keeps receiving a (SIGHUP) (exit code = 16) and drops. I get dropped as quick as 30 seconds, and CANNOT get past 59.4 minutes, EVER.

I'm using 8.1 with KDE 3.1.1, with a U.S. Robotics 56K Performance Pro V.92 PCI modem, which is fully supported (modem drivers are in kernel 2.3 and higher). I manually start/stop my connection with WVDial or KInternet.

WVDial just does not work for me. KInternet is what I use.

I rewired the phone line, put the modem in a new slot, removed nearby electrical equipment, contacted the ISP, tested on 3 different phone networks, used wvdialconf to setup the modem, added additional codes to the init string when the wvdialconf string didn't fix the problem, dropped my firewall, and the list goes on, and on. Then I remembered I still had a partition with WindozeME on it.

Really don't think that it is a physical problem.

Set up the modem in windoze. When I checked the configuration, I found the init string was different. I added two more codes to the string in windoze, and tested it out.

I also have a dual boot system. My init string is identical in Windoze and Linux.

- Strange thing -

I started several small downloads (12M total), and let it run. I was able to download the files, then stayed idle for a total of 5 hours before my ISP dropped me!!! Tried it again in windoze (to see if I could do it again), this time with a 78M file. Again!!! 5 hours went by before my ISP dropped me, and before the whole file was downloaded, which meant no idle time.

- Stranger thing -

Great! (right?) So I booted into SuSE, changed the init string to the SAME one I had success with in windoze (because the previous one wvdialconf set didn't work). Then I tested it the same way I did in windoze. pppd received a (SIGHUP) at 33.1 minutes and died, and then again at 26.6 minutes and died.

Again, I never was able to make WVDial work correctly since SuSE 7.0

Afterward, I tried it again in windoze, and got the same 5 hours before my ISP dumped me. **********

...

You do need to know what protocol your ISP is using, PAP, CHAP, or whatever and make appropriate entries in those files. Mine uses PAP.

My ISP says that they are using neither PAP, or CHAP, but a straight login.

Have to believe there is something n the login file. Been a long time since I had to use a normal login file. :-) Sorry !

...

Make sure that your options file is edited properly, and that the line "plugin passwordfd.so" is in your /ppp/peers/kppp file.

It is, and is being loaded each time pppd starts.

...

Read the ppp HOWTO. It helped me get this thing going.

Where can I find the HOWTO? Is it a SuSE HOWTO or general linux? I scoured man pppd over and over in the past, and again today. I did find that according to the "Authentication" section of man pppd, that authentication must be satisfactorily completed before IPCP can be started. I am successfully sending and receiving IPCP transmissions to establish IP and DNS addresses.

I'm sorry, It is 4:30 am right now and I am really tired. Promise that I will locate it for you and get back to you.

This is what's happening in the KInternet logs:

*When I am dumped -

We are connected. (2003-09-17 09:27:47 PDT) pppd: Hangup (SIGHUP) pppd: Modem hangup pppd: cbcp_lowerdown pppd: Script /etc/ppp/ip-down started (pid 14391) pppd: Connection terminated. pppd: Connect time 59.4 minutes. pppd: Sent 145015 bytes, received 1541806 bytes. pppd: Waiting for 1 child processes... pppd: script /etc/ppp/ip-down, pid 14391 pppd: Script /etc/ppp/ip-down finished (pid 14391), status = 0x0 We are disconnected. (2003-09-17 10:27:10 PDT) pppd died: A modem hung up the phone (exit code 16)

*When I take myself down -

We are connected. (2003-09-17 12:33:04 PDT) Stopping connection. (2003-09-17 13:04:27 PDT) pppd: Terminating on signal 15. pppd: cbcp_lowerdown pppd: Script /etc/ppp/ip-down started (pid 16331) pppd: sent [LCP TermReq id=0x2 "User request"] pppd: rcvd [LCP TermAck id=0x2] pppd: Connection terminated. pppd: Connect time 31.5 minutes. pppd: Sent 65550 bytes, received 601502 bytes. pppd: Hangup (SIGHUP) pppd: Waiting for 1 child processes... pppd: script /etc/ppp/ip-down, pid 16331 pppd: Script /etc/ppp/ip-down finished (pid 16331), status = 0x0 We are disconnected. (2003-09-17 13:04:28 PDT) pppd died: pppd received a signal (exit code 5)

I'm not sure where to go from here!!!

Hang in there. We (this list) will solve it for you.

Bernd

Bob S.

Bernd wrote:

On Wednesday, 17 September, 2003 17:30, Joe Morris (NTM) wrote:

...

On 09/18/2003 06:37 AM, Bernd wrote:

...

...

Make sure that your options file is edited properly, and that the line "plugin passwordfd.so" is in your /ppp/peers/kppp file.

It is, and is being loaded each time pppd starts.

Are you sure? You said you were using kinternet and wvdial.

<snip>

In using KInternet as a dialer, this is how the connect process begins:

Starting connection. (2003-09-17 17:00:56 PDT) pppd: Plugin passwordfd.so loaded. pppd: --> WvDial: Internet dialer version 1.42 pppd: --> Initializing modem. pppd: --> Sending: ATZ pppd: OK etc.......

OK, let's start with the basics here. I'll rave on a bit but this is because after running Bulleting Boards Systems (BBSs for some years) I've had to deal with a lot "Why doesn't work on YOUR BBS when it works perfectly on the xxx BBS?" questions :-). Above you will see the entry "pppd: --> Sending: ATZ". Now, this initialising string is OK *IF* you are always using the same system and also have the intiliasing string "permanently" stored in NVRAM (non volatile RAM) on the modem. Why it is all working on your Windows system is because Win has a 'preference' file for your modem (and any other modem it has in its driver database) -- and, I must add this, Win has a tendency to override what YOU want it to do :-(. However, you can correct this somewhat by using the EXTRA modem settings in the Modem settings in the Control Panel. What this is leading to is that when you go to use Linux and the init string "you" issue, ATZ, only resets the modem to whatever is stored in the Profile 0 - ie, ATZ copies what is in Profile0 into the Active Profile which is the profile that will be used to initialise the modem to make the outgoing call and to connect to your ISP. Now, you just don't know what the heck is in Profile0 (unless you look using the AT&V command in a terminal program). But the best way to always know what the modem will be initialised with is to put the string in yourself. Where do you put it? Go to the Control Centre/Center/Yast2 modules/Network/Modem and Edit the modem current settings (the bottom part of the menu which comes up). On the top line of the 'box' you will see the Baud Rate - which should be set to the highest speed your computer can talk to the modem (normally 115200 bps nowadays). The next line will have ATZ and the line under it will have a number of parameters after the AT. Well, the 2 lines should reversed as far as I am concerned and, in fact, there is no need for the second line - but do this and we'll take it from here. What I state now is very much dependent on your modem, and you will need to look at the manual for your modem to get the right parameters, but I feel that the following is pretty well universal for all more recent modems (using the Hayes command set). On the first line put (and this can be done either in caps or lower case and with or without spaces between the parameters - the modem doesn't care about either): AT &F &C1 &D2 E0 S0=0 and on the second line, if you wish, put the "obligatory" ATZ One of the more important parameters in the first line is the &F which resets the modem to factory specifications. In other words, this will "clean" the modem of anything left over from what Windows 'told' it and you then start with the params YOU want it to use (everything following the &F). (A mistake people make when they either buy a new modem or a secondhand one is to omit the &F the first time they use the modem because it is not known what params were stored in the Profile0 either by the factory when the modem was tested before packing for sale or what the previous owner had there. Always issue &F on the first use of the modem.) OK, you put the above string(s) when you configure it thru the Control Centre but you can also put this string in the wvdial.conf file (together with all the other info - name, password, phone number) if you are using wvdial. Or if you are using kppp then you can also put it/them in the modem configuration menu. When using kinternet - which is what I would be recommending - then the parameters come from the configuration in the Control Centre and you can check what is there by right-clicking on the kinternet icon and selecting Settings/View Configuration.

In using wvdial to dial from the shell, the output does not show the use of "Plugin passwordfd.so" , yet I am prompted for the password, and manually input it in the shell, and the connection continues fine (until I get the (SIGHUP) to pppd).

...

There is a command string to 'cat' the actual commands in /etc/ppp/options at the beginning of the file. Try this on options, peers/xxx (whichever program you are using), and if you have another options.ttySx file (I made this for different options for different ports, as per the ppp man page).

???

...

Maybe this might give a clue, though if changing your modem string actually changed the behaviour, it does sound modem driver related, not ppp's problem.

Changing the modem string did not change anything. I can use the default created by wvdialconf, or the default one from windoze, with the same results. I also added commands to the init string that I felt might help, but nothing changed.

Thanks for the response,

Bernd

"I can use the default created by wvdialconf". As far as I am concerned - unless SuSE has fixed the bug- wvdialconf does not import the info from what you put in when you set up the modem in the Control Centre/Network/Modem. You need to type the info in yourself. But I may be wrong. When reading your message(s) containing what your log(s) are showing it occurred to me that you were being disconnected around the hour and the 1/2 hour mark - eg. you don't stay on-line longer that 59.4 mins and it just happens that you logged-on just past the hour. What I am wondering about is whether: (1) your ISP pings you around the 1/2 and 1 hour times to see if you are still on-line (mine pings me on the hour every hour) and if I don't respond the ISP disconnects me because he thinks I am no longer active; and (2) whether you have something set in your modem, say, some kind of timer which disconnects you after something does not happen. I don't know your modem so I am guessing. However, there is one setting that one should be aware of and that is that there is a parameter (%E on most modems, but not all) which controls Fallback/Fallforward and also another one which controls at which baud rate the modem will disconnect when you are on a bad, noisy telephone line. The Fallback/Fallforward parameters comes into play when the phone line is bad and it allows the modem to retrain with the remote modem as the quality of the line decreases or improves (and here it is possible to set the modem to only FallBACK and never FallFORWARD! - a trap for young players); and when the quality of the phone line gets so bad that the throughput of your data reaches a certain low level (set you you) then the modem will disconnect to save you money on long distance calls. Alright, I've said enough :-). Over to you. Cheers. -- Hire teenagers while they still know everything.

The 03.09.18 at 23:36, Basil Chupin wrote:

OK, let's start with the basics here. I'll rave on a bit but this is because after running Bulleting Boards Systems (BBSs for some years)

I'm still a fidonet user, a point :-)

Go to the Control Centre/Center/Yast2 modules/Network/Modem and Edit the modem current settings (the bottom part of the menu which comes up). On

If you are using wvdial on a console - as I am, and Bernd is trying as well, then you need to put that into /etc/wvdial.conf as well (profile "[Dialer Defaults]". -- Cheers, Carlos Robinson

On Thursday, 18 September, 2003 06:36, Basil Chupin wrote:

Bernd wrote:

...

On Wednesday, 17 September, 2003 17:30, Joe Morris (NTM) wrote:

...

On 09/18/2003 06:37 AM, Bernd wrote:

...

...

Make sure that your options file is edited properly, and that the line "plugin passwordfd.so" is in your /ppp/peers/kppp file.

It is, and is being loaded each time pppd starts.

Are you sure? You said you were using kinternet and wvdial.

<snip>

In using KInternet as a dialer, this is how the connect process begins:

Starting connection. (2003-09-17 17:00:56 PDT) pppd: Plugin passwordfd.so loaded. pppd: --> WvDial: Internet dialer version 1.42 pppd: --> Initializing modem. pppd: --> Sending: ATZ pppd: OK etc.......

<snip>

What this is leading to is that when you go to use Linux and the init string "you" issue, ATZ, only resets the modem to whatever is stored in the Profile 0 - ie, ATZ copies what is in Profile0 into the Active Profile which is the profile that will be used to initialise the modem to make the outgoing call and to connect to your ISP. Now, you just don't know what the heck is in Profile0 (unless you look using the AT&V command in a terminal program). But the best way to always know what the modem will be initialised with is to put the string in yourself. Where do you put it?

<serious snip> SORRY! If you notice the last line of the log above, well, that's me saying "etc......". I only included a part of the log as the process begins, to show that yes indeed passwordfd.so is being loaded. There's considerably more, including the -full- init string that I copied from the windoze default setup, and verified to the modem manufacturers list of commands. I have used the default init strings from windoze and placed this in wvdial.conf and Yast modem setup. I have used the defaults from wvdialconf, and Yast modem setup, these two being the same. I have also altered all these strings with other commands listed in the manufacturers manual, that may be appropriate to eliminate disconnect due to line noise and idle time, as well as others. None of this has made ANY difference in my connect time in SuSE. <snip>

When reading your message(s) containing what your log(s) are showing it occurred to me that you were being disconnected around the hour and the 1/2 hour mark - eg. you don't stay on-line longer that 59.4 mins and it just happens that you logged-on just past the hour.

I've already looked at that also, from previous logs. I thought I had a pattern related to a cron job, but not so. This just happens to be the output and times of these sessions. I have the same results no matter where on the minute hand I begin my session. I get disconnected at fairly random intervals, but never exceed 59.4 minutes of connect time.

What I am wondering about is whether:

(1) your ISP pings you around the 1/2 and 1 hour times to see if you are still on-line (mine pings me on the hour every hour) and if I don't respond the ISP disconnects me because he thinks I am no longer active; and

I get dumped at random intervals, and exactly the same way, whether I am actively downloading or idle, and whether or not I echo lcp packets.

(2) whether you have something set in your modem, say, some kind of timer which disconnects you after something does not happen. I don't know your modem so I am guessing. However, there is one setting that one should be aware of and that is that there is a parameter (%E on most modems, but not all) which controls Fallback/Fallforward and also another one which controls at which baud rate the modem will disconnect when you are on a bad, noisy telephone line. The Fallback/Fallforward parameters comes into play when the phone line is bad and it allows the modem to retrain with the remote modem as the quality of the line decreases or improves (and here it is possible to set the modem to only FallBACK and never FallFORWARD! - a trap for young players); and when the quality of the phone line gets so bad that the throughput of your data reaches a certain low level (set you you) then the modem will disconnect to save you money on long distance calls.

Hmmm! Just looked, don't see it in the manual. Do see min/max connect speeds. I'm using all the others that could misinterpret line noise and miscellaneous glitches as a drop. I'll keep looking for other commands that I missed. Thanks!!! Bernd -- "If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea." Antoine de St. Exupery

The 03.09.18 at 19:47, Bernd wrote:

Nothing different in the two logs.

Mmmm.

I commented out all 'lcp' lines in /options, after the problem had already begun. It hasn't made any difference whatsoever. I still am sending/receiving lcp packets while negotiating with the ISP.

And, later, specially near the connection failure? -- Cheers, Carlos Robinson

On Saturday, 20 September, 2003 16:20, Carlos E. R. wrote:

The 03.09.18 at 19:47, Bernd wrote:

...

Nothing different in the two logs.

Mmmm.

...

I commented out all 'lcp' lines in /options, after the problem had already begun. It hasn't made any difference whatsoever. I still am sending/receiving lcp packets while negotiating with the ISP.

And, later, specially near the connection failure?

Nothing at all! (SIGHUP) hits pppd without any other activity near it in time. Bernd -- "If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea." Antoine de St. Exupery

The 03.09.22 at 19:06, Bernd wrote:

I did try strace. I got 548 lines of output in 30 seconds of tracing, and then it exited.

It exited before pppd finished? perhaps you were not tracing the children. But yes, the log file can be verrrry big.

Thanks for everything!!!

Welcome! It't is a strange problem, and I would like to know the reason... -- Cheers, Carlos Robinson

Carlos, et al, I just noticed something in my old windoze logs!!! It shows <cr> & <lf> when sending and receiving, sometimes the one, sometimes the other, sometimes both!!! I do not 'see' this in any of my linux logs, even with debug on. I can't (don't know how to) set 'line termination' in Yast or WVDial. There is nothing in man wvdial.conf to set this up. There is also nothing in man pppd to set this in /etc/ppp/options. It may be set this way by default already, but I can't verify it. How can I set the 'line termination' in Yast or with WVDial? I am able to set it in KPPP, but... When I setup KPPP (no I haven't tried it before), I get inconsistent results. KPPP is sending obscure AT commands that 'I' did not enter in modem/modem commands/init string 0 or init string 1. Therefore I get errors reported back from my modem, or no response at all. I looked in kppprc, but couldn't find the incorrect AT commands there. I see no other place to change the config for kppp. I can't get kppp to use the AT commands I want to send the modem. So I can't try KPPP as an option, to see if it is 'line termination'. Any ideas??? Or am I barking up the wrong tree??? MTIA Bernd -- "If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea." Antoine de St. Exupery

Bernd wrote:

On Saturday, 20 September, 2003 16:35, Carlos E. R. wrote:

...

The 03.09.19 at 10:46, Bernd wrote:

...

In these previous logs I've saved over the last month+, I find more random drop times, yet half still apply to the "top of the hour". Except for the fact that I can't stay connected longer than 59.4 min, overall, it still seems random.

You could try to automate getting all connect, disconnect and on time, and graph frequencies - I'd use OO for that. If there is a certain rough similarity in times, that's something you can show your provider.

Unfortunately, it's not my ISP. I got another ISP to give me a test account for the day. I got a (SIGHUP) to pppd after 58.1 minutes. Soooo... It's on my side, or it's the modem itself.

I have been busy elsewhere (building a computer for a friend of mine) and haven't been reading the thread and if you have already done what I suggested some time ago then you can send me an abusive e-mail :-). You said above "or it's the modem itself." One of the things I suggested was for you to get hold of another modem and see if you still come up with the same problems. I think in an earlier message you said that you would try and (?)borrow another modem for this purpose but I don't know if you did. The other thing, what exactly is the initialising string(s) that you send to the modem in SuSE?

...

...

If I could only track the source of the (SIGHUP)!!!

Any of the ideas I told you were any good? strace, ltrace and such?

I did try strace. I got 548 lines of output in 30 seconds of tracing, and then it exited.

...

Perhaps you could post a new question on how to trace signals, maybe some one knows and notices the question. Or post it on some technical/programming list -- I think there is one on SuSE. not sure -- and if you get to know that, tell me, I'm interested :-)

I'll give this a go.

Thanks for everything!!!

Bernd

Cheers. -- Hire teenagers while they still know everything.

On Thursday, 25 September, 2003 08:23, Basil Chupin wrote: <snip>

The sending of a CR (carriage return) or LF (line feed) is a function of the modem (and the computer's software communicating with it) and is (normally) controlled by the S3 and S4 Registers. But I don't think this should be worrying you UNLESS what is below is not being done in SuSE.

Thanks!

The only one which could be a worry is that one must always use RTS/CTS flow control -- also know as Hardware flow control -- and not use XON/XOFF flow control (the old Xmodem protocol related thing). See the explanations for these in your modem manual. But whether you read the manual or not, do NOT use XON/XOFF for data flow control :-).

Already being done!

-- Hire teenagers while they still know everything.

I told my son (14) about your signature. He said, "Who is that guy?" I told him he should know already;-) He gave me a look and walked off. How true it is. -- "If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea." Antoine de St. Exupery

Bernd wrote:

On Wednesday, 24 September, 2003 23:58, you wrote: <snip>

...

I have been busy elsewhere (building a computer for a friend of mine) and haven't been reading the thread and if you have already done what I suggested some time ago then you can send me an abusive e-mail :-).

You said above "or it's the modem itself." One of the things I suggested was for you to get hold of another modem and see if you still come up with the same problems. I think in an earlier message you said that you would try and (?)borrow another modem for this purpose but I don't know if you did.

The other thing, what exactly is the initialising string(s) that you send to the modem in SuSE?

No abuse!!!

I'm not able to return my modem for another one. I've been tryin to fix this problem for so long that I passed the timeframe of the distributors "return policy". AAARGH!!! I am trying to contact the manufacturer to see if they will replace it with an external, or refund me (according to warranty). I am still within the warranty period, so...

Unfortunately, I don't have another modem to try at present.

Here's the main init strings that I have used for this modem:

The init string that was default in windoze, plus a few related S Registers (Tested successfully in windoze. No difference in SuSE.):

From where *exactly* did you get the initialising string for Windows? Did it come from a log file or from the modem "profile" file sitting in the Drivers sub-directory of the Windows operating system?

AT&F1E0Q0V1&C1&D2S0=0S6=8S7=60S10=200S19=0S25=20L1M1&M4&K1&H1&R2&I0B0X4

OK, the first thing. The '&F1' above -- is this just a typo on your part or is this actually in the init string? Should this be '&F' or '&F0' or is it really '&F1'? Why am I asking? Because.... If it is &F1 then this is re-setting the modem to factory default settings for Profile1 - which may NOT be the same as the ones in Profile0. And it is Profile0 that you would normally be working with. In fact the ATZ mentioned below (and used in wvdial and so on) loads Profile0 into the active profile - but you have not reset it to factory defaults because you have used AT&F1 and reset Profile1. Change the beginning of the above string to AT &F (&F0 which is the same thing; &F automatically means &F0 in modem language). Now for the rest. By issuing AT&F you are resetting Profile0 to factory defaults. If you look in the manual it will show you what the defaults are for each of the parameters and the S Registers. It is therefore a waste of time to issue commands to the modem to set parameters to default values if they are already set by the AT&F command. For example, (?)all modems now have &C1 and &D2 as default settings; same as Q0 and V1. However, S0 is normally set to 1 so issuing 'S0=0' is correct (you don't want the modem answering the phone should someone call you on the line :-)). You only ut into the init string the commands which are NOT the defaults and the ones you really want to use to modify the behaviour of the modem. Get rid of any unnecessary commands in the above init string if they are already the defaults (thru the &F command). Apart from being a 'waste' it is also possible that having too many commands represented by the number of characters on a line will cause the modem to reject the commands- there is a finite number of characters you can put on a line for the modem to recognise. Somewhere in the manual it will tell you this. From memory this number used to 40 characters but it may have gone up on the newer modems.

The init string that was default upon using wvdialconf (Same as Yast default.): AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0

This is the SECOND line of initialising strings when you are setting up the modem when installing SuSE - and which also appears in kppp and in wvdial (although I've had to manually type in info into this conrtol file). The first line is ATZ. Re the above. Drop the "+FCLASS=0" from the above. The "+FCLASS" is to do with a FAX setting, and may be causing you a problem. Now, getting back to the ATZ -- which I said was the FIRST line of the 2 (?or 3) init strings shown when setting up the modem. ATZ I said will set the ACTIVE profile of the modem (ie the one with which the modem will dial out and communicate with your ISP) to the paramaters stored in Profile0. But see what I said earlier above re whether the &F1 is a typo.

All the init strings that I have used are prefaced with a first init of ATZ.

Oh what a "dangerous" thing to say :-). I hope you mean that, "There are 2 initialising strings issued to the modem and string #1 has ATZ in it and the following one has ATQ0V1...... in it." Reason why I am saying this is that if you have something like ATZ Q0 V1 etc then this string will not work: anything after the ATZ is ignored by the modem (UNLESS you put several "~" after it to create a delay of several seconds for the modem to digets the ATZ). Oly use ATZ if it is the only parameter in an intitialising string.

One other thing I just noticed in my windoze log, is that there was a 3rd init string: "ATDT;" before the normal dialing start of "ATDT". My understanding from the manual is that the " ; " returns the modem to command mode after dialing. I have not been using this in SuSE, yet it is used by default in windoze. I'm testing it right now. I'll report back if anything new happens.

Drop the ";" at the end of the ATDT. ATDT only means that you ware using Tone Dialling and there is no need for the ";". What I suggest is that you type the following into the wvdial or kppp or when you are installing SuSE and configuring the modem: alter the FIRST line to read- AT &F E0 &C1 &D2 S0=0 even though &C1 and &D2 are probably default settings anyway' then either DROP the second line completely, because there is no need for it, or change it to read ATZ. And now for the closing comment- I didn't know that your modem was an INTERNAL modem. I had assumed that it was an exteranl modem, connected via cOM1 or cOM2 or USB. Being an internal modem, it's not a Winmodem which requires a special driver to work correctly in Linux? ( I have an internal modem which uses a Rockwell (now Conexant) chipset and I have to use the hcf driver put out by Linuxant - and hte modem works beautifully!) Cheers.

Thanks everyone!!!

Bernd

Pleasure. -- Hire teenagers while they still know everything.

On Friday, 26 September, 2003 10:13, Bernd wrote: <snip>

I'm going to test the following, and reply on this and the rest later:

Init 1: AT Init 2: AT&F1

I'll let you know the results.

44.8 minutes connected, then received (SIGHUP) pppd signal #16. Bernd -- "If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea." Antoine de St. Exupery

On Friday 26 September 2003 18:13 pm, Bernd wrote:

On Friday, 26 September, 2003 08:49, Basil Chupin wrote: <snip>

<snip>

I'm looking for a command I can send the modem that will print the defaults to stdout, but I don't find one. Do you know how I can find out??? I'm on my 3rd day waiting for a response from the manufacturers techs!!!

AT&V should do that. <snip> -- Vic Ayres