On Wed, Mar 11, 2009 at 12:47 PM, Santiago Garcia Mantinan
<ma...@debian.org> wrote:
> 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.
The grep only showed some commented lines in interfaces (I will delete
them and see if they caused some effect although they were commented
out). Aside from that only udev persistency rules, and one hit in a
xend-config.sxp.dpkg-old (I don't have xen installed anymore).
> 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?
Yes, NetworkManager and its gnome client are running. But I remember
reading just recently that under Debian it is patched such that it
only picks up on auto interfaces. In fact, in the nm-applet I only see
br0, not eth2, and when I go into the settings (I've not really looked
at it / used it before, just somehow found its way onto my system) it
says "br0 - never" under wired connections.
I'm running dhcp3-client 3.1.1-6, AFAIK that's the only one I have installed.
Trimming of comments, I think I have only the stock config:
---snip---
option rfc3442-classless-static-routes code 121 = array of unsigned integer 8;
request subnet-mask, broadcast-address, time-offset, routers,
domain-name, domain-name-servers, domain-search, host-name,
netbios-name-servers, netbios-scope, interface-mtu,
rfc3442-classless-static-routes;
---snap---
I have some entries in the enter/exit hooks, but all from packages,
nothing custom.
> 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.
Thanks, I appreciate it that you're interested in helping out anyway!
I'm running a custom .26 kernel, but I just checked my config and it
has IP_PNP not set (kernel level autoconfiguration), which as far as I
know is the only option that does ip address assignment.
Aside from that the only other noteworthy package I use (this is on a
desktop btw), is virtualbox - which was also the reason I setup the
bridge. But, aside from loading the vobxnetflt module, this problem
occurs before I start virtualbox.
~David
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
