[opensuse] wicked and network change
Hi list, I recently upgraded (rather:re-installed) my system to 13.2, which first used NetworkManager for setting up the network. Though it was sort off annoying that I always had to restart my VPN after a hibernation, what really made me dump it was that several times after an zypper up it lost all connection to the device, and I ended up rebooting to return it to a sane state... So I changed to wicked (I'm not using wireless anyhow), and set up VPN via systemd. While this works fine, it behaves weird when I switch to a different (wired) network (as I do daily between home and work). The network is set for DHCP, and after boot I can see the IP address using ifconfig. But if I suspend and resume connected to the other network, ifcofig will still show the old address, allthough I can see in the system logs that DHCP has acquired a new address for that interface. Indeed, 'ip addr show' lists two: snoopy:~% ip addr show enp0s25 3: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff inet 192.168.1.33/24 brd 192.168.1.255 scope global enp0s25 valid_lft forever preferred_lft forever inet xxx.xxx.xxx.23/24 brd xxx.xxx.xxx.255 scope global enp0s25 valid_lft forever preferred_lft forever I find this somehow - wicked. Is this the default/expected behavior? My old system (12.3) always had only one address active. Is there a way to get back to the old way? Thanks, Pit -- Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit Institute for Solar Physics Tel.: +34 922 405 590 (Spain) P.Suetterlin@royac.iac.es +46 8 5537 8507 (Sweden) Peter.Suetterlin@astro.su.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Thu, 16 Apr 2015 11:46:45 +0100 P.Suetterlin@royac.iac.es пишет:
Hi list,
I recently upgraded (rather:re-installed) my system to 13.2, which first used NetworkManager for setting up the network. Though it was sort off annoying that I always had to restart my VPN after a hibernation, what really made me dump it was that several times after an zypper up it lost all connection to the device, and I ended up rebooting to return it to a sane state...
So I changed to wicked (I'm not using wireless anyhow), and set up VPN via systemd. While this works fine, it behaves weird when I switch to a different (wired) network (as I do daily between home and work). The network is set for DHCP, and after boot I can see the IP address using ifconfig. But if I suspend and resume connected to the other network, ifcofig will still show the old address, allthough I can see in the system logs that DHCP has acquired a new address for that interface. Indeed, 'ip addr show' lists two: snoopy:~% ip addr show enp0s25 3: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff inet 192.168.1.33/24 brd 192.168.1.255 scope global enp0s25 valid_lft forever preferred_lft forever inet xxx.xxx.xxx.23/24 brd xxx.xxx.xxx.255 scope global enp0s25 valid_lft forever preferred_lft forever
I find this somehow - wicked.
Is this the default/expected behavior? My old system (12.3) always had only one address active. Is there a way to get back to the old way?
In the past network was restarted across suspend/resume which probably explains it. You can try to emulate it by adding script to /usr/lib/systemd/system-sleep; see ystemd-sleep(8). I hesitate to call it a bug, although behavior is quite unusual indeed. Open bug report to find out for sure.
Thanks,
Pit
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov wrote:
In the past network was restarted across suspend/resume which probably explains it. You can try to emulate it by adding script to /usr/lib/systemd/system-sleep; see ystemd-sleep(8).
I hesitate to call it a bug, although behavior is quite unusual indeed. Open bug report to find out for sure.
Thanks Andrei! Looking through the bugreports I found some (sort of) similar issues that could be solved by enabling nanny in the wicked configuration (/etc/wicked/common.xml) I'll try this, too and report back if it solves my problem. Pit -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
P.Suetterlin@royac.iac.es wrote:
Looking through the bugreports I found some (sort of) similar issues that could be solved by enabling nanny in the wicked configuration (/etc/wicked/common.xml) I'll try this, too and report back if it solves my problem.
No, neither nanny, nor switching the interface to 'on cable connect' fixes the issue. So I filed a report: https://bugzilla.opensuse.org/show_bug.cgi?id=927586 Pit -- Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit Institute for Solar Physics Tel.: +34 922 405 590 (Spain) P.Suetterlin@royac.iac.es +46 8 5537 8507 (Sweden) Peter.Suetterlin@astro.su.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Andrei Borzenkov
-
P.Suetterlin@royac.iac.es