Hi, When I run (as user) wvdial on a console on SuSE 9.1, with the same configuration files as in SuSE 8.2, I get these messages (the connection works): --> Warning: Could not modify /etc/ppp/pap-secrets: Permission denied --> --> PAP (Password Authentication Protocol) may be flaky. --> Warning: Could not modify /etc/ppp/chap-secrets: Permission denied --> --> CHAP (Challenge Handshake) may be flaky. --> pid of pppd: 6840 --> pppd: ovider --> Using interface ppp0 --> pppd: ovider --> pppd: ovider --> pppd: ovider .... --> Connected... Press Ctrl-C to disconnect --> pppd: ovider And a lot more of those "ovider" in between. What on earth are those "ovider" things? :-? I don't care about /etc/ppp/pap-secrets not been writeable - any way, pppd is suid: -rwsr-sr-- 1 root dialout 255044 2004-06-01 16:41 /usr/sbin/pppd* -- Cheers, Carlos Robinson
On Wednesday 30 June 2004 08:00 am, Carlos E. R. wrote:
Hi,
When I run (as user) wvdial on a console on SuSE 9.1, with the same configuration files as in SuSE 8.2, I get these messages (the connection works):
--> Warning: Could not modify /etc/ppp/pap-secrets: Permission denied --> --> PAP (Password Authentication Protocol) may be flaky. --> Warning: Could not modify /etc/ppp/chap-secrets: Permission denied --> --> CHAP (Challenge Handshake) may be flaky. --> pid of pppd: 6840 --> pppd: ovider --> Using interface ppp0 --> pppd: ovider --> pppd: ovider --> pppd: ovider .... --> Connected... Press Ctrl-C to disconnect --> pppd: ovider
And a lot more of those "ovider" in between. What on earth are those "ovider" things? :-?
Looks like the last part of 'provider'... Mayhaps you have a file somewhere that is messed up?
I don't care about /etc/ppp/pap-secrets not been writeable - any way, pppd is suid:
-rwsr-sr-- 1 root dialout 255044 2004-06-01 16:41 /usr/sbin/pppd*
-- Cheers, Carlos Robinson
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 06/30/04 12:24 + +----------------------------------------------------------------------------+ "Coed dorms promote campus unrest."
The Wednesday 2004-06-30 at 12:25 -0400, Bruce Marshall wrote:
--> pppd: ovider --> pppd: ovider --> pppd: ovider .... --> Connected... Press Ctrl-C to disconnect --> pppd: ovider
And a lot more of those "ovider" in between. What on earth are those "ovider" things? :-?
Looks like the last part of 'provider'... Mayhaps you have a file somewhere that is messed up?
I know, that is what I noticed when grepping the config. But the "/etc/wvdial.conf" file is the exact untouched file I had in SuSE 8.2, dated "Feb 2 2004" -- Cheers, Carlos Robinson
* Carlos E. R. <robin1.listas@tiscali.es> [06-30-04 19:36]:
I know, that is what I noticed when grepping the config. But the "/etc/wvdial.conf" file is the exact untouched file I had in SuSE 8.2, dated "Feb 2 2004"
If you do not have 'Stupid Mode' enabled, try it. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
* Carlos E. R. <robin1.listas@tiscali.es> [07-01-04 12:28]:
The Wednesday 2004-06-30 at 20:05 -0500, Patrick Shanahan wrote:
If you do not have 'Stupid Mode' enabled, try it.
It has been on for years :-)
Then, perhaps, the opposite ?? Just a shot in the dark! -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
The Thursday 2004-07-01 at 13:21 -0500, Patrick Shanahan wrote:
If you do not have 'Stupid Mode' enabled, try it.
It has been on for years :-)
Then, perhaps, the opposite ?? Just a shot in the dark!
:-) I also tried that years ago. If I do so, it tries to log into the access router of the providers, meaning that ppp session is not started, like if I tried to log into the router configuration. Those routers are designed for many types of access, not only ppp (for example, direct terminal access, VoIP, ISDN, etc). I know, I worked for the company that sold them and for one of the main ISP that used them O:-) But that is not the problem: the conection works, it is only the messages on the terminal that runs wvdial. The log file is devoid of them "ovider"s. A nuisance only, that appeared with SuSE 9.1 But thank you for trying :-) -- Cheers, Carlos Robinson
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2004-07-02 at 02:46 +0200, I wrote:
The Thursday 2004-07-01 at 13:21 -0500, Patrick Shanahan wrote:
If you do not have 'Stupid Mode' enabled, try it.
It has been on for years :-)
Then, perhaps, the opposite ?? Just a shot in the dark!
:-)
I also tried that years ago. If I do so, it tries to log into the access router of the providers, meaning that ppp session is not started, like if
I was having a secondary problem, that one of my internet providers stopped working for me after I updated to SuSE 9.1 - I thought the provider must have change something. pppd[6857]: rcvd [CHAP Challenge id=0x3 <7211438c80e5297b239c109ed968bf65>, name = "Hiper"] pppd[6857]: Unable to obtain CHAP password for ****@telelineb on Hiper from plugin pppd[6857]: No CHAP secret found for authenticating us to Hiper pppd[6857]: sent [CHAP Response id=0x3 <3ff*...>, name = "****@telelineb"] pppd[6857]: rcvd [LCP EchoRep id=0x0 magic=0xded72aa1] pppd[6857]: rcvd [CHAP Failure id=0x3 ""] pppd[6857]: CHAP authentication failed pppd[6857]: sent [LCP TermReq id=0x4 "Failed to authenticate ourselves to peer"] So, a ihave just tried to renable stupidmode=0 after having it at 1 for years... and it worked. In this case, the login/password is given before starting the ppp session, and it is not logged, but can be seen on the wvdial terminal: --> Carrier detected. Waiting for prompt. Welcome to 3Com Total Control HiPer ARC (TM) Networks That Go The Distance (TM) login: --> Looks like a login prompt. --> Sending: ****@telelineb ****@telelineb Password: --> Looks like a password prompt. --> Sending: (password) However, I'm still getting dozens of that "ovider" string. I guess I'll have a look at the sources. :-} [...] No luck there: I see no "ovider" string there, but dozens of "provider". P.S.: I'm looking at the thread of your problems with nvida, but I have no help to give there. I also have an nvidia card, but I haven't seen that problem - yet. Right now, I have two open sesions opened, one with gnome and another with kde (F7 and F8) - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFA6bnttTMYHG2NR9URAs5CAJwOl0yvMPcdVFLR6sS1cVQaBdO1ngCdGuC5 iSGYFgVu+hA1nAaBbmy/JvY= =kAeG -----END PGP SIGNATURE-----
* Carlos E. R. <robin1.listas@tiscali.es> [07-05-04 15:29]:
The Friday 2004-07-02 at 02:46 +0200, I wrote:
The Thursday 2004-07-01 at 13:21 -0500, Patrick Shanahan wrote:
If you do not have 'Stupid Mode' enabled, try it.
It has been on for years :-)
Then, perhaps, the opposite ?? Just a shot in the dark! ...
So, a ihave just tried to renable stupidmode=0 after having it at 1 for years... and it worked. In this case, the login/password is given before starting the ppp session, and it is not logged, but can be seen on the wvdial terminal:
--> Carrier detected. Waiting for prompt. Welcome to 3Com Total Control HiPer ARC (TM) Networks That Go The Distance (TM) login: --> Looks like a login prompt. --> Sending: ****@telelineb ****@telelineb Password: --> Looks like a password prompt. --> Sending: (password)
Well, it was just a dark shot. I haven't used dial-up for several years, but had similar problems with two secondary shell providers.
However, I'm still getting dozens of that "ovider" string. I guess I'll have a look at the sources. :-} [...] No luck there: I see no "ovider" string there, but dozens of "provider".
it *does* look like the first char has been dropped.
P.S.: I'm looking at the thread of your problems with nvida, but I have no help to give there. I also have an nvidia card, but I haven't seen that problem - yet.
It is probably (??) a combination of the Riva TNT2 card, kernel and nvidia driver. What I really don't understand is that it worked with the 5336 driver for ~5 months before trouble. The 4620 driver has given me back additional X sessions, correct (or seemingly) logon to level 5 and jumped from 89 fps to 1200 fps in kde and Xfce. That's a new wrinkle. NOTE: fps were down in the 5336 driver also.
Right now, I have two open sesions opened, one with gnome and another with kde (F7 and F8)
me so. gud luk, -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
The Monday 2004-07-05 at 21:55 -0500, Patrick Shanahan wrote:
However, I'm still getting dozens of that "ovider" string. I guess I'll have a look at the sources. :-} [...] No luck there: I see no "ovider" string there, but dozens of "provider".
it *does* look like the first char has been dropped.
It does indeed, I know. But I may be one of the very few people using wvdial directly on a console, so that not many people have noticed that behaviour.
P.S.: I'm looking at the thread of your problems with nvida, but I have no help to give there. I also have an nvidia card, but I haven't seen that problem - yet.
It is probably (??) a combination of the Riva TNT2 card, kernel and nvidia driver. What I really don't understand is that it worked with the 5336 driver for ~5 months before trouble. The 4620 driver has given me back additional X sessions, correct (or seemingly) logon to level 5 and jumped from 89 fps to 1200 fps in kde and Xfce. That's a new wrinkle. NOTE: fps were down in the 5336 driver also.
Probably some patch triggered the problem. Software is so complex nowdays that a little change on a corner may have unforeseen consequences on a totally diferent and unrelated (aparently) corner. By the way, I get around 800 fps on the small window of glxgears (the TV is on). At full window I get 114. When minimized (not shown) it goes to 4000. CPU (PIV-1800)is up to 100%. I have a "NV11 (GeForce2) Board" (64Mb): DeviceName=GeForce2 MX/MX 400 VendorName=nVidia Corporation SubVendorName=Micro-star International Co Ltd And the driver is: /lib/modules/precompiled/2.6.5-7.75-default/nvidia/gfx//nv-linux.o-1.0-5336.pre which is the one YOU installed for me when upgrading to SuSE 9.1. -- Cheers, Carlos Robinson
The Wednesday 2004-06-30 at 14:00 +0200, I wrote:
When I run (as user) wvdial on a console on SuSE 9.1, with the same configuration files as in SuSE 8.2, I get these messages (the connection works):
--> Warning: Could not modify /etc/ppp/pap-secrets: Permission denied --> --> PAP (Password Authentication Protocol) may be flaky. --> Warning: Could not modify /etc/ppp/chap-secrets: Permission denied --> --> CHAP (Challenge Handshake) may be flaky. --> pid of pppd: 6840 --> pppd: ovider --> Using interface ppp0 --> pppd: ovider --> pppd: ovider --> pppd: ovider .... --> Connected... Press Ctrl-C to disconnect --> pppd: ovider
And a lot more of those "ovider" in between. What on earth are those "ovider" things? :-?
I have noticed that at the same time that I get these on the wvdial terminal (hundreds of them, by the way): --> pppd: ovider --> pppd: ovider --> pppd: ovider the log get these other entries: Jul 15 20:49:24 nimrodel pppd[6100]: rcvd [Compressed data] 00 03 14 97 c7 0e ab 48 ... Jul 15 20:49:24 nimrodel pppd[6100]: sent [CCP ResetReq id=0x12] Jul 15 20:49:25 nimrodel pppd[6100]: rcvd [CCP ResetAck id=0x12] Jul 15 20:49:26 nimrodel pppd[6100]: rcvd [Compressed data] 00 03 ac 57 d9 ae a3 38 ... Jul 15 20:49:26 nimrodel pppd[6100]: sent [CCP ResetReq id=0x13] Jul 15 20:49:26 nimrodel pppd[6100]: rcvd [CCP ResetAck id=0x13] They are simultaneous. I have reason to believe that other people are getting different messages, like "modem" (I noticed this on a diferent, unrelated post on this list, perhaps). I think wvdial is trying to print some message, but there is some corruption or buffer overflow somewhere or something of the sort, and the wrong message gets printed. On a related note - what are those "ResetReq" the pppd daemon sends? Could that be related to the fact that the downloads are slower than in previous SuSE versions? I see the modem lights go off now and then, but can't say if at the same time as these reset things. -- Cheers, Carlos Robinson
The Thursday 2004-07-15 at 21:05 +0200, Carlos E. R. wrote:
The Wednesday 2004-06-30 at 14:00 +0200, I wrote:
When I run (as user) wvdial on a console on SuSE 9.1, with the same configuration files as in SuSE 8.2, I get these messages (the connection works):
--> Warning: Could not modify /etc/ppp/pap-secrets: Permission denied --> --> PAP (Password Authentication Protocol) may be flaky. --> Warning: Could not modify /etc/ppp/chap-secrets: Permission denied --> --> CHAP (Challenge Handshake) may be flaky. --> pid of pppd: 6840 --> pppd: ovider --> Using interface ppp0 --> pppd: ovider --> pppd: ovider --> pppd: ovider .... --> Connected... Press Ctrl-C to disconnect --> pppd: ovider
And a lot more of those "ovider" in between. What on earth are those "ovider" things? :-?
After upgrade to kernel patch 104: Linux version 2.6.5-7.104-default (geeko@buildhost) (gcc version 3.3.3 (SuSE Linux)) #1 Wed Jul 28 16:42:13 UTC 2004 the string has changed to: --> pppd: Provider --> pppd: Provider --> pppd: Provider The "Mystery of the missing 'P'" has changed its name to "Mastery of the baffling message" :-P However, transmission speed is still slow. -- Cheers, Carlos Robinson
participants (3)
-
Bruce Marshall -
Carlos E. R. -
Patrick Shanahan