[plasma-nm] [Bug 364094] Can't connect to wired network when adding routes.

[Jan Grulich via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364094

Jan Grulich  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #7 from Jan Grulich  ---
I cannot fix this in plasma-nm, you would need to report this problem to
NetworkManager.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 364094] Can't connect to wired network when adding routes.

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364094

--- Comment #6 from ge...@abenthung.name ---
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!

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 364094] Can't connect to wired network when adding routes.

[Jan Grulich via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364094

--- Comment #5 from Jan Grulich  ---
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.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 364094] Can't connect to wired network when adding routes.

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364094

--- Comment #4 from ge...@abenthung.name ---
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]:   [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`

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 364094] Can't connect to wired network when adding routes.

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364094

--- Comment #3 from ge...@abenthung.name ---
`/var/log/syslog/` shows this when adding the route, which looks fine:
-
Jun  8 14:18:16 xxx NetworkManager[1013]:   [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]:   [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]:   [1465388402.6097] device
(eth0): Activation: starting connection 'Kabelnetzwerkverbindung 1'
(d433ee91-c5f6-4d0c-8069-96c5e7d84ffb)
Jun  8 14:20:02 xxx NetworkManager[1013]:   [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]:   [1465388402.6111] device
(eth0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Jun  8 14:20:02 xxx NetworkManager[1013]:   [1465388402.6118] manager:
NetworkManager state is now CONNECTING
Jun  8 14:20:02 xxx NetworkManager[1013]:   [1465388402.6135] device
(eth0): state change: prepare -> config (reason 'none') [40 50 0]
Jun  8 14:20:02 xxx NetworkManager[1013]:   [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]:   [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]:   [1465388402.6255] manager:
NetworkManager state is now CONNECTED_LOCAL
Jun  8 14:20:02 xxx NetworkManager[1013]:   [1465388402.6258] device
(eth0): Activation: failed for connection 'Kabelnetzwerkverbindung 1'
Jun  8 14:20:02 xxx NetworkManager[1013]:   [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]:   [1465388402.6288] policy:
auto-activating connection 'Kabelnetzwerkverbindung 1'
Jun  8 14:20:02 xxx NetworkManager[1013]:   [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]:   [1465388402.6296] device
(eth0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Jun  8 14:20:02 xxx NetworkManager[1013]:   [1465388402.6297] manager:
NetworkManager state is now CONNECTING
Jun  8 14:20:02 xxx NetworkManager[1013]:   [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]:   [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]:   [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]:   [1465388402.6324] manager:
NetworkManager state is now CONNECTED_LOCAL
Jun  8 14:20:02 xxx NetworkManager[1013]:   [1465388402.6327] device
(eth0): Activation: failed for connection 'Kabelnetzwerkverbindung 1'
Jun  8 14:20:02 xxx NetworkManager[1013]:   [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 

[plasma-nm] [Bug 364094] Can't connect to wired network when adding routes.

[Jan Grulich via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364094

--- Comment #2 from Jan Grulich  ---
Could you please provide log from NetworkManager once you try to connect to the
modified connection? Or is there any notification with error?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 364094] Can't connect to wired network when adding routes.

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364094

--- Comment #1 from ge...@abenthung.name ---
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

-- 
You are receiving this mail because:
You are watching all bug changes.