similar to: Fully virtualized domU Linux network (VLAN) trouble

We had problem using tagged vlans inside domU. Testing shows that this is caused by changing network interfaces in network-bridge script. Following patch should allow to use vlans in guest. Testing scenario: configure vlan network (e.g. vlan 1 on eth0 => eth0.1) start xend create domU and configure same vlan inside it You can see that vlan is still <interface>.<vlan_id>. You can

Hello, I use a script network-multi vlan and network-bridge-vlan for multiple VLANs in domu. Several domu uses the bridge vlanbr30. Need to dom0 as was in this vlan''e. How? I tried to put a bridge interface ip, but with him until the rest domu in vlanbr30 not get through. How to understand the need to create a virtual interface (vifx.y) and add it to the bridge vlanbr30. How?

Hello, can anybody help me how to configure vlans? There are vlans: vlan2 vlan3 vlan30 Server has one nic - eth0. vlan2 should be dom0 eth0(peth0) for management Each vlan3 and vlan30 should be has its own bridge. How to make it? Br Peter _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

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

While I am still in the process of working through this here are the steps I am taking to set up each machine. 1) Since each of my servers have multiple NIC ports I bond them together (see page 34 of the Administrators Guide) first. This is best down from the physical server and not via the remote console. If you do it remotely you will then have to reconfigure the management port before

Hi all, did somebody successfuly export ISDN Cards to DomU? I want to have 2 ISDN Cards in DomU (for Asterisk with mISDN) lspci -vt -[0000:00]-+-00.0 nVidia Corporation MCP55 Memory Controller +-01.0 nVidia Corporation MCP55 LPC Bridge ... +-05.1 nVidia Corporation MCP55 SATA Controller +-06.0-[0000:01]--+-00.0 Cologne Chip Designs GmbH ISDN

Hi, I''m running Nevada 75a configured as dom0. I added a domU HVM running Nevada 75a, on a Sun X4600 with 8 ADM Dual cores. I can get the domU installed and configured, however, I can not get any network connectivity. I followed the steps accoding to documents on Open Solaris. I also followed some of the threads of the list to verify the configuration, but I can not fix the

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

I am running CentOS 5.3 x86_64 as my dom0 and CentOS 5.3 on my domU's. On the dom0, I have two interfaces that are bonded and have tagged VLANs. I can get the networks to the domU's by creating a bridge for each of the VLANS (bond0.3, bond0.4, etc). On the domU, the interfaces show up as eth0, eth1, etc. Is there a way to set up the network on the dom0 so my domU's see a single

Hello, I have a linux box sitting between (and bridging/firewalling) 2 LAN segments. I''m using Bridge/Netfilter/IMQ/tc(htb) to control (shape) mail/web traffic that traverses the 2 networks. The networks also have some VLAN tagged traffic flying around. My linux box behaves OK with VLAN traffic except that the shaping doesn''t seem to work. Normal http shapes alright but as soon

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 am running KVM guests under Redhat 6. I tried to setup a bridge device to an interface with a vlan trunk connected to a Juniper switch. On the KVM host, I am able to define vlans and access them via the vlan trunk. I was not able to access a vlan from the kvm guest connected to the bridged interface. I believe this would be what is commonly called QinQ or 802.1ad. Is this possible to do? I

<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

Dear Experts, Does anyone install Windows Vista on XVM successfully? I am using machine Sun x4600 with AMD 8218 cpu with virtualization feature. i installed OpenSolaris build 75, My installation steps: # svccfg -s xvm/xend setprop config/vncpasswd = astring: \"secret\" # svccfg -s xvm/xend setprop config/vnc-listen = astring: \"0.0.0.0\" # svccfg -s xvm/xend setprop

Hi, I have a problem similar to the previous poster (thread: Virtual network of DomU''s), but apparently not with similar solutions... Situation: - two physical links aggregated to "default0" - dladm create-vlan on default0 with several different vlans - xVM DomU running linux connected to the same vlans when trying to ping the DomU from Dom0, I can see with snoop (in Dom0)

> Use an Intel pro/100 or pro/1000 driver..they are known to > work with VLANs. > > I guess it's also possible that it's a problem in the > bridging code, so try the latest kernel > as well... I compiled the latest 2.6.19 kernel and tested it with two 3COM 3c905c fast ethernet interfaces which work fine with vlan 802.1q tagging, but when I have added the eth0 and eth1

Hi, I'm inter-connecting AccessPoints using a tinc mesh and have bridge-nodes to bridge this vpn into some existing backbone. The AccessPoints bridge their users into 802.1q VLANs (per WiFi-Client, there can be multiple VLANs active on each AP) in the tinc mesh, and the bridge nodes bridge some vlans into the backbone. Now there is a router in the backbone that uses the same MAC on all VLANs,

OK, thanks again for all your help. I have resolved this, finally. The problem was that I configured VLAN 48 as the native VLAN on the trunk port.That was a mistake as apparently the native VLAN is the one where Cisco does not bother to tag packets. For now I set the native VLAN to VLAN 1 and that works. Cheers, Boris. On Sun, Jan 25, 2015 at 7:13 PM, Boris Epstein <borepstein at

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