I’m running a couple of virtual machines using openSuSE 12.1 and I’ve noticed two possibly related network issues:
Some percentage of time, when the machine boots, the network interfaces come up as per normal, but then immediately go down. There’s no logs (that I’ve been able to find, certainly not in the messages where all the other activity happens) that indicates why this would be. It just happens. I can bring up the interfaces using ‘ifup’ just fine. When this happens at boot, attempting to bring up the interfaces with a init.d network restart results in the same behavior. If it doesn’t happen at boot, then the init.d scripts work per normal (at least in my small sample size so far).
Even if the network comes up and stays as per normal at boot, it will reset itself after awhile. The time seems to be random… maybe 10 minutes, or might stay up for longer sometimes. But I’m not 100% on the timing. (The virtual hosts usually don’t run for too long at any one time.) Again, no indication I’ve found why the network decides to restart.
The problem with the reset, and this may be related to the issue though I don’t see how, is that I have custom changes to the iptables. I’ve got this set up to get initialized properly on boot with no problems, but when the network resets, it loses my custom iptables settings.
The guest is openSUSE 12.1, and so is the host (also run from a Mac host… actually, not sure if I’ve noticed this issue on the Mac host, 90% of the time, I’m running suse on suse).
It’s virtualbox.
I too don’t believe the custom routing is part of the problem, but since I don’t have a theory as to what the problem is, thought I’d mention it.
The reset just seems to happen. There may be some common cause, but I’ve not been able to detect it. If I look in the logs, I see where the network goes down, but there’s nothing that seems pertinent right before. I’ve got the guest up and running now. I’ll post the log info next time the reset happens.
On 2012-06-01 19:36, zanerock wrote:
> The problem with the reset, and this may be related to the issue though
> I don’t see how, is that I have custom changes to the iptables. I’ve got
> this set up to get initialized properly on boot with no problems, but
> when the network resets, it loses my custom iptables settings.
There is a hook in SuSEfirewall2 to place your own iptables rules, so that
they are applied on any network restart.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
I concur; I’ve had a similar problem when pxe-booting 12.1. After some time (~3 minutes, probably the default timeout of systemd), the service network-remotefs.service failed which also caused network.service to fail. My solution: Disable network-remotefs.service. You might want to try that although your time constant (10 min) does not fit mine… – Yarny
Thanks all. I used the ‘systemctl --failed’ and found that the NetworkManager.service was failing. Don’t know if that runs by default or I misconfigured, but I disabled it and so far everything looks good. I’ll add the hook to setup the iptables as well for good measure.
