similar to: Kickstart from tagged VLAN?

Hi I''m testing around with xen 3.0 snapshot from last week. And i''m now having a problem with a xenbr which is based on a vlan if (dot1q). this is all in dom0 os: debian testing network: tg3 I can start the bridge based on my normal physical eth0 which is working without any problems. My clan without bridge is also working. I can start the bridge based on a vlan if with help

Hi, I want to add 2 vlans by the following steps: 1. add the vlan interfaces: vconfig add eth0 100 --vlan100 vconfig add eth0 101 --vlan101 2. modify the network-bridge script by the websit, http://wiki.xensource.com/xenwiki/XenNetworking#head-04ebcc1760dbc4678e83b116afa310dc0612dc39 Comment each time ifup or ifdown commands are executed.The reason is that ifdown ends with

I think it should be sufficient to do as following: - create and test the vlans as normal (i think you already did this) - try to create the bridge as follows (for the first try without starting xend): # network-bridge start netdev=vlan100 bridge=xenbr0 at least this was working on my debian testing installation but i have a problem now with incorrect tcp checksums in dom0 or domU. See my

Hello, I''m trying to setup an 8 port wan configuration (pptp+pppoe) with one vlan trunk. My internal networks are : LAN(eth9): 10.0.0.0/16 VLAN10(eth9) 10.10.0.0/24 VLAN20(eth9) 10.20.0.0/24 VLAN30(eth9) 10.30.0.0/24 VLAN100(eth9) 10.100.0.0/24 I would like to post my configuration here since i don''t success to do the following: 1. Communicate between VLANxx to LAN

Hi all. What is the canonical way of getting xen to fully work with 802.1q (vlans) ? After (re)searching i found many ways but so far none is working. platform is gentoo (x86/32) and netwerk card a tg3. xen is v3. my config is as follows ... eth0 is simply up (with no ip) and i created several eth0.x interfaces corresponding to several vlans. eth0.10 is de ''default'' vlan

Hi, I am currently struggling with the right way to configure a bonding device via kickstart (via PXE). I am installing servers which have "eno" network interfaces. Instead of the expected bonding device with two active slaves (bonding mode is balance-alb), I get a bonding device with only one active slave and an independent, non-bonded network device. Also the bonding device

Hello All, I seem to have run into a bug with the new --bridgeslaves=<INTERFACE> option. It would seem that if I tell the bridge device to use a virtual interface (like bond0) rather than a physical interface (em1/em2) that kickstart completely barfs on it. I have provided my network section below which works fine as long as i don't enable all the bridge content. When the

Are there any new tools in CentOS 6 to configure VLAN interfaces (where the switch passes multiple tagged VLANs over one physical link to the host) or is it best to edit /etc/sysconfig/network-scripts/eth?.vlan# files manually? -- Les Mikesell lesmikesell at gmail.com

Using a kickstart file that stops with a curses dialog "You have multiple network devices on this system. Which one do you want to install through?" The machine being configured with PXEboot has two ethernet interfaces. What's missing from the network entries below? I'd like this install to proceed without asking which ethernet interface. PXE begins the install with DHCP, so

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a machine running 2.6.18-rc3 with a bridge config that looks like this: cr1:~# brctl show bridge name bridge id STP enabled interfaces vlan100 36b0.0007e90f40c1 yes eth0.100 eth2.100 vlan101 5dc0.0007e90f40c1 yes

Hello all, I need a virtual firewall/router solution. I''m thinking of a netscreen 1000 but I want to know if it can be done in Linux. Here is my idea: 1 Linux box 2 GigE interfaces 1 interface setup with a public IP address ($PUBIP) 1 interface setup with 802.1q VLAN trunking with 100 vlans assigned ($VLAN1-$VLAN100) a /25 subnet routed to $PUBIP from my core routers All $VLAN

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

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 =

Hello, I''m receiving this error while restarting/starting Shorewall : Processing /etc/shorewall/init ... WARNING: default route ignored on interface vlan20 WARNING: default route ignored on interface vlan10 WARNING: default route ignored on interface vlan30 WARNING: default route ignored on interface vlan50 WARNING: default route ignored on interface vlan100 My route -n

Hi all, I'm having a bit of trouble with something and was wondering if anyone else has encountered this or knows what the problem is. I have one computer I would like to kickstart a centos 5.0 or 5.1 install. I have another computer which is the tftpboot server and contains the centos 5.0 and centos 5.1 install directories I wish to do the kickstart over nfs and my network is using MTU

I just realized that I hadn''t actually asked a question when I posted this before. Let me try again... I am trying to configure a Linux box with all possible VLANs (4094 of them), and a subnet on each VLAN. Creating the VLANs isn''t a problem. But, when I try to use "ip addr add ..." commands to assign an IP address to each VLAN interface, I get to do about 280 of

> 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

Here is my script for post install if you want to try it. In order for the shuffling to not occur you do need to create the udev rules file somehow. I am not sure how mangled this will be in email but it is worth a try. It should run OK with nothing else. I have a better version in the works but the enhancements are mainly useful for Fedora 19-21. I did forget to say I also block

Hi all, Is it possible to have native VLAN (802.1q) and a VLAN x at the same time in DOMU''s? This is what I have configured on my DOM0 (xen2): Eth0 (connected by a 801.1q trunk to Cisco 2950 switch) Created vlan100 : vconfig eth0 100 Created bridge : brctl addbr br100 Attach switchport: brctl addif br100 eth0.100 Attach a DOMU : brctl addif br100 vif2.0 I now have bridge br100