364094 – Can't connect to wired network when adding routes.

Bug 364094 - Can't connect to wired network when adding routes.

Summary: Can't connect to wired network when adding routes.

Status:	RESOLVED INTENTIONAL

Alias:	None

Product:	plasma-nm
Classification:	Plasma
Component:	general (show other bugs)
Version:	5.5.5
Platform:	Ubuntu Linux

Importance:	NOR normal
Target Milestone:	---
Assignee:	Lukáš Tinkl

URL:
Keywords:

Depends on:
Blocks:

Reported:	2016-06-08 11:25 UTC by georg
Modified:	2016-06-14 12:04 UTC (History)
CC List:	1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Screenshot showing the not-working-setup (365.20 KB, image/png) 2016-06-08 11:25 UTC, georg	Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.

Description georg 2016-06-08 11:25:39 UTC

Created attachment 99411 [details]
Screenshot showing the not-working-setup

When adding a static route with the "Verbindungs-Editor" in KDE, the network manager can't connect to the network anymore.

Adding a route manually with `route` works as expected. e.g. `sudo route add 10.196.0.194 gw 192.168.0.100 eth0`

I have pretty much default network from a cable provider. My computer has the static IPv4 address 192.168.0.5. The default gateway is 192.168.0.1 Network-Mask: 255.255.255.0 this works so far. I have a second router with IP 192.168.0.100 where a device with IP 10.196.0.194 is connected. Thus I used to add a static route for this address using 192.168.0.100 as Gateway.

Before Kubuntu 16.04 I had added a route with plasma-nm and it worked properly. Since 16.04 I can add the route with plasma-nm, but when doing so the network is not connecting anymore.

Kubuntu 16.04 (Upgraded from 15.10)
KDE Frameworks 5.18.0
Qt 5.5.1 (kompiliert gegen 5.5.1)
Das xcb Fenstersystem

Comment 1 georg 2016-06-08 11:28:00 UTC

By the way: translating programm-names in different languages is really not a good idea. Another thing: it's really hard to figure out whats the programms name, causing the problem. It's almost impossible to translate the german programm name "Verbindungs Editor" into "plasma-nm". THis should at least stand in the "About" Section of every programm....

Comment 2 Jan Grulich 2016-06-08 11:59:39 UTC

Could you please provide log from NetworkManager once you try to connect to the modified connection? Or is there any notification with error?

Comment 3 georg 2016-06-08 12:22:56 UTC

`/var/log/syslog/` shows this when adding the route, which looks fine:
-----------------
Jun  8 14:18:16 xxx NetworkManager[1013]: <info>  [1465388296.3223] keyfile: update /etc/NetworkManager/system-connections/Kabelnetzwerkverbindung 1 (d433ee91-c5f6-4d0c-8069-96c5e7d84ffb,"Kabelnetzwerkverbindung 1")
Jun  8 14:18:16 xxx NetworkManager[1013]: <info>  [1465388296.3240] audit: op="connection-update" uuid="d433ee91-c5f6-4d0c-8069-96c5e7d84ffb" name="Kabelnetzwerkverbindung 1" pid=11566 uid=1000 result="success"
Jun  8 14:18:16 xxx org.kde.kdeconnect[3001]: kdeconnect.core: Broadcasting identity packet

------------------


When trying to connect:
------------------
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6097] device (eth0): Activation: starting connection 'Kabelnetzwerkverbindung 1' (d433ee91-c5f6-4d0c-8069-96c5e7d84ffb)
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6103] audit: op="connection-activate" uuid="d433ee91-c5f6-4d0c-8069-96c5e7d84ffb" name="Kabelnetzwerkverbindung 1" pid=3114 uid=1000 result="success"
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6111] device (eth0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6118] manager: NetworkManager state is now CONNECTING
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6135] device (eth0): state change: prepare -> config (reason 'none') [40 50 0]
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6150] device (eth0): state change: config -> ip-config (reason 'none') [50 70 0]
Jun  8 14:20:02 xxx avahi-daemon[870]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.11.
Jun  8 14:20:02 xxx avahi-daemon[870]: New relevant interface eth0.IPv4 for mDNS.
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6253] device (eth0): state change: ip-config -> failed (reason 'config-failed') [70 120 4]
Jun  8 14:20:02 xxx avahi-daemon[870]: Registering new address record for 192.168.0.11 on eth0.IPv4.
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6255] manager: NetworkManager state is now CONNECTED_LOCAL
Jun  8 14:20:02 xxx NetworkManager[1013]: <warn>  [1465388402.6258] device (eth0): Activation: failed for connection 'Kabelnetzwerkverbindung 1'
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6265] device (eth0): state change: failed -> disconnected (reason 'none') [120 30 0]
Jun  8 14:20:02 xxx avahi-daemon[870]: Withdrawing address record for 192.168.0.11 on eth0.
Jun  8 14:20:02 xxx avahi-daemon[870]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.11.
Jun  8 14:20:02 xxx avahi-daemon[870]: Interface eth0.IPv4 no longer relevant for mDNS.
Jun  8 14:20:02 xxx whoopsie[881]: [14:20:02] Cannot reach: https://daisy.ubuntu.com
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6288] policy: auto-activating connection 'Kabelnetzwerkverbindung 1'
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6294] device (eth0): Activation: starting connection 'Kabelnetzwerkverbindung 1' (d433ee91-c5f6-4d0c-8069-96c5e7d84ffb)
Jun  8 14:20:02 xxx whoopsie[881]: [14:20:02] Cannot reach: https://daisy.ubuntu.com
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6296] device (eth0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6297] manager: NetworkManager state is now CONNECTING
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6302] device (eth0): state change: prepare -> config (reason 'none') [40 50 0]
Jun  8 14:20:02 xxx avahi-daemon[870]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.11.
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6305] device (eth0): state change: config -> ip-config (reason 'none') [50 70 0]
Jun  8 14:20:02 xxx avahi-daemon[870]: New relevant interface eth0.IPv4 for mDNS.
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6322] device (eth0): state change: ip-config -> failed (reason 'config-failed') [70 120 4]
Jun  8 14:20:02 xxx avahi-daemon[870]: Registering new address record for 192.168.0.11 on eth0.IPv4.
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6324] manager: NetworkManager state is now CONNECTED_LOCAL
Jun  8 14:20:02 xxx NetworkManager[1013]: <warn>  [1465388402.6327] device (eth0): Activation: failed for connection 'Kabelnetzwerkverbindung 1'
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6335] device (eth0): state change: failed -> disconnected (reason 'none') [120 30 0]
Jun  8 14:20:02 xxx whoopsie[881]: [14:20:02] Cannot reach: https://daisy.ubuntu.com
Jun  8 14:20:02 xxx avahi-daemon[870]: Withdrawing address record for 192.168.0.11 on eth0.
Jun  8 14:20:02 xxx avahi-daemon[870]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.11.
Jun  8 14:20:02 xxx avahi-daemon[870]: Interface eth0.IPv4 no longer relevant for mDNS.
Jun  8 14:20:02 xxx whoopsie[881]: [14:20:02] Cannot reach: https://daisy.ubuntu.com
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6379] policy: auto-activating connection 'Kabelnetzwerkverbindung 1'
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6390] device (eth0): Activation: starting connection 'Kabelnetzwerkverbindung 1' (d433ee91-c5f6-4d0c-8069-96c5e7d84ffb)
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6392] device (eth0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6394] manager: NetworkManager state is now CONNECTING
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6400] device (eth0): state change: prepare -> config (reason 'none') [40 50 0]
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6404] device (eth0): state change: config -> ip-config (reason 'none') [50 70 0]
Jun  8 14:20:02 xxx avahi-daemon[870]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.11.
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6418] device (eth0): state change: ip-config -> failed (reason 'config-failed') [70 120 4]
Jun  8 14:20:02 xxx whoopsie[881]: [14:20:02] Cannot reach: https://daisy.ubuntu.com
Jun  8 14:20:02 xxx whoopsie[881]: [14:20:02] Cannot reach: https://daisy.ubuntu.com
Jun  8 14:20:02 xxx avahi-daemon[870]: New relevant interface eth0.IPv4 for mDNS.
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6421] manager: NetworkManager state is now CONNECTED_LOCAL
Jun  8 14:20:02 xxx avahi-daemon[870]: Registering new address record for 192.168.0.11 on eth0.IPv4.
Jun  8 14:20:02 xxx NetworkManager[1013]: <warn>  [1465388402.6424] device (eth0): Activation: failed for connection 'Kabelnetzwerkverbindung 1'
Jun  8 14:20:02 xxx whoopsie[881]: [14:20:02] Cannot reach: https://daisy.ubuntu.com
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6430] device (eth0): state change: failed -> disconnected (reason 'none') [120 30 0]
Jun  8 14:20:02 xxx avahi-daemon[870]: Withdrawing address record for 192.168.0.11 on eth0.
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6472] policy: auto-activating connection 'Kabelnetzwerkverbindung 1'
Jun  8 14:20:02 xxx avahi-daemon[870]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.11.
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6483] device (eth0): Activation: starting connection 'Kabelnetzwerkverbindung 1' (d433ee91-c5f6-4d0c-8069-96c5e7d84ffb)
Jun  8 14:20:02 xxx avahi-daemon[870]: Interface eth0.IPv4 no longer relevant for mDNS.
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6485] device (eth0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6487] manager: NetworkManager state is now CONNECTING
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6494] device (eth0): state change: prepare -> config (reason 'none') [40 50 0]
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6498] device (eth0): state change: config -> ip-config (reason 'none') [50 70 0]
Jun  8 14:20:02 xxx whoopsie[881]: [14:20:02] Cannot reach: https://daisy.ubuntu.com
Jun  8 14:20:02 xxx avahi-daemon[870]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.11.
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6519] device (eth0): state change: ip-config -> failed (reason 'config-failed') [70 120 4]
Jun  8 14:20:02 xxx whoopsie[881]: [14:20:02] Cannot reach: https://daisy.ubuntu.com
Jun  8 14:20:02 xxx whoopsie[881]: message repeated 2 times: [ [14:20:02] Cannot reach: https://daisy.ubuntu.com]
Jun  8 14:20:02 xxx avahi-daemon[870]: New relevant interface eth0.IPv4 for mDNS.
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6521] manager: NetworkManager state is now CONNECTED_LOCAL
Jun  8 14:20:02 xxx avahi-daemon[870]: Registering new address record for 192.168.0.11 on eth0.IPv4.
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6523] policy: disabling autoconnect for connection 'Kabelnetzwerkverbindung 1'.
Jun  8 14:20:02 xxx NetworkManager[1013]: <warn>  [1465388402.6526] device (eth0): Activation: failed for connection 'Kabelnetzwerkverbindung 1'
Jun  8 14:20:02 xxx avahi-daemon[870]: Withdrawing address record for 192.168.0.11 on eth0.
Jun  8 14:20:02 xxx NetworkManager[1013]: <info>  [1465388402.6546] device (eth0): state change: failed -> disconnected (reason 'none') [120 30 0]
Jun  8 14:20:02 xxx avahi-daemon[870]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.11.
Jun  8 14:20:02 xxx avahi-daemon[870]: Interface eth0.IPv4 no longer relevant for mDNS.
Jun  8 14:20:02 xxx named[948]: no longer listening on 192.168.0.11#53
Jun  8 14:20:02 xxx org.kde.kdeconnect[3001]: "Keine derartige Schnittstelle »org.freedesktop.DBus.Properties« des Objekts im Pfad /org/freedesktop/NetworkManager/ActiveConnection/9"
Jun  8 14:20:02 xxx org.freedesktop.Telepathy.AccountManager[3001]: (process:3103): libnm-glib-WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/9: Keine derartige Schnittstelle ?org.freedesktop.DBus.Properties? des Objekts im Pfad /org/freedesktop/NetworkManager/ActiveConnection/9
Jun  8 14:20:02 xxx org.freedesktop.Telepathy.AccountManager[3001]: message repeated 3 times: [ (process:3103): libnm-glib-WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/9: Keine derartige Schnittstelle ?org.freedesktop.DBus.Properties? des Objekts im Pfad /org/freedesktop/NetworkManager/ActiveConnection/9]
Jun  8 14:20:02 xxx org.freedesktop.Telepathy.AccountManager[3001]: (process:3103): libnm-glib-WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/10: Keine derartige Schnittstelle ?org.freedesktop.DBus.Properties? des Objekts im Pfad /org/freedesktop/NetworkManager/ActiveConnection/10
Jun  8 14:20:02 xxx org.freedesktop.Telepathy.AccountManager[3001]: message repeated 3 times: [ (process:3103): libnm-glib-WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/10: Keine derartige Schnittstelle ?org.freedesktop.DBus.Properties? des Objekts im Pfad /org/freedesktop/NetworkManager/ActiveConnection/10]
Jun  8 14:20:02 xxx org.freedesktop.Telepathy.AccountManager[3001]: (process:3103): libnm-glib-WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/11: Keine derartige Schnittstelle ?org.freedesktop.DBus.Properties? des Objekts im Pfad /org/freedesktop/NetworkManager/ActiveConnection/11
Jun  8 14:20:02 xxx org.freedesktop.Telepathy.AccountManager[3001]: message repeated 4 times: [ (process:3103): libnm-glib-WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/11: Keine derartige Schnittstelle ?org.freedesktop.DBus.Properties? des Objekts im Pfad /org/freedesktop/NetworkManager/ActiveConnection/11]
Jun  8 14:20:02 xxx org.kde.kdeconnect[3001]: "Keine derartige Schnittstelle »org.freedesktop.DBus.Properties« des Objekts im Pfad /org/freedesktop/NetworkManager/ActiveConnection/10"
Jun  8 14:20:02 xxx org.kde.kdeconnect[3001]: "Keine derartige Schnittstelle »org.freedesktop.DBus.Properties« des Objekts im Pfad /org/freedesktop/NetworkManager/ActiveConnection/11"
Jun  8 14:20:25 xxx org.kde.KScreen[3001]: kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: "eDP1" ) ( "eDP1" ) to KScreen::Output(Id: 67 , Name: "eDP1" ) ( "eDP1" )

Comment 4 georg 2016-06-08 12:28:24 UTC

By the way, the following error message also appears, when no route is entered. (The network works flawlessly then anyway):

------------
Jun 08 14:26:48 xxx nm-dispatcher[12169]: req:1 'up' [eth0], "/etc/NetworkManager/dispatcher.d/01ifupdown": complete: failed with Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1.
Jun 08 14:26:48 xxx NetworkManager[1013]: <warn>  [1465388808.9901] dispatcher: (25) 01ifupdown failed (failed): Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1.
------------

I think the problem might be with messages from `org.kde.kdeconnect`

Comment 5 Jan Grulich 2016-06-13 10:12:03 UTC

Could you please verify whether all your IPv4 addresses/routes are correct when you run "nmcli connection show your_connection_name"? If they are correct, then it means that we (from plasma-nm) set it correctly and there is a problem in NetworkManager and not in plasma-nm.

Comment 6 georg 2016-06-14 08:25:15 UTC

Here the relevant output of the command `nmcli connection show Kabel` where "Kabel is the name of my connection:

----------------------
ipv4.addresses:                         192.168.0.11/24
ipv4.gateway:                           192.168.0.1
ipv4.routes:                            { ip = 10.196.0.194/8, nh = 192.168.0.100 }
----------------------

This helped me to figure a working resolution:
When I change the Route to one of the following pairs it works:
* IP: 10.0.0.0, SubnetMask: 255.0.0.0
* IP: 10.196.0.194, SubnetMask: 255.255.255.255

With one of this configuration the `nmcli`-command gives me:
----------------------
ipv4.addresses:                         192.168.0.11/24
ipv4.gateway:                           192.168.0.1
ipv4.routes:                            { ip = 10.0.0.0/8, nh = 192.168.0.100 }
----------------------
OR
----------------------
ipv4.addresses:                         192.168.0.11/24
ipv4.gateway:                           192.168.0.1
ipv4.routes:                            { ip = 10.196.0.194/32, nh = 192.168.0.100 }
----------------------


However, before the upgrade it also worked with the pair [IP: 10.196.0.194, SubnetMask: 255.0.0.0].
It's upon you to leave it, or fix it, since this was clearly a misconfiguration. (A error/warning message would be nice though ;-)

THanks for your help!

Comment 7 Jan Grulich 2016-06-14 12:04:48 UTC

I cannot fix this in plasma-nm, you would need to report this problem to NetworkManager.