Created attachment 367401 [details] output of NetworkManager Description of problem: I'm using fedora 12. All the packages are the newest from the repo. The NetworkManager can make LAN connection successfully. But it can not make ADSL connection using pppoe. In the DSL tab, I just entered diaup username and password, all other options are with default value. Version-Release number of selected component (if applicable): #rpm -qa|grep NetworkManager NetworkManager-pptp-0.7.996-4.git20090921.fc12.i686 NetworkManager-gnome-0.7.996-5.git20091021.fc12.i686 NetworkManager-vpnc-0.7.996-4.git20090921.fc12.i686 NetworkManager-0.7.996-5.git20091021.fc12.i686 NetworkManager-glib-0.7.996-5.git20091021.fc12.i686 NetworkManager-openvpn-0.7.996-4.git20090923.fc12.i686 #rpm -qa|grep ppp ppp-2.4.4-13.fc12.i686 kernel: kernel-2.6.31.5-96.fc12.i686.PAE #rpm -qa|grep dbus dbus-cxx-doc-0.4.3-1.fc12.noarch dbus-1.2.16-8.fc12.i686 dbus-cxx-0.4.3-1.fc12.i686 dbus-libs-1.2.16-8.fc12.i686 dbus-glib-0.82-2.fc12.i686 How reproducible: Steps to Reproduce: 1. login to gnome desktop 2. edit a ADSL connection entry using pppoe (just enter the username and password) 3. use the entry to connect ISP. Actual results: NetworManager can not connect my ISP in the end Expected results: NetworManager will connect my ISP, and ready for all the desktop network application to be online. Additional info: I use the following step to get some log: # /etc/init.d/NetworkManager stop # NM_PPP_DEBUG=1 NetworkManager --no-daemon 2>&1 | tee /tmp/nm.log output on console: ... NetworkManager: <info> (eth0): device state change: 8 -> 3 (reason 0) NetworkManager: <info> (eth0): deactivating device (reason: 0). -- Error received: Numerical result out of range -- Original message: type=0x19 length=56 flags=<REQUEST,ACK> sequence-nr=1257305830 pid=4196082 NetworkManager: <WARN> check_one_route(): (eth0) error -34 returned from rtnl_route_del(): Sucess NetworkManager: <info> Activation (eth0) starting connection 'unicom' NetworkManager: <info> (eth0): device state change: 3 -> 4 (reason 0) NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started... NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting... NetworkManager: <info> (eth0): device state change: 4 -> 5 (reason 0) NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful. NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete. NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... NetworkManager: <info> (eth0): device state change: 5 -> 7 (reason 0) NetworkManager: <info> Starting pppd connection NetworkManager: <debug> [1257305824.230001] nm_ppp_manager_start(): Command line: /usr/sbin/pppd nodetach lock nodefaultroute debug user 172078001716@201 plugin rp-pppoe.so nic-eth0 noauth nodeflate usepeerdns mru 1492 mtu 1492 lcp-echo-failure 3 lcp-echo-interval 20 ipparam /org/freedesktop/NetworkManager/PPP/0 plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so Plugin rp-pppoe.so loaded. RP-PPPoE plugin version 3.3 compiled against pppd 2.4.4 Plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so loaded. ** Message: nm-ppp-plugin: (plugin_init): initializing NetworkManager: <debug> [1257305824.241839] nm_ppp_manager_start(): ppp started with pid 1813 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) scheduled... ** Message: nm-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection' NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) started... NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) complete. using channel 2 Using interface ppp0 Connect: ppp0 <--> eth0 ** Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase 'establish' sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x5c92c8ac>] rcvd [LCP ConfAck id=0x1 <mru 1492> <magic 0x5c92c8ac>] sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x5c92c8ac>] rcvd [LCP ConfAck id=0x1 <mru 1492> <magic 0x5c92c8ac>] rcvd [LCP ConfReq id=0x1 <mru 1492> <auth pap> <magic 0x5004b3a>] sent [LCP ConfAck id=0x1 <mru 1492> <auth pap> <magic 0x5004b3a>] sent [LCP EchoReq id=0x0 magic=0x5c92c8ac] ** Message: nm-ppp-plugin: (nm_phasechange): status 6 / phase 'authenticate' ** Message: nm-ppp-plugin: (get_credentials): passwd-hook, requesting credentials... NetworkManager: <WARN> pppd_timed_out(): Looks like pppd didn't initialize our dbus module NetworkManager: <info> (eth0): device state change: 7 -> 9 (reason 14) NetworkManager: <info> Marking connection 'unicom' invalid. NetworkManager: <info> Activation (eth0) failed.
My platform is dell 640m. NetworkManager works well with DSL in fedora 10/11
The upstream fix for this should be: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=82011dff04123df5634c3a17ceae19c76c67c9e0
Removed fedora group restriction per discussion on IRC #fedora-devel
Test builds available here: http://koji.fedoraproject.org/koji/taskinfo?taskID=1788689 Would you mind installing those and seeing if they fix the problem? If so, we can try to get these into Fedora 12 before it gets released.
jlaska, notting, warren - we need a vote on whether to make this a blocker, impact is on everyone who uses an ADSL/PPPoE connection direct into their PC (i.e. not via a router) to get online, as I understand it. (Maybe all direct PPPoE connections, dcbw can clarify). jlaska has concerns about accepting changes to NM this late that could potentially change the codepath for _all_ connections. Personally I recognize that but I think I lean to accepting this as a blocker as the impact is sufficiently serious. votes? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
on the impact of the change, dcbw says: <dcbw> adamw: the fix could affect wired 802.1x as well, but the fix ensures the same conditions as pre-patch <dcbw> adamw: basically it loosens conditions for PPPoE but preserves them for 802.1x -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Given we have a fix, I'd take this.
Actual patch used in the build is: http://cvs.fedoraproject.org/viewvc/F-12/NetworkManager/pppoe-auth-fix-82011dff04123d.patch?view=markup
if we get a +1 from jesse or jlaska i think we can put it in... -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
+1 Spoke (okay typed) with Dan on IRC. I'm hesitant to open up NetworkManager at this point if the patches affect common wire{d,less} code paths. However, Dan feels confident with the patch and feels 95% certain the changes are specific to pppoe code paths (and not common code). I'm comfortable taking the patch. Once we have confirmation of the fix, I gather we'll do the tagging? Our fallback should regressions surface during RC validation will be to revert the patch and document the issue.
in that case, adding to the blocker list. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
great, it works! I tried it three times, all succeded. thanks.
Tagged for the release.
(In reply to comment #12) > great, it works! > > I tried it three times, all succeded. Thanks for the quick turnaround on testing!
*** Bug 532046 has been marked as a duplicate of this bug. ***