This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 449] Packets sent by dom0 to domU lost in domU before us

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 449] Packets sent by dom0 to domU lost in domU before userspace delivery
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Tue, 13 Dec 2005 15:34:52 +0000
Delivery-date: Tue, 13 Dec 2005 15:37:55 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

------- Additional Comments From craig@xxxxxxxxxxxxxxxxxxxxx  2005-12-13 15:34 
Given that this is a networking issue, I should describe my network
configuration in slightly more detail.

I have a bridge at br0 that's bought up during system boot. The physical
interface, an Intel e1000 (ifname is eth1000), is joined to the bridge. From
that point on, the bridge interface is treated as if it was the physical 

This scheme is pleasantly simple and works just fine under Xen 2.0. I don't
think it's related to the issue here (since it's essentially the same as the
default Xen scheme, though without the virtual-eth0-and-MAC-funnybusiness of
some configurations), but am including the info just for completeness.

Xend runs no network setup script (and network-bridge has been backed up then
replaced with an empty script, just in case), as it's all configured by the time
Xen starts. vif-bridge is run normally and is unmodified.

Here's the Debian /etc/network/interfaces file that does the setup work on the


auto lo
iface lo inet loopback

# the PCI-X giabit card, our main path to the rest of the world
# Now via a bridge to support Xen, see below
iface eth1000 inet static
        pre-up /sbin/nameif -s
        # Work around Xen 3.0 bug #449 (unsuccessful; disabled)
        # mtu 1400

auto br0
iface br0 inet static
        pre-up /sbin/nameif -s
        # Include the main ethernet interface in the bridge
        bridge_ports eth1000
        # Enable spanning tree... just in case:
        bridge_stp on
        # Learning delay before entering forwarding mode:
        bridge_fd 2
        # Tell ifup not to wait more than 30s for the bridge to be ready:
        bridge_maxwait 30

# These aren't normally used; they're the interfaces
# on the motherboard.
iface eth100a inet dhcp
iface eth100b inet dhcp


Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>