Well I am sorry for disrupting your day here. There appear to be more
issues as you may have indicated.
If the original eth0 is brought up first, and then the bridge (say,
eth1) (or br1) is brought up second there are no issues really to begin
with.
However if the eth0 is then brought down, and we test the connection,
the bridge still functions, but eth0 doesn't work anymore. Then, if I
bring down the bridge and bring it back up again, eth0 functions again.
But I tried -- and I am not trying to turn this into a support request
form -- to use virtual interfaces solely (aliases) and the thing that
didn't work is that dhcp (dhclient) didn't like being told to use
eth0:0.
So useing aliases is not without issue either, it seems. It's probably
the proper solution but for now my bridge works, no matter how
unreliable :p.
I just don't know what alternative there is to create a named interface
out of some other interface. I assume basing the bridge on the alias
would work; that is what it seemed to be doing. Having a bridge with its
own IP and a root device with its own IP is not much different from
having two aliases with their own IP, right?
