Your message dated Sun, 15 Jun 2008 12:15:42 +0200
with message-id <[EMAIL PROTECTED]>
and subject line route problems
has caused the Debian Bug report #485774,
regarding [bridge-utils] route not set correctly after boot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
485774: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485774
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: bridge-utils
Version: 1.4-2
Severity: normal

--- Please enter the report below this line. ---
I don't know, if this is a bug or an issue in my setup, so please apologize, if
the latter is the case.

Since I have installed virtualbox with bridge setup, after booting of
the machine the routing table is:

localnet        *               255.255.255.0   U     0      0        0 eth1
localnet        *               255.255.255.0   U     0      0        0 br0
default         192.168.1.10    0.0.0.0         UG    0      0        0 br0
default         192.168.1.10    0.0.0.0         UG    0      0        0 eth1

resulting in broken DNS (which is pointing to DNS on the server at
192.168.1.10).


After doing /etc/init.d/networking restart the routing table is:

localnet        *               255.255.255.0   U     0      0        0 br0
default         majestix.violad 0.0.0.0         UG    0      0        0 br0

and network is up as usual.

/etc/network/interfaces:
allow-hotplug eth0
iface eth0 inet dhcp

allow-hotplug eth1
iface eth1 inet dhcp

allow-hotplug eth2
iface eth2 inet dhcp

allow-hotplug eth3
iface eth3 inet dhcp

# virtualbox bridging
auto br0
iface br0 inet dhcp
    bridge_ports eth1


Since restarting the network fixes the problem, I guess, that there is some
issue in the boot sequence of the network.

Thanks a lot for looking into the problem,
Mathias

--- System information. ---
Architecture: amd64
Kernel:       Linux 2.6.24-2-obelix-opt

Debian Release: lenny/sid
  990 testing         apt-cacher 
  800 unstable        apt-cacher 
  600 experimental    apt-cacher 

--- Package information. ---
Depends       (Version) | Installed
=======================-+-===========
libc6        (>= 2.7-1) | 2.7-10


Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Sorry, I must have missed your mail among all the spam I got lately.

For what I see the problem here is a setup problem in your interfaces file,
let's see it:

------------------
/etc/network/interfaces:
allow-hotplug eth0
iface eth0 inet dhcp

allow-hotplug eth1
iface eth1 inet dhcp

allow-hotplug eth2
iface eth2 inet dhcp

allow-hotplug eth3
iface eth3 inet dhcp

# virtualbox bridging
auto br0
iface br0 inet dhcp
    bridge_ports eth1
------------------

Since you are adding eth1 to your br0 interface I think you don't want it
defined as well on your interfaces, thus I would suggest that you remove or
comment these two lines:

allow-hotplug eth1
iface eth1 inet dhcp

And I believe that should do it. Other than that I see everything ok.

Regards...
-- 
Manty/BestiaTester -> http://manty.net


--- End Message ---

Reply via email to