similar to: xen vlans in domU

<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

--- 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

Hi, [1] Are there guides for setting up a virtual switch for use in between guest domains in Xen ? [2] In Xen, is it possible for a guest domain to perform a initial dhcp IP lookup from another guest domain ? How are the configurations like ? Are there references or step procedures ? Kindly advice. Thanks. _______________________________________________ Xen-users mailing list

Hello list, I've posted here about this before, but I realise that it may have been assumed that the bridged vlans simply put a switch port in a blocking state and left my question ignored. So to recap. I have two tg3 interfaces named 'in' and 'out' and a bridge named 'br0' My vlan trunk is on the 'in' side of the network, and set as in.2, in.3 ... The

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

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

Hi Rahul, If you're certain that your problem isn't as Stephen suggested, you might want to have a look at this: --- (From http://ebtables.sourceforge.net/brnf-faq.html <http://ebtables.sourceforge.net/brnf-faq.html> ) How do I let vlan-tagged traffic go through a vlan bridge port and the other traffic through a non-vlan bridge port? Suppose eth0 and eth0.15 are ports of br0.

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

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''m trying to implement simple untagged vlans on our switch and have misconfigured something.. ISP gw is on the default vlan1 (untagged) Router eth1 is setup on the switch with default vlan1 and member of vlan4. eth0 is default vlan4 which connects to the clients that are all default members of vlan4 eth0 is x.x.x.86/28 This is what clients are connecting to as their gw.. (no

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 ?

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

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

Hi all, I have xen2.0.7 running in a fedora core 3 ! I have dom0 and domU running fine and communicating between each other as well between other machines on diferent networks. Still i want to improve my network setup and i start reading manuals and malling lists about bridging and vlans configuration! I have two nics each one associated to eth0 and eth1. Eth0 -> Vlan A Eth1 -> Vlan

Andrew and Dennis are spot on. Their conclusions about your server being connected to an access port and not a trunk port would be my conclusion as well. On Sat, Jan 24, 2015 at 9:11 AM, Dennis Jacobfeuerborn < dennisml at conversis.de> wrote: > Hi Boris, > what I'd like to know is the actual VLAN configuration of the switch > port (link-type and tagged and untagged VLANs).

Hi, The attached patches enables the bridge to filter and forward packets according to their IEEE 802.1q headers. The goals behind this change include : - Enable running STP on 802.1q tagged networks. STP packets must be untagged. It isn't obvious how else to enable STP with the current bridge and vlan code. - Add native support for an untagged vlan. Currently an untagged vlan can

Do you need the whole configuration? On the switch end, we have the relevant VLAN (VLAN 48) with the assigned IP address of 192.168.48.101 and the range of ports (Gi1/0/1 - Gi1/0/8) assigned to that VLAN. Seems - and acts - like a legitimate setup and works fine, except for this particular instance. Thanks. Boris. On Fri, Jan 23, 2015 at 8:54 PM, Dennis Jacobfeuerborn < dennisml at

Thank you everyone. OK, the mystery deepens, I guess. The machine does need to support several VLAN's, it is currently on a trunkport (8021q encapsulated), it made it into the ARP table - which I specifically tested for by physically unplugging the table, clearing the ARP table and plugging it back in. The ARP table currently looks like this: hq#show arp Protocol Address Age (min)

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

I'm looking for some information regarding the interaction of KVM, VLANs, firewalld, and the kernel's forwarding configuration. I would appreciate input especially from anyone already running a similar configuration in production. In short, I'm trying to figure out if a current configuration is inadvertently opening up traffic across network segments. On earlier versions of CentOS