similar to: [Bridge] eth2.100: received packet with own address as source address

Hello You must add first: vlan (tagged) to eth2 eth2 interface is not tagged by default and not know vlan-s . It is like a cisco if you have 24 ports in cisco by default all ports are in vlan1. if you want to do trunk (with vlans) you myst add (vlans) to this ports (tagged or untagged) So you can compare that all interfaces in linux by default are in one vlan(but not tagged). (only for

Hello, My name is Ferm?n Gal?n and I work as Research Engineer at CTTC, Spain. I'm trying to configure a bridge with brctl to switch VLAN tagged traffic (802.1q), but I'm getting some problems. In particular, I've a physical interface (eth2) connected to a Cisco trunk port (so, the traffic to/from eth2 is tagged). I've added eth2 to a bridge ('brctl addif somebrige

As the issue concerns both the -user (configuration) and -devel (OOPS), I''m sending this message to both lists. Some time ago I complained about two problems: - VLANs are not working on machines with 100 Mbit cards - I get a kernel Oops (sometimes panic) when I try to use bonding and VLANs with Xen The root of the issue is the same in both cases: VLAN interfaces must *not* be

As the issue concerns both the -user (configuration) and -devel (OOPS), I''m sending this message to both lists. Some time ago I complained about two problems: - VLANs are not working on machines with 100 Mbit cards - I get a kernel Oops (sometimes panic) when I try to use bonding and VLANs with Xen The root of the issue is the same in both cases: VLAN interfaces must *not* be

I ran into an issue when trying to create VMs in CentOS 5.5 with VLANs. My setup is as follows: -CentOS 5.5 x64 xen kernel -LVM for storage -Kickstart file hosted on apache in /var/www/html/ -VM start file in /etc/xen/ -VLAN100 interface with public IP, VLAN200 interface with private IP My vm start file is as follows: kernel = "/boot/vm-inst/vmlinuz" ramdisk =

I have a strange problem with VLANs with Xen 3.0.4. I signalled it on Xen-users list, but found no definitive solution to it. I configure VLANs so that they are available in dom0; domUs don''t know that they use VLANs. I use a stock "network-bridge" comming from Xen for setting up networking: #!/bin/bash dir=$(dirname "$0") "$dir/network-bridge"

Hi, i have big trouble with a Debian Lenny dom0 and latest kernel 2.6.32.19 with xen-4.0.1rc5. Due some reason the system freezes from time to time. I used kernel 2.6.31.9 with xen-3.4.2 before. The machine doesn''t write anything to serial console so there are no errors or something like that. Perhaps there is something to see from the logs ... Hardware Board: Intel DQ45CB CPU: