search for: set_name_type

...two vlans, 4 and 51. My question is this: should the vlan interfaces on the linux firewall be created first, then bridged; or should the bridge interface be created, then vlans bound to that? Here's the first: ip link set eth0 up ip link set eth1 up vconfig set_bind_mode PER_DEVICE vconfig set_name_type DEV_PLUS_VID_NO_PAD vconfig add eth0 4 vconfig add eth1 4 vconfig add eth0 51 vconfig add eth1 51 ip link set eth0.4 up ip link set eth1.4 up ip link set eth0.51 up ip link set eth1.51 up brctl addbr br0 brctl addif br0 eth0.4 brctl addif br0 eth1.4 brctl stp br0 off ip link set br0 up brctl addbr...

I just added 802.1Q VLAN support to redhat initscripts. And after support was ready, I tried to restart shorewall. Well it blew into pieces. Seems like shorewall can''t handle device names like: eth0.3 very properly. That''s default naming of vlan devices. eth1 is master device and 3 is id of my test vlan. So when I added to interfaces line: home eth0.3 detect seems like

...There are also some (occasional) messages from the dhcp server like "ip length 576 disagrees with bytes received 590" followed by "accepting packet with data after udp payload". I'm using kernel.org's 2.6.17.11. The bridge is created like this: ifconfig eth1 up vconfig set_name_type DEV_PLUS_VID_NO_PAD brctl addbr br0 for i in <range of vlan tags>; do vconfig add eth1 $i vconfig set_flag eth1.$i 1 0 brctl addif br0 eth1.$i done for i in <range of vlan tags>; do ifconfig eth1.$i up done ifconfig br0 <internal-ip> Note that eth1 doesn't g...

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

Hi, I am facing issues after upgrading one of the server from rhel5.5. (86_64) to latest rhel5.7 (86_64). The server is under trunk configuraion. I have set the network bridge as follows: #!/bin/bash vconfig set_name_type DEV_PLUS_VID_NO_PAD dir=$(dirname " $0" /etc/xen/scripts/network-bridge $@ vifnum=1 bridge=xenbr2 netdev=bond0.10 /etc/xen/scripts/network-bridge $@ vifnum=2 bridge=xenbr3 netdev=bond0.12 /etc/xen/scripts/network-bridge $@ vifnum=3 bridge=xenbr4 netdev=bond0.15 /etc/xen/script...

...bond1 : eth2 & eth3 are attached to bond1, where physical ip has been set . In the /etc/xen/xend-config.sxp, I am using (network-script *multi-network-bridge*) , the multi-network-bridge is as follows: [root@lnhst039 scripts]# cat multi-network-bridge #!/bin/sh # vconfig set_name_type DEV_PLUS_VID_NO_PAD dir=$(dirname "$0") #------------------------------------------------------------------------- /etc/xen/scripts/network-bridge $@ vifnum=1 bridge=xenbr2 netdev=bond0.12 /etc/xen/scripts/network-bridge $@ vifnum=2 bridge=xenbr3 netdev=bond0.13 /etc/xen/scripts/netw...

...t $BR_NAME $BR_IF_DMZ $BR_IF_DMZ_COST" for file in $BR_NAME $BR_IF_DMZ $BR_IF_MZ; do echo "1" > /proc/sys/net/ipv4/conf/${file}/proxy_arp; echo "1" > /proc/sys/net/ipv4/conf/${file}/forwarding; done; # Setup VLAN Interfaces # Use vlan<id> name type $VCONFIG set_name_type VLAN_PLUS_VID_NO_PAD while read conf ; do case "$conf" in \#*|"") ;; # Ignore empty lines and comments *) pattern=[[:space:]]*\#* vlan="${conf%%$pattern}" # Remove Whitespaces and comments # Add VLA...

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