Comment # 2 on bug 957461 from andreas bittner

some hours ago some update appeard via zypper up and I restarted a few services
just to notice later that NAT of this machine was again completely broken
therafter:

zypp history:

2016-10-03 13:40:56|command|root@tux|'zypper' 'up'|
2016-10-03
13:40:56|install|libgcrypt20|1.6.1-32.1|x86_64||42.1-update-oss|89241c3c6236de7f9950e83c7c0f28464561f181d4a3521c9b818e3b356898da|
2016-10-03
13:40:56|install|libgcrypt20-32bit|1.6.1-32.1|x86_64||42.1-update-oss|fcd2fee1e2c5396adc6f86979d6251856a92eba42d17f56f0bc9dae67a630020|
2016-10-03
13:40:56|install|libopenjpeg1|1.5.2-5.1|x86_64||42.1-update-oss|bf189717ba57690f34deafe75a35905f71ac4226cd0250cf0ef7c96fbb7a426d|


restart commands after that:

  987  2016-10-03 13:41:20 systemctl restart systemd-journald.service
polkit.service wickedd.service display-manager.service

  990  2016-10-03 13:41:29 systemctl restart ModemManager.service



Later, today, I noticed that the nat functionality of the kernel
(susefirewall2) was completely nonfunctional again. I needed to restart the
whole machine to bring it back into normal state.

users on the inside of the network it is doing ipv4 nat for, couldnt browse the
web or fetch or send mails via pop3/smtp and so on.