Yes, I should have checked bugzilla. However upon doing so I am more confused.
First, the problem described in the referenced bug 55367 seems to be when a MS windows client tries to connect to a Linux dialup server. This situation is not the same as my situation. In my case I have a Linux ppp client (my desktop) trying to connect to my ISP's Linux dialup ppp server. Now while I agree that my problem can be related, the suggested cure of using ppp-2.4.1-3.i386.rpm from rawhide did not fix the problem which leads me to believe something else is occurring. Second, if I run wvdial directly from the command line everything works properly. Since the last thing that wvdial does is to start pppd shouldn't I have the same problem as when pppd starts first and just uses wvdial as a dialer? In both cases pppd is running, but only in the case that pppd initiates the connection do I have a problem. This is why I thought it might just be a configuration problem. R P Herrold wrote: >On Mon, 8 Apr 2002, Paul R. Ganci wrote: > >>Yesterday I set up wvdial to replace chat in order to connect to my ISP. >>When I run wvdial from the command line everything works perfectly. >>However if wvdial is called by pppd from the >>/etc/sysconfig/network-script/ifup-ppp script the connection is >>immediately terminated with "IPCP terminated by peer" and "LCP >>terminated by peer" errors. >> > >Bugzilla is your friend: > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=55367 > -- Paul ([EMAIL PROTECTED]) _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
