RE: networkmanager-0.9.8.9 will not connect to a wired network

[John Frankish <j-frankish slb com>]

> > > On Tue, 2014-04-22 at 10:05 +0000, John Frankish wrote:
> > > > I compiled networkmanager-0.9.8.9 from source to /usr/local to use dhcpcd (also compiled from source).
> > > >
> > > > Since networkmanager configured as above looks for /usr/local/etc/hosts, I adjusted the source to 
> > > > look at /etc/hosts (it already knew to look for /etc/resolv.conf).
> > > >
> > > > Run from the console, neworkmanager looks as though it connects to an ipv4 wired network (I've tried 
> > > > two different networks), modifies
> /etc/resolv.conf accordingly, but it does not actually connect -I cannot ping the router nor google.com.
> > > > Dhcpcd run alone from the console connects without problems.
> > > >
> > > > This is the same problem I experienced using networkmanager-0.9.8.8 reported in another thread.
> > > >
> > > > I've attached the networkmanager debug output and the strace output, but neither seem to give a clue 
> > > > as to the problem - I believe that either networkmanager is trying to write something to 
> > > > /usr/local/etc that is in /etc (or vice versa) or there is some kind of linux-pam/polkit 
> > > > permissionserror, but I cannot see evidence of either in the debug output.
> > > >
> > > > From the debug snippet below things look to have worked, but they didn't - any troubleshooting hints 
> > > > would be gratefully received.
> > >
> > > The x.x.x.x/0 bits are likely the problem.  Let's investigate why
> > > that's happening especially since NetworkManager says it got the
> > > right prefix from dhcpcd.
> > >
> > > Would you mind applying the attached patch to your sources?  Then
> > > re-run the test and reply with the output so we can debug a bit further.
> >
> > One more thing, when things aren't working, can you provide the output
> > of:
> >
> > ip addr
> > ip route
> Thanks for the reply and the patch
>
> The patch applied cleanly, but unfortunately things still do not work - debug
> output attached.
>
> My system does not have the "ip" command, but the "route" command
> produces the following:
>
> $ route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> default         10.180.20.1     0.0.0.0         UG    0      0        0 eth0
> 10.180.20.1     *               255.255.255.255 UH    0      0        0 eth0
> 127.0.0.1       *               255.255.255.255 UH    0      0        0 lo
>
> Shouldn't that be 255.255.255.0?
I compiled iproute2 - the output is pasted below.

From the comparison of NetworkManager (not working) to uphcpdc (working), it looks like NetworkManager is 
trying to assign a static ip address?

Regards
John
----------
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default 
    link/ether da:99:56:25:5d:6b brd ff:ff:ff:ff:ff:ff
3: tunl0: <NOARP> mtu 1480 qdisc noop state DOWN group default 
    link/ipip 0.0.0.0 brd 0.0.0.0
4: ip_vti0: <NOARP> mtu 1500 qdisc noop state DOWN group default 
    link/ipip 0.0.0.0 brd 0.0.0.0
5: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 24:b6:fd:fa:e1:60 brd ff:ff:ff:ff:ff:ff

$ ip route [NetworkManager]
default via 10.180.20.1 dev eth0  proto static 
10.180.20.1 dev eth0  proto static  scope link 
127.0.0.1 dev lo  scope link

$ ip route [udhcpc]
default via 10.180.20.1 dev eth0 
10.180.20.0/24 dev eth0  proto kernel  scope link  src 10.180.20.126 
127.0.0.1 dev lo  scope link