Webmin's net module writes /etc/conf.d/net in a deprecated format. Initially, it was the config_ethx="...." with the alias_ethx="..." However, that format has now been fully deprecated--and webmin just trashes the config.
This means other really useful things like Virtualmin don't work--and end up trashing your server. So this should proably be masked out until someone fixes it. Who knows... maybe I'll see if I can get around to it this week.
Seems there was another bad problem with Virtualmin dealing with how it processed virtual interfaces versus IP addresses under Gentoo.
Anyway, "out of the box" it turns this:
config_eth0=( "192.168.1.132 netmask 255.255.255.128 brd 192.168.1.255" )
routes_eth0=( "default gw 192.168.1.254" )
config_eth0="( "192.168.1.132 netmask 255.255.255.128 brd 192.168.1.255" )"
routes_eth0="( "default gw 192.168.1.254" )"
...which, of course, makes the OS do everything but boot right!
If you have config_eth0 then only new style config is used
If you don't then it tries to support old style.
The error is in mixing them.
(In reply to comment #1)
> If you have config_eth0 then only new style config is used
> If you don't then it tries to support old style.
> The error is in mixing them.
Actually, it doesn't. I had one that was the "old style" and, after the latest round of emerge --update --deep world, the "old style" is no longer supported. So probably the best thing is to change Webmin to conform.
I'm looking at it right now.
Question: would it be safe to *not* read /etc/conf.d/net and just build it based on currently active interfaces and routing? It would tend to (1) reduce the chance of parsing error and (2) allow a more "pristine" /etc/conf.d/net file to be built out of webmin.
Also, /etc/conf.d/routes needs to be factored in as well.
The only time it seems like this would be a problem is if someone wanted to add an interface that they didn't want active at boot (a temporary alias), and then decided for whatever reason, they wanted to add a permanent alias interface.
"But nobody's ever really going to want to do that, are they?" :)
Love making assumptions and writing code to carry it out :)
(In reply to comment #2)
> (In reply to comment #1)
> > If you have config_eth0 then only new style config is used
> > If you don't then it tries to support old style.
> > The error is in mixing them.
> Actually, it doesn't. I had one that was the "old style"
Then open a new bug attaching your full /etc/conf.d/net file as that's news to me.
I've got a better way... delete everything out of /etc/conf.d/net then use the Webmin interface to add eth0 back with a static IP address. Then add an alias (eth0:1). Then reboot and watch the console messages.