[opensuse] Leap 42.3 suddenly doesnt assign ipv4 default route via dhcpv4 any more?
Hi there, today I was called to figure out what network trouble there was going on. Turns out that a 42.3 leap installation configured for dhcp v4, was getting its address but wasnt getting a default route at all. route -n shows only the local lan ipv6 route is there The only stuff I can think of right now is this recent yast network update. I have rebooted the leap machine several times and I even checked # wicked check dhcp4 eth0 or that command it fetches the dhcp information nicely and in there are the gateways and route shown, but the network stack from the actual wicked stack running doesnt assign or use this gateway info What happened? Is anyone else having trouble with dhcp4 on a simple lan? this is like very basic stuff, wondering if its again me messing stuff up, although I cant remember anything :( Thanks for helping. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* cagsm
Hi there,
today I was called to figure out what network trouble there was going on. Turns out that a 42.3 leap installation configured for dhcp v4, was getting its address but wasnt getting a default route at all.
route -n
shows only the local lan
ipv6 route is there
The only stuff I can think of right now is this recent yast network update.
I have rebooted the leap machine several times and I even checked
# wicked check dhcp4 eth0
or that command
it fetches the dhcp information nicely and in there are the gateways and route shown, but the network stack from the actual wicked stack running doesnt assign or use this gateway info
What happened? Is anyone else having trouble with dhcp4 on a simple lan? this is like very basic stuff, wondering if its again me messing stuff up, although I cant remember anything :(
I have seen that on tw. I issue: systemctl restart wicked wicedd network and it is usually resolved. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Nov 27, 2017 at 1:40 PM, Patrick Shanahan
I have seen that on tw. I issue: systemctl restart wicked wicedd network and it is usually resolved.
you mean even after a direct startup/reboot? isnt the network stack supposed to be fresh then? meanwhile i reverted back to static lan ip for the time being I can maybe try some other day. but isnt this like essential basic networking stuff that is then corrupted? i am using release 42.3 and not tumbleweed. thanks for your reply nevertheless. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
cagsm wrote:
Hi there,
today I was called to figure out what network trouble there was going on. Turns out that a 42.3 leap installation configured for dhcp v4, was getting its address but wasnt getting a default route at all.
route -n
shows only the local lan
Just to be safe - check what dhcp is giving you - cat /var/lib/wicked/lease-ethX-dhcp-ipv4.xml
ipv6 route is there
That is not dhcp related. (it comes from a router or radvd daemon).
The only stuff I can think of right now is this recent yast network update.
Looks like openSUSE-2017-1295. I haven't applied that one yet. Will have to try it out -- Per Jessen, Zürich (5.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
cagsm wrote:
Hi there,
today I was called to figure out what network trouble there was going on. Turns out that a 42.3 leap installation configured for dhcp v4, was getting its address but wasnt getting a default route at all.
route -n
shows only the local lan
Just to be safe - check what dhcp is giving you -
cat /var/lib/wicked/lease-ethX-dhcp-ipv4.xml
ipv6 route is there
That is not dhcp related. (it comes from a router or radvd daemon).
The only stuff I can think of right now is this recent yast network update.
Looks like openSUSE-2017-1295. I haven't applied that one yet. Will have to try it out
Can't reproduce. I've applied the patches and rebooted - came up with a default ipv4 route. -- Per Jessen, Zürich (5.5°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
cagsm -
Patrick Shanahan -
Per Jessen