> ---snip---
> auto lo
> iface lo inet loopback
>
> auto br0
> iface br0 inet dhcp
> bridge_ports eth2
> bridge_fd 2.5
> ---snap---
I have setups that look mostly like yours and they work perfectly, I'd like
to know a bit more about your setup, you say that your interfaces is exactly
like that and if it is just like that I cannot see how eth2 can get the
default route.
> After booting the default route is now set for eth2, not for br0. I think it
> used to be that it would always get set for both interfaces, which seemed to
> work fine. Both interfaces are up with the same ip address, exactly as before
> when it used to work fine.
Having it set for both interfaces was also not good.
If you don't have eth2 mentioned on your interfaces other than on the
bridge_ports line then you must have it somewhere else.
I'm thinking about some daemon doing dirty things, I would do a
grep -r eth2 /etc
and see what that accounts for.
What dhcp client do you have installed? can you have a look at its config?
Any network daemons running? maybe something related to gnome or kde?
I don't think this is a but on bridge-utils but on your setup, but I'd like
to know what is hapenning for the next time this happens to anybody else.
Regards...
--
Manty/BestiaTester -> http://manty.net
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
