Re: Fw: [SLE] PPPD 2.4.1 problem with SuSe 8.0 Personal
* Logan
[07-26-02 13:18]: Jun 19 04:17:37 gateway pppd[13228]: pppd 2.4.1 started by root, uid 0 Jun 19 04:17:37 gateway pppd[13228]: Using interface ppp0 Jun 19 04:17:37 gateway pppd[13228]: Connect: ppp0 <--> /dev/ttyS0 Jun 19 04:17:37 gateway pppd[13228]: sent [LCP ConfReq id=0x1
0x0>
<pcomp> <accomp>] Jun 19 04:18:01 gateway pppd[13228]: Hangup (SIGHUP) Jun 19 04:18:01 gateway pppd[13228]: Modem hangup Jun 19 04:18:01 gateway pppd[13228]: Connection terminated. Jun 19 04:18:01 gateway pppd[13228]: Exit. that is EXACTLY the same thing that appeared in my log... and i have no freaking clue... the responses to this is was NOT indepth and said, "i plugged in a pci modem and it was solved." well... i wish i could, because the onboard one is the only softmodem that doesn't have a stable
/etc/wvdial.conf:
[Dialer Defaults]
YaST2 configured = 1
Modem = /dev/ttyS1
Baud = 57600
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2
Init3 =
Area Code =
Phone = **********
Username = ************
Password = ************
Ask Password = 0
Dial Command = ATDT
Stupid Mode = 1
Compuserve = 0
Force Address =
Idle Seconds = 180
DialMessage1 =
DialMessage2 =
#WVDialMon Exec = Netscape -remote "reload()"
ISDN = 0
Auto DNS = 1
Load Predefined Prefix = None
-------------------------------------------------------------
morituri te salutant fur die ganze familie!
----- Original Message -----
From: "SuSEnixER"
port. =( *sigh* see if that makes the wheels spin...
It still looks like it is dropping when ppp tries to connect (the Stupid Mode solution).
Please post the contents of your /etc/wvdial.conf & ~/.kde2/share/config/kppprc
remember to disguise private info. AND trim EVERYTHING except a description of your problem. ie. other people's sigs, unnecessary divider lines, etc... -- Patrick Shanahan Registered Linux User #207535 @ http://counter.li.org
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
with this wvdial.conf, does anyone see a reason why it would be acting the
way it should? i'm STILL unable to connect through linux, and this is
getting very frustrating... not like i have anything else to be doing, but
it is rather weird that i'd have problems with it, esp when there is NO
reason why it should be doing it... all of a sudden connecting then modem
turning off
gateway pppd[13228]: pppd 2.4.1 started by root, uid 0
gateway pppd[13228]: Using interface ppp0
gateway pppd[13228]: Connect: ppp0 <--> /dev/ttyS1
gateway pppd[13228]: sent [LCP ConfReq id=0x1
/etc/wvdial.conf: [Dialer Defaults] YaST2 configured = 1 Modem = /dev/ttyS1 Baud = 57600 Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 Init3 = Area Code = Phone = ********** Username = ************ Password = ************ Ask Password = 0 Dial Command = ATDT Stupid Mode = 1 Compuserve = 0 Force Address = Idle Seconds = 180 DialMessage1 = DialMessage2 = #WVDialMon Exec = Netscape -remote "reload()" ISDN = 0 Auto DNS = 1 Load Predefined Prefix = None
------------------------------------------------------------- morituri te salutant fur die ganze familie!
----- Original Message ----- From: "SuSEnixER"
To: "SuSe - SLE" Sent: Friday, July 26, 2002 4:52 PM Subject: Re: Fw: [SLE] PPPD 2.4.1 problem with SuSe 8.0 Personal * Logan
[07-26-02 13:18]: Jun 19 04:17:37 gateway pppd[13228]: pppd 2.4.1 started by root, uid 0 Jun 19 04:17:37 gateway pppd[13228]: Using interface ppp0 Jun 19 04:17:37 gateway pppd[13228]: Connect: ppp0 <--> /dev/ttyS0 Jun 19 04:17:37 gateway pppd[13228]: sent [LCP ConfReq id=0x1
<pcomp> <accomp>] Jun 19 04:18:01 gateway pppd[13228]: Hangup (SIGHUP) Jun 19 04:18:01 gateway pppd[13228]: Modem hangup Jun 19 04:18:01 gateway pppd[13228]: Connection terminated. Jun 19 04:18:01 gateway pppd[13228]: Exit. that is EXACTLY the same thing that appeared in my log... and i have no freaking clue... the responses to this is was NOT indepth and said, "i plugged in a pci modem and it was solved." well... i wish i could, because the onboard one is the only softmodem that doesn't have a stable
linmodem port. =( *sigh* see if that makes the wheels spin...
It still looks like it is dropping when ppp tries to connect (the Stupid Mode solution).
Please post the contents of your /etc/wvdial.conf & ~/.kde2/share/config/kppprc
remember to disguise private info. AND trim EVERYTHING except a description of your problem. ie. other people's sigs, unnecessary divider lines, etc... -- Patrick Shanahan Registered Linux User #207535 @ http://counter.li.org
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
On Sunday 28 July 2002 14.43, Logan wrote:
is EXACTLY what i see in my kppp/kinternet/wvdial logs...
When you use wvdial you should see things in the log before this. Things like "Dialling" and possibly the answering machine's login prompt. Could you post that, it may be relevant. //Anders
On Sunday 28 July 2002 14.43, Logan wrote:
is EXACTLY what i see in my kppp/kinternet/wvdial logs...
When you use wvdial you should see things in the log before this. Things
"Dialling" and possibly the answering machine's login prompt. Could you
PPP-logfile:
jul 25 03:33:58 linux pppd[1191]: Plugin passwordfd.so loaded
jul 25 03:33:58 linux pppd[1191]: pppd 2.4.1 started by root, uid 0
jul 25 03:33:58 linux pppd[1191]: Perms of /dev/ttyS1 are ok, no 'mesg n'
neccesary
jul 25 03:33:58 linux pppd[1191]: using channel 1
jul 25 03:33:58 linux pppd[1191]: using interface ppp0
jul 25 03:33:58 linux pppd[1191]: connect: ppp0 <--> /dev/ttyS1
jul 25 03:33:58 linux pppd[1191]: sent [LCP ConfRq id=0x1
that, it may be relevant.
//Anders
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
On Sunday 28 July 2002 15.11, Logan wrote:
PPP-logfile:
jul 25 03:33:58 linux pppd[1191]: Plugin passwordfd.so loaded jul 25 03:33:58 linux pppd[1191]: pppd 2.4.1 started by root, uid 0 jul 25 03:33:58 linux pppd[1191]: Perms of /dev/ttyS1 are ok, no 'mesg n' neccesary jul 25 03:33:58 linux pppd[1191]: using channel 1 jul 25 03:33:58 linux pppd[1191]: using interface ppp0 jul 25 03:33:58 linux pppd[1191]: connect: ppp0 <--> /dev/ttyS1 jul 25 03:33:58 linux pppd[1191]: sent [LCP ConfRq id=0x1
<pcomp> <accomp>] jul 25 03:34:45 linux pppd[1191]: Hangup (SIGHUP) jul 25 03:34:45 linux pppd[1191]: modem hangup jul 25 03:34:45 linux pppd[1191]: connection terminated jul 25 03:34:45 linux pppd[1191]: exit ------------------------------------------------------------- morituri te salutant fur die ganze familie! (Those about to die salute you for the whole family???)
Yes, this is what you posted before, but it's useless from a problem solving perspective. It just shows ppp starting but not getting a reply from the remote. I was thinking that the messages from wvdial *before* ppp starts would perhaps show why there's no response. It's a bit of a long shot, I know, but the above from pppd tells us next to nothing. //Anders
Logan wrote:
gateway pppd[13228]: pppd 2.4.1 started by root, uid 0 gateway pppd[13228]: Using interface ppp0 gateway pppd[13228]: Connect: ppp0 <--> /dev/ttyS1 gateway pppd[13228]: sent [LCP ConfReq id=0x1
<pcomp> <accomp>] gateway pppd[13228]: Hangup (SIGHUP) gateway pppd[13228]: Modem hangup gateway pppd[13228]: Connection terminated. gateway pppd[13228]: Exit.
I just checked my log after I got kppp working again after the update. It had the following line before the starting of pppd, or more correctly, the first thing pppd did. Jul 26 09:32:11 jmorris pppd[6796]: Plugin passwordfd.so loaded. Jul 26 09:32:11 jmorris pppd[6796]: pppd 2.4.1 started by joe, uid 500 Also, some thoughts that have bit me in the past. Are you in dialout group? Have you edited the wvdial.conf file and changed the permissions? Should be -rw-r----- 1 root dialout 413 Feb 1 23:21 wvdial.conf (obviously the date will be different). But, if the above plugin is not loading, that would be my first guess. -- Joe & Sesil 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 God, I am what I am.
On Sun, 28 Jul 2002 07:43:05 -0500
"Logan"
about it, but i put down $92 which i shouldn't have spent, but did anyways, to get a working modem for linux because i love the os so much. this is just making me lose faith...
thanks ahead of time logan
Hi, long ago I switched to very simple logon scripts, the way it was originally done. Try this: /etc/ppp/your-ip.chat put your number after ATDT ######################################## TIMEOUT 60 ABORT "NO CARRIER" ABORT BUSY ABORT "NO DIALTONE" ABORT ERROR "" +++\dATZ OK ATDT3550105 CONNECT ####################################### /etc/ppp/your-ip.options ###################################### /dev/ttyS1 115200 crtscts lock your-username@your-ip.com noipdefault defaultroute debug ######################################## /etc/on ####################################### #!/bin/sh # initiate a ppp connection /usr/sbin/pppd connect "/usr/sbin/chat -v -f /etc/ppp/your-ip.chat" \ file /etc/ppp/your-ip.options ######################################### Open an xterm, or console: Just type "on" to bring up a connection, watch the debug output. To get off, hit control-c Your problem sounds like you are giving the wrong logon name, or your pap.secrets isn't setup right. Your logon name is often different from your username, check your ip's howto. -- use Perl; #powerful programmable prestidigitation
participants (4)
-
Anders Johansson
-
Joe & Sesil Morris (NTM)
-
Logan
-
zentara