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.