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-users] network-bridge with vlan and problems ...

To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] network-bridge with vlan and problems ...
From: christian gattermair <christian.gattermair@xxxxxxx>
Date: Tue, 18 Sep 2007 14:19:42 +0200
Delivery-date: Tue, 18 Sep 2007 05:21:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.7

i try to set up my xen enviroment to a vlan bridge ...

/etc/xen/scripts/network-bridge start netdev=eth4.850 bridge=xen-br850 

Link veth4.850 is missing.
This may be because you have reached the limit of the number of interfaces
that the loopback driver supports.  If the loopback driver is a module, you
may raise this limit by passing it as a parameter (nloopbacks=<N>); if the
driver is compiled statically into the kernel, then you may set the parameter
using netloop.nloopbacks=<N> on the domain 0 kernel command line.

ip link show | grep veth
3: veth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
5: veth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
7: veth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
9: veth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
11: veth4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
13: veth5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
15: veth6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
17: veth7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
19: veth8: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
21: veth9: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
23: veth10: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
25: veth11: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
27: veth12: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
29: veth13: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
31: veth14: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
33: veth15: <BROADCAST,MULTICAST> mtu 1500 qdisc noop

my debian networking config:

iface xen-br850 inet manual
        up ifconfig eth4 up
        up vconfig add eth4 850
        up /sbin/ifconfig eth4.850 up
        up ifconfig eth4.850 netmask
        up route add default gw
        up /etc/xen/scripts/network-bridge start netdev=eth4.850 
bridge=xen-br850 antispoof=no
        down /etc/xen/scripts/network-bridge stop netdev=eth4.850 
bridge=xen-br850 antispoof=no
        down vconfig rem eth4.850

how can i create veth4.850???

eth4.850 (the vlan interface) is up and runs.

thanks for any hint!

with friendly greetings,


Xen-users mailing list

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