Re: Problems getting device state change events through

2016-12-16 Thread matti kaasinen
> > 2016-12-15 18:41 GMT+02:00 Dan Williams : > >> > ping started to work after executing >> > > *route add default dev eth0 metric 99* >> > So, everything is fine! >> >> That implies that the default route was not set up correctly >> beforehand. What's the output of "ip route" before you add that

Re: Problems getting device state change events through

2016-12-15 Thread matti kaasinen
Hi Dan, Story below is kind of follow up of my late query referenced: https://mail.gnome.org/archives/networkmanager-list/2016-April/msg00055.html 2016-12-14 16:36 GMT+02:00 matti kaasinen : > I used to have NM 0.9.8.10 together with dhclient. Now I upgraded to NM > 1.0.10 together with internal

Problems getting device state change events through

2016-12-14 Thread matti kaasinen
Hi! I used to have NM 0.9.8.10 together with dhclient. Now I upgraded to NM 1.0.10 together with internal dhcp client. Old system had very cumbersome network up sequence in order to preserve dhcp provided IP. Both set-ups have also avahi/avahi-auto-ip running for providing IPv4LL addresses trying