[Bug 902650] New: wicked: No default route using static IP/route
http://bugzilla.opensuse.org/show_bug.cgi?id=902650 Bug ID: 902650 Summary: wicked: No default route using static IP/route Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: armv7 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: afaerber@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Since a few weeks in Factory I do not get a default route set up anymore on one of my devices running Factory. force:~ # cat /etc/sysconfig/network/routes default 192.168.1.1 - - Config options were verified using YaST. The following command sets up the route okay when run manually: ip route add default via 192.168.1.1 Two differences stand out between this and other devices running same Factory: 1) To get a non-random MAC address, it uses LLADDR='xx:xx:xx:xx:xx:xx' in ifcfg-enp1s0. 2) To avoid SSH connections breaking off, I need to run ethtool -K enp1s0 tx off. Possibly related to bug #821077 (default route detected/displayed wrong)? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=902650
Bernhard Wiedemann
http://bugzilla.opensuse.org/show_bug.cgi?id=902650
Marius Tomaschewski
Since a few weeks in Factory I do not get a default route set up anymore on one of my devices running Factory.
force:~ # cat /etc/sysconfig/network/routes default 192.168.1.1 - -
Config options were verified using YaST.
The following command sets up the route okay when run manually: ip route add default via 192.168.1.1
Two differences stand out between this and other devices running same Factory:
1) To get a non-random MAC address, it uses LLADDR='xx:xx:xx:xx:xx:xx' in ifcfg-enp1s0. 2) To avoid SSH connections breaking off, I need to run ethtool -K enp1s0 tx off.
Possibly related to bug #821077 (default route detected/displayed wrong)?
No, bug #821077 is about deprecated "route" command line utility. It is rather a dup of bug #900112, fixed in wicked 0.6.12. - ethernet: Do not fail when ETHTOOL_GSET/SSET fails - dbus: omit ethernet speed, duplex, autoneg properties if not supported by the driver - ethtool: independent ioctl requests are handled separately: if one fails it does not stop the following ones Could you verify it on armv7? Further, please provide /etc/sysconfig/network/ifcfg-enp1s0 (IPADDR or REMOTE_IPADDR have to match 192.168.1.1). Best would be to attach files as described at: http://en.opensuse.org/openSUSE:Bugreport_wicked -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=902650
--- Comment #2 from Andreas Färber
It is rather a dup of bug #900112, fixed in wicked 0.6.12.
- ethernet: Do not fail when ETHTOOL_GSET/SSET fails - dbus: omit ethernet speed, duplex, autoneg properties if not supported by the driver - ethtool: independent ioctl requests are handled separately: if one fails it does not stop the following ones
Could you verify it on armv7?
The report is against 0.6.12: i | libwicked-0-6 | Paket | 0.6.12-1.1 | armv7hl | openSUSE-Factory-repo-oss i | wicked | Paket | 0.6.12-1.1 | armv7hl | openSUSE-Factory-repo-oss i | wicked-service | Paket | 0.6.12-1.1 | armv7hl | openSUSE-Factory-repo-oss Also, for testing more recent versions, please add an openSUSE_Factory_ARM repository in network:wicked:factory and possibly network:wicked:master. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=902650
--- Comment #3 from Marius Tomaschewski
The report is against 0.6.12:
Then please provide full logs as requested in http://en.opensuse.org/openSUSE:Bugreport_wicked
Also, for testing more recent versions, please add an openSUSE_Factory_ARM repository in network:wicked:factory and possibly network:wicked:master.
added to both. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=902650
--- Comment #4 from Andreas Färber
Further, please provide /etc/sysconfig/network/ifcfg-enp1s0 (IPADDR or REMOTE_IPADDR have to match 192.168.1.1).
Like I indicated, it is a regression. BOOTPROTO='static' MTU='' REMOTE_IPADDR='' STARTMODE='auto' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='192.168.1.164/24' NAME='' NETWORK='' LLADDR='XX:XX:XX:XX:XX:XX'
Best would be to attach files as described at: http://en.opensuse.org/openSUSE:Bugreport_wicked
From wicked show-config:
<interface origin="compat:/etc/sysconfig/network/ifcfg-enp1s0"
uuid="21b30000-3c7b-0600-a400-0000e88c4f54">
<name>enp1s0</name>
<control>
<mode>boot</mode>
<link-detection>
<require-link/>
</link-detection>
</control>
<ethernet>
<address>XX:XX:XX:XX:XX:XX</address>
</ethernet>
<link/>
<ipv4>
<enabled>true</enabled>
<forwarding>false</forwarding>
<arp-verify>true</arp-verify>
<arp-notify>false</arp-notify>
</ipv4>
ipv4:static
<address>
<local>192.168.1.164/24</local>
</address>
<ipv6>
<enabled>true</enabled>
<forwarding>false</forwarding>
</ipv6>
</interface>
andreas@force:~> ip addr show
1: lo:
http://bugzilla.opensuse.org/show_bug.cgi?id=902650
--- Comment #5 from Andreas Färber
http://bugzilla.opensuse.org/show_bug.cgi?id=902650
Andreas Färber
http://bugzilla.opensuse.org/show_bug.cgi?id=902650
--- Comment #7 from Andreas Färber
http://bugzilla.opensuse.org/show_bug.cgi?id=902650
Marius Tomaschewski
(In reply to Marius Tomaschewski from comment #1)
Further, please provide /etc/sysconfig/network/ifcfg-enp1s0 (IPADDR or REMOTE_IPADDR have to match 192.168.1.1).
Like I indicated, it is a regression.
IMO it is not. Unfortunately you still didn't provided what I've requested but a filtered version only. *Please* stop interpreting yourself and provide the logs -- otherwise I can't reproduce it. (In reply to Andreas Färber from comment #7)
The debug log looks to me as if the default route is parsed correctly but assigned to interface eth0 (USB ethernet adapter, not attached) rather than enp1s0.
Then there are two valid config files and eth0 matches it too => IMO INVALID. Attach full config + logs as requested please. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=902650
--- Comment #10 from Marius Tomaschewski
(In reply to Andreas Färber from comment #4)
(In reply to Marius Tomaschewski from comment #1)
Further, please provide /etc/sysconfig/network/ifcfg-enp1s0 (IPADDR or REMOTE_IPADDR have to match 192.168.1.1).
Like I indicated, it is a regression.
IMO it is not.
See also: http://bugzilla.suse.com/show_bug.cgi?id=866250 Use yast2-network 3.1.102 where it is fixed. Not setting the interface in the routes file were and will always cause random results. We can try to catch some cases as good as possible, but incomplete config -> incomplete configuration will remain. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=902650
--- Comment #11 from Marius Tomaschewski
http://bugzilla.opensuse.org/show_bug.cgi?id=902650
Andreas Färber
(In reply to Andreas Färber from comment #4)
(In reply to Marius Tomaschewski from comment #1)
Further, please provide /etc/sysconfig/network/ifcfg-enp1s0 (IPADDR or REMOTE_IPADDR have to match 192.168.1.1).
Like I indicated, it is a regression.
IMO it is not.
That's not a matter of opinion. Worked before, now doesn't => regression.
Unfortunately you still didn't provided what I've requested but a filtered version only. *Please* stop interpreting yourself and provide the logs -- otherwise I can't reproduce it.
Please actually log in and look at the attachment before complaining!
(In reply to Andreas Färber from comment #7)
The debug log looks to me as if the default route is parsed correctly but assigned to interface eth0 (USB ethernet adapter, not attached) rather than enp1s0.
Then there are two valid config files and eth0 matches it too => IMO INVALID.
How is it in your opinion invalid to have multiple network interfaces with configs on a host?! If the interface is not up because the device is not present, it certainly is a bad idea to set up the default route on it. While I can certainly edit the route file to name an interface, that will only work with one kernel at a time. Which brings me to the question, why is my single network device in absence of permanent udev names not named eth0 in the first place? Then I could have a single ifcfg-eth0.
Attach full config + logs as requested please.
If you need additional logs, please request them in more detail. I just don't see how my MAC address is relevant to IP routing configuration. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=902650
Marius Tomaschewski
While I can certainly edit the route file to name an interface, that will only work with one kernel at a time. Which brings me to the question, why is my single network device in absence of permanent udev names not named eth0 in the first place? Then I could have a single ifcfg-eth0.
Pass the net.ifnames=0 on the kernel command line, then you will get eth0 under systemd -- for more info, see: http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface... With more than one interface and no persistent udev rule and disabled perdictable systemd names, you'll get eth0,eth1,... randomly assigned to the available nics by the kernel. This is job of udev / systemd-udev to make them persistent and the behavior changed here. Wicked has _nothing_ to do with the names except that it is using them.
If you need additional logs, please request them in more detail. I just don't see how my MAC address is relevant to IP routing configuration.
I don't need any logs -- you are/were using two configs/interfaces and a route matching both. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com