similar to: How to work with VLANs and several nic Interfaces ?

re can somebody tell me what am I doing wrong (at this late night hour), because vlan are not getting bridged at all. ifconfig eth0 0.0.0.0 up ifconfig eth1 0.0.0.0 up brctl addbr br0 brctl addif br0 eth0 brctl addif br0 eth1 ifconfig br0 up vconfig add br0 X vconfig add br0 Y X = vlan-ID (example: 222) Y = vlan ID (example: 223) # brctl show bridge name bridge

<I apologize if this arrives twice... I sent it first from an non-subscribed address, don't know if that'll get to the list or not --JJ> Hi folks, I have an implementation question regarding bridging on a linux box between a catalyst trunk port and a cisco 26something w/802.1q subinterfaces. So right now, there's no vlan trunking going on on the link my bridging firewall sits

On Mon, Nov 21, 2011 at 1:18 AM, Ian Campbell - Ian.Campbell@citrix.com wrote: > On Sun, 2011-11-20 at 01:11 +0000, > xen-devel.GarveyPatrickD@OrdinaryAmerican.net wrote: >> http://wiki.xen.org/wiki/Assign_Hardware_to_DomU_with_PCIBack_as_module >> contains a link to the University of Cambridge Computer Laboratory >> copy of the Xen User Manual >>

Hello. I''m trying to use vlan in domU, but have something strange: I created bridge on eth0. This interface was configured as trunk with vlan 300, 301. I use this bridge in my domU, and I can see tagged packets when run tcpdump in domU. Also I created interface on domU to work with vlan 300. On this interface I see untagged packets in vlan300. And everything looks fine. But when

The Xen Mercurial cheatsheet ( http://www.cl.cam.ac.uk/research/srg/netos/xen/readmes/hg-cheatsheet.txt ) says: <<<<<<<<<<<<< You can point a browser and this and use Hg''s web interface to view revision history, or use it as the nominated source when issuing "hg init" or "hg pull" commands. However, to avoid taxing the Mercurial

--- In english --- Hello! I am to implement a new architecture of the network in my company but I do not know right where to start ... need help! Currently 90% of my servers are virtual machines under Xen. I have many valid IP networks and all Hypervisors are configured in bridge mode, to simplify. We have 3 VMWare ESX Hypervisor also in bridge mode. Some networks are exclusive to certain

My actual scenario is: -Hundreds PCs in a internal network (fixed IP), divided in +- 6 different subnets -A +- 6 customers with leased lines -A Cisco Catalyst 4006 connecting groups of PCs to corresponding customers (imagine a Call Center company) -Works fine. The problem: Frequently, it''s necessary to migrate dozens PCs from a customer to another. You know, change all IPs and

I am using 8021q vlans on my servers, and I cannot figure out how to make PXE/DHCP work. Has anyone figured out how to do this ?

I have 3 machines, T60 thinkpad with e1000 NIC Dell PowerEdge 2950 with bnx2 NIC HP DL360 G4P with tg3 NIC All running xen 3.03 / 2.6.16.29-xen I have a netbootable image with 2.6.16.29-xenU. This image when it boots creates a vlan eth0.4002, and then tries to communicate on that interface to a central server. On the machines with e1000 an bnx2 NICs, this works fine. On the

REPRO: - download the seed from : "http://xenbits.xensource.com/xen-2.0-testing.hg" repository (seed archive<http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen-2.0-testing.hg.tar.gz> ) http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen-2.0-testing.hg.tar.gz - mkdir xen - cd xen - tar -zxvf ~/downloads/xen-2.0-testing.hg.tar.gz - cd xen-2.0-testing.hg.tar.gz -

Does anyone have VLAN tagging working from within a guest on vmware-server? I'm running a centos 4.5 guest on a centos 5 host with vmware server 1.04and I've tried creating vlans using both the /etc/sysconfig/network-scripts method and just doing it from the cli via vconfig. Either way appears to work, the OS creates the vlans, but I think vmware's network adapter must be eating the

Hi all, i need config xen with this ___________ __________ |VM1 |----------------bridge1-------------------| | |__________ | | | ____________ | |-----BALBLA |VM2 |

Hi, I'm using Vlans in my network as a way of preventing pier to pier communication - I only want nodes in the network to talk to the gateway (a linux box). I have successfully set up lots of sub interfaces using the vconfig too, one for each vlan. What I would like to be able to do is remove the ip address from each of these subinterfaces eth0.x and bridge them to eth0. I have successfully

Hello I have few questions regarding tc functionality (qdiscs, classes, etc.) when vlans are in use. For example, consider interface eth0, for which I create and extra vlan with vconfig, let''s say eth0.11. Then using tc I can add usual things - qdiscs, filters, ... - to both eth0 and eth0.11. The questions are: - on which interface - virtual or real, should I actually use tc ? Or

I''m a newbie. :) I followed the steps written by Jerone Young: http://sourceforge.net/mailarchive/message.php?msg_id=10562241 but i found an error at the 17th step: 17. mkinitrd /boot/initrd-2.6.10-xen0.img 2.6.10-xen0 it said:"No module ata_piix found for kernel 2.6.10-xen0, aborting." so I commented the line of "module /boot/initrd-2.6.10-xen0.img" in the

Dear all, since yesterday our samba PDC did "loose" his master status within our LAN for the domain "SRG" - since then windows boxes did not "see" the logon server anymore. nmblookup -T -M SRG is reporting some of the windows machines (one box running since more then a year...). - net rpc join -S SRG -U root (on the PDC works) - net rpc join -S

Dear all, since yesterday our samba PDC did "loose" his master status within our LAN for the domain "SRG" - since then windows boxes did not "see" the logon server anymore. nmblookup -T -M SRG is reporting some of the windows machines (one box running since more then a year...). - net rpc join -S SRG -U root (on the PDC works) - net rpc join -S 192.168.123.202

Hi, I am configuring some servers in a high availability setup. The servers are connected to two switches with two LAN cards in each server. The two switches are connected directly to each other. The servers are configured to bridge eth0 and eth1 with spanning tree. Usually this makes sure eth1 is disabled, unless something happens to eth0. This way I can have one IP address on each server. Now

Hi to the ML. I''m new to VLAN configuration, and combining it to XEN is a bit difficult. I want to use VLAN because it''s possible to "arping" from a domU to an other, and VLAN looks like; the only solution to prevent that. May be I''m wrong if someone got a solution, I may be interrested. I''ve also tryed ebtables, but nothing to prevent arp

Running on Centos 5.6 with KVM... I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge? I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it. There also seems to be a bug with 5.6