Bugzilla – Bug 802761
Route is not setup correctly after installation via DHCP
Last modified: 2013-03-04 11:29:06 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 After the update to RC1 I can not longer connect to internet. After some investigation, I found out, that the route has not been set up correctly. The root shows like this: c-web2:~ # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 10.0.20.254 0.0.0.0 UG 0 0 0 eth0 10.0.16.0 10.0.20.1 255.255.255.0 UG 0 0 0 eth0 10.0.16.0 10.0.20.1 255.255.255.0 UG 0 0 0 br0 10.0.20.0 0.0.0.0 255.255.255.0 U 0 0 0 br0 10.0.20.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo I can connect again after running the following command: c-web2:~ # route add default gw 10.0.20.254 br0 I did not run any special setup before, configuration via DHCP works within the network with different other systems including OSS 12.3beta1. The issue occures on both my test machines. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Please test by calling as user root dhcpcd-test eth0 if your client gets a value for GATEWAYS offered. Depending on the setting of DHCLIENT_BIN in /etc/sysconfig/network/dhcp either dhcpcd or dhclient is used. Please provide the the valiue of DHCLIENT_BIN from /etc/sysconfig/network/dhcp
Dear Lars, DHCLIENT_BIN is empty; for dhcpcd-test I receive the following results: c-web1:~ # dhcpcd-test eth0 info, eth0: hardware address = 60:a4:4c:2c:77:8d info, eth0: broadcasting for a lease debug, eth0: sending DHCP_DISCOVER with xid 0x767c3f96 debug, eth0: waiting for 10 seconds debug, eth0: sending DHCP_DISCOVER with xid 0x767c3f96 debug, eth0: sending DHCP_DISCOVER with xid 0x767c3f96 err, eth0: timed out info, eth0: exiting c-web1:~ # dhcpcd-test br0 info, br0: hardware address = 60:a4:4c:2c:77:8d info, br0: broadcasting for a lease debug, br0: sending DHCP_DISCOVER with xid 0x5fac7dd8 debug, br0: waiting for 10 seconds debug, br0: got a packet with xid 0x5fac7dd8 info, br0: offered 10.0.20.31 from 10.0.20.1 IPADDR='10.0.20.31' NETMASK='255.255.255.0' NETWORK='10.0.20.0' BROADCAST='10.0.20.255' ROUTES='10.0.16.0,255.255.255.0,10.0.20.1' GATEWAYS='10.0.20.254' HOSTNAME='c-web1' DNSDOMAIN='vie.weberhofer.at' DNSSERVERS='10.0.20.1' NTPSERVERS='10.0.20.1' DHCPSID='10.0.20.1' LEASETIME='86400' RENEWALTIME='0' REBINDTIME='0' INTERFACE='br0' CLASSID='dhcpcd 3.2.3' CLIENTID='01:60:a4:4c:2c:77:8d' DHCPCHADDR='60:a4:4c:2c:77:8d' NETBIOSNAMESERVER='10.0.20.1' NETBIOSNODETYPE='8' info, br0: exiting
Above info provided needed information.
*** Bug 803019 has been marked as a duplicate of this bug. ***
Similar problem here with networkmanager Initially it's: linux-6dv9:~ # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wlan0 192.168.178.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 After stopping wlan and starting again, I have: linux-6dv9:~ # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.178.1 0.0.0.0 UG 0 0 0 wlan0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 192.168.178.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 Marius, anything I can debug?
sysconfig and most other packages has been changed to not use NETWORKMANAGER variable any more, but a network.service alias link. See also release notes bug #800771 and - still unfixed - bug #798348, to adopt switching between NetworkManager and /etc/init.d/network in yast2. [/etc/init.d/network is currently active only while miminal installation, in all other cases NetworkManager because yast2 is unable to switch it as needed.] To enable NetworkManager, use: systemctl stop network.service systemctl --force enable NetworkManager.service systemctl start network.service to disable NetworkManager, use: systemctl stop network.service systemctl --force disable NetworkManager.service systemctl start network.service This command: systemctl --no-pager -p Id show network.service reports "Id=NetworkManager.service" when NetworkManager acts as the network service, "Id=network.service" means /etc/init.d/network. *** This bug has been marked as a duplicate of bug 798348 ***
Looking at this report, I guess that NM is running on eth0 and you started dhcpcd on br0 ... Please make sure to either enable or disable 'NM' using above commands as needed and _reboot_. Verify using "ps axwf" that the correct one is running. When your problem still exists, please reopen/remove duplicate flag of this bug report. When you are using /etc/init.d/network, please call supportconfig (supportutils package) and attach the archive it creates.
With the manual workaround from comment #6, routing is back to br0. However, I wouldn't consider a manual workaround an actual fix.
This bug were resolved as duplicate of the wrong bug, fixed to bnc#803058. Note: The fix does not catch work for 12.3-RC1 -> 12.3-RC2 updates, but only for 12.2 -> 12.3 updates: it checks if the old sysconfig package were still using the NETWORKMANAGER variable or not. The fixed packages are: http://download.opensuse.org/factory-snapshot/ (sysconfig-0.80.5, NetworkManager, systemd-presets-branding-openSUSE) *** This bug has been marked as a duplicate of bug 803058 ***