Public bug reported:
Binary package hint: network-manager
This is 9.10 beta with updates.
I had to use pppoeconf on the command-line to connect to internet because
network-manager can't connect.
With 9.10 beta i couldn't connect due to a strange error message from
network-manager.
i ran pppoeconf and connected, upgraded, the error message is gone. so a
problem less.
then i tried to remove all the files that pppoeconf created to get a clean
environment. I think I did it.
then configured network-manager again, but it still can't connect.
all is going OK until the point where it should actually connect and that
fails, it just says it can't connect, no error message.
in syslog is written:
Oct 10 23:12:30 papillon NetworkManager: <info> Activation (eth0) starting
connection 'DSL connection 1'
Oct 10 23:12:30 papillon NetworkManager: <info> (eth0): device state change: 3
-> 4 (reason 0)
Oct 10 23:12:30 papillon NetworkManager: <info> Activation (eth0) Stage 1 of 5
(Device Prepare) scheduled...
Oct 10 23:12:30 papillon NetworkManager: <info> Activation (eth0) Stage 1 of 5
(Device Prepare) started...
Oct 10 23:12:30 papillon NetworkManager: <info> Activation (eth0) Stage 2 of 5
(Device Configure) scheduled...
Oct 10 23:12:30 papillon NetworkManager: <info> Activation (eth0) Stage 1 of 5
(Device Prepare) complete.
Oct 10 23:12:30 papillon NetworkManager: <info> Activation (eth0) Stage 2 of 5
(Device Configure) starting...
Oct 10 23:12:30 papillon NetworkManager: <info> (eth0): device state change: 4
-> 5 (reason 0)
Oct 10 23:12:30 papillon NetworkManager: <info> Activation (eth0) Stage 2 of 5
(Device Configure) successful.
Oct 10 23:12:30 papillon NetworkManager: <info> Activation (eth0) Stage 3 of 5
(IP Configure Start) scheduled.
Oct 10 23:12:30 papillon NetworkManager: <info> Activation (eth0) Stage 2 of 5
(Device Configure) complete.
Oct 10 23:12:30 papillon NetworkManager: <info> Activation (eth0) Stage 3 of 5
(IP Configure Start) started...
Oct 10 23:12:30 papillon NetworkManager: <info> (eth0): device state change: 5
-> 7 (reason 0)
Oct 10 23:12:30 papillon NetworkManager: <info> Starting pppd connection
Oct 10 23:12:30 papillon NetworkManager: <debug> [1255209150.738329]
nm_ppp_manager_start(): Command line: /usr/sbin/pppd nodetach lock
nodefaultroute user #### plugin rp-pppoe.so nic-eth0 rp_pppoe_service ####
noauth nodeflate usepeerdns mru 1492 mtu 1492 lcp-echo-failure 3
lcp-echo-interval 20 ipparam /org/freedesktop/NetworkManager/PPP/5 plugin
/usr/lib/pppd/2.4.4/nm-pppd-plugin.so
Oct 10 23:12:30 papillon NetworkManager: <debug> [1255209150.793118]
nm_ppp_manager_start(): ppp started with pid 2913
Oct 10 23:12:30 papillon NetworkManager: <info> Activation (eth0) Stage 4 of 5
(IP6 Configure Get) scheduled...
Oct 10 23:12:30 papillon NetworkManager: <info> Activation (eth0) Stage 3 of 5
(IP Configure Start) complete.
Oct 10 23:12:30 papillon NetworkManager: <info> Activation (eth0) Stage 4 of 5
(IP6 Configure Get) started...
Oct 10 23:12:30 papillon NetworkManager: <info> Activation (eth0) Stage 4 of 5
(IP6 Configure Get) complete.
Oct 10 23:12:30 papillon pppd[2913]: Plugin rp-pppoe.so loaded.
Oct 10 23:12:30 papillon pppd[2913]: RP-PPPoE plugin version 3.8p compiled
against pppd 2.4.5
Oct 10 23:12:30 papillon pppd[2913]: Plugin
/usr/lib/pppd/2.4.4/nm-pppd-plugin.so loaded.
Oct 10 23:12:31 papillon pppd[2913]: pppd 2.4.5 started by root, uid 0
Oct 10 23:12:31 papillon pppd[2913]: PPP session is 2706
Oct 10 23:12:31 papillon pppd[2913]: Connected to <MAC> via interface eth0
Oct 10 23:12:31 papillon pppd[2913]: Using interface ppp0
Oct 10 23:12:31 papillon pppd[2913]: Connect: ppp0 <--> eth0
Oct 10 23:12:31 papillon NetworkManager: SCPlugin-Ifupdown: devices added
(path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Oct 10 23:12:31 papillon NetworkManager: SCPlugin-Ifupdown: device added
(path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration
found.
Oct 10 23:12:51 papillon NetworkManager: <WARN> pppd_timed_out(): Looks like
pppd didn't initialize our dbus module
Oct 10 23:12:51 papillon NetworkManager: <info> (eth0): device state change: 7
-> 9 (reason 14)
Oct 10 23:12:51 papillon NetworkManager: <info> Marking connection 'DSL
connection 1' invalid.
Oct 10 23:12:51 papillon NetworkManager: <info> Activation (eth0) failed.
Oct 10 23:12:51 papillon NetworkManager: <info> (eth0): device state change: 9
-> 3 (reason 0)
Oct 10 23:12:51 papillon NetworkManager: <info> (eth0): deactivating device
(reason: 0).
Oct 10 23:12:53 papillon NetworkManager: <debug> [1255209173.002033]
ensure_killed(): waiting for ppp pid 2913 to exit
Oct 10 23:12:53 papillon NetworkManager: <debug> [1255209173.259510]
ensure_killed(): ppp pid 2913 cleaned up
Oct 10 23:12:53 papillon NetworkManager: SCPlugin-Ifupdown: devices removed
(path: /sys/devices/virtual/net/ppp0, iface: ppp0)
-------------------
i tried to start the pppd command-line listed in this log by hand, and i
get (interesting part only):
** Message: nm-ppp-plugin: (get_credentials): passwd-hook, requesting
credentials...
** (process:2930): WARNING **: nm-ppp-plugin: (get_credentials): could
not get secrets: (19) Method "NeedSecrets" with signature "" on
interface "org.freedesktop.NetworkManager.PPP" doesn't exist
Unable to obtain CHAP password for #### on ##### from plugin
No CHAP secret found for authenticating us to ####
CHAP authentication failed: Access Denied
CHAP authentication failed
ProblemType: Bug
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Sat Oct 10 23:32:14 2009
DistroRelease: Ubuntu 9.10
IpRoute:
213.250.19.90 dev ppp0 proto kernel scope link src 95.176.196.184
default dev ppp0 scope link
Package: network-manager 0.8~a~git.20091005t192303.1d28ad1-0ubuntu2
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.43-generic
RfKill:
SourcePackage: network-manager
Uname: Linux 2.6.31-13-generic i686
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386
--
network-manager: can't connect using PPPoE
https://bugs.launchpad.net/bugs/448287
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
