Submitted by UWF on Wed, 01/04/2012 - 15:03
After setting up many virtual network interfaces with Webmin network interface manager they disappear. I add them using the correct IP and Netmask with automatic Broadcast but after a reboot once in awhile the virtual interfaces will still be there but the IPs will not function at all, after deleting the interfaces and adding them again it works as usual. I've had this issue on Debian 6.0 64bit on two different servers, the main IP and the first added virtual interface do not have this problem.
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Wed, 01/04/2012 - 22:22 Comment #1
That's weird ... so does a reboot fix this problem, or trigger it? I saw a problem once on a system with many interfaces where it hit the kernel limit of 64k interfaces that could ever exist (including those that were created and deleted). A reboot was the only fix.
Submitted by UWF on Thu, 01/12/2012 - 14:41 Comment #2
The reboot actually triggers the problem, I know, weird. The only solution is to delete all the virtual interfaces and add them back. I made sure I'm editing my active at boot tab. No success.
Submitted by UWF on Thu, 01/12/2012 - 15:24 Comment #3
I found the problem, it actually is a bug with Webmin and not my specific system or operating system (well maybe OS not sure), but when the network interfaces manager edits /etc/network/interfaces it places auto eth0 after all of my virtual interfaces (eth0:1 eth0:2 eth0:3 eth0:4 eth0:5) and of course a virtual interface can't start until the physical one is started, but the real one is still able to start at the end of it all.
I simple edited this: auto lo eth0:1 eth0:2 eth0:3 eth0:4 eth0:5 eth0
To this: auto lo eth0 eth0:1 eth0:2 eth0:3 eth0:4 eth0:5
I hope it is fixed in the next version, also is it alright having my loopback after eth0 or should I put eth0 first?
Submitted by JamieCameron on Thu, 01/12/2012 - 17:30 Comment #4
Interesting, I didn't know that the real interface had to come first ... I guess this has never been a problem before, as the real interface would usually be created first.
Regardless, I will fix Webmin in the next release to always put eth0 before eth0:1
Submitted by UWF on Fri, 01/13/2012 - 11:45 Comment #5
Awesome, any suggestion on where loopback should come? Also, eth0 came with the installation so it was first, but maybe I saved eth0 after creating some virtual interfaces, because last time I had this issue on another dedi eth0 and eth0:1 worked but the rest had to be re-added every time I rebooted.
Submitted by JamieCameron on Fri, 01/13/2012 - 12:49 Comment #6
I'd say loopback should be first .. at least, that's where Webmin will put it.
Submitted by Issues on Fri, 01/27/2012 - 13:18 Comment #7
Automatically closed -- issue fixed for 2 weeks with no activity.