Comment # 1 on bug 957461 from andreas bittner

Oh noes ;) I am coming closer to this bug with the help of my other dbus
related bugs.

https://bugzilla.opensuse.org/show_bug.cgi?id=929564


I have finally figured out that the nat capability of my Leap 42.1 dies
immediately when I

systemctl restart dbus.service


Fellow lan machines can not ping or tcp connect or anything any more (simple
susefirewall2 config via yast or default means) when one is issuing the
dbus.service restart.

Unless one then

systemctl restart SuSEfirewall2.service

again thereafter to fix it again.

This is a huge pain. Why is dbus affecting the firewall or is it even iptables
or what exactly? 

iptables -L

looks just normal and rules do exist

Is it maybe again some other networking (or wicked or something?) component
where dbus ties in and blocks down?


The suse linux box itself can be normally pinged and accessed (via ssh for
example) from either side (lan or wan)

Only the routing/nat seems to be affected.

My other dbus related bugreport was about dbus causing huge cpu load on xserver
or xorg or so.


Please read my findings at

#boo929564
https://bugzilla.opensuse.org/show_bug.cgi?id=929564#c5
onwards (or the whole bugreport)

and xorg dbus bug at
#boo954433
https://bugzilla.opensuse.org/show_bug.cgi?id=954433


Thanks in advance for sorting out these damn dbus related bugs