From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020809
Description of problem:
"redhat-config-network-1.1.16-1" is not able to activate an existing modem
connection. The modem is detected correctly, but after setting up the Internet
connection, activating the very same connection does not work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Launch "redhat-config-network-1.1.16-1".
2. Set up modem and ISP (works fine!).
3. Try to activate the phone line.
Actual Results: None. After some time, the message that the PPP connection
cannot be established is issued. The log file shows:
Aug 17 15:50:56 banach ifup-ppp: pppd started for ppp0 on /dev/ttyS4 at 115200
Aug 17 15:50:56 banach pppd: pppd 2.4.1 started by root, uid 0
Aug 17 15:50:57 banach pppd: Connect script failed
Aug 17 15:50:58 banach pppd: Exit.
Expected Results: The modem should dial up, and Internet access should work.
The "wvdial.conf" file which has been produced by
"redhat-config-network-1.1.16-1" is correct and works! Dialling up manually as
root via wvdial leads to a working Internet connection. Seems like the interface
from "redhat-config-network-1.1.16-1" to "wvdial" is not set up properly. A
similar bug (#71122) has just been reported for "Limbo". However, in that case,
it is claimed that "redhat-config-network" does even detect the modem which is
quite different from the present case - hence a separate bug report :)
However, in that case, it is claimed that "redhat-config-network" does #not#
even detect the modem which is quite different from the present case - hence a
separate bug report :)
can you attach your ifcfg-ppp0, please?
Created attachment 72484 [details]
PPP configuration script
this is also true in 1.2.58: modem is activated but not set "active" so one has
to close connection by kill ppp connection.
Created attachment 95623 [details]
The same bug? Activate does not work on existing ppp0. ppp0 was deleted and
reconfigured. When apply was hit, the attached bug message was generated. Had
to kill the app to close it.
See attachment #95623 [details]