similar to: Proper use of MASQ in Multi-ISP config

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

-----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. I''m running linux box with Slackware 9.1 and compiled kernel 2.4.31 with "yes" to VLANs and "yes" to all QoS. On this box i have more ethernet interfaces: eth0 eth1 eth2 and so as more vlan interfaces: eth0.100 eth1.3 eth1.4 This is entrace(uplink) router to our whole network and my goal is to shape users on this machine. I want for this purpose use HTB so

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.

Package: src:xen-api Severity: wishlist I've tried to configure VLAN using XCP + openvswitch using Wheezy, though it's still not fully working, I think VLAN configuration on dom0 can be better documented. It's fair easy to configure VLAN in Debian. First you need to ensure that your physical switch is in trunk mode, which means it will pass all kinds of VLAN tagged network flow, and

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

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:

Hey, Is it possible to configure various vlan interfaces via a kickstart install? For example: # vlan 101 network --device eth0.101 --bootproto static --ip=10.10.10.10 --netmask= 255.255.255.0 # vlan 102 network --device eth0.102 --bootproto static --ip=10.11.11.11 --netmask= 255.255.255.0 Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello, I have a xen server that needs to run a domU on a different vlan than xen''s. I have configured my switch (a cisco catalyst) to tag every untagged packet to the default vlan (the one in which is dom0) and to accept tagged packets (for that domU). I have xenbr0 linked with the eth0, the default network. Then I run * vconfig add eth0 101 -> To create a virtual interface with

Hi all ls centos supporting vlan setup? ls it reliable? how can I do it? Thank you --------------------------------- Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail -------------- next part -------------- An HTML attachment was scrubbed... URL:

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

Does facter support NICs that are not named ethX? I happen to use custom names on my systems. Just a quick look at the code I don''t see why it wouldn''t but the behavior I am seeing is very different. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To

Hi, Attached is patch for correcting zones in Samples6 for iv6 Thanks Togan ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters.

Shorewall 4.4.19.4 is now available. Problems corrected in this update: 1) Previously, the compiler would allow a degenerate entry (only the BAND specified) in /etc/shorewall/tcpri. Such an entry now raises a compilation error. 2) Previously, it was possible to specify tcfilters and tcrules that classified traffic with the class-id of a non-leaf HFSC class. Such classes are