QoS in multi-bridge network

Hi,
In a point-to-multipoint bridge network (1 bridge as root the others as non-root) bandwidth is shared equally. Is there a way to let for instance one non-root bridge have 4 Mbps and the other non-root bridge 2 Mbps?
Thanks,
Joost Koopmans

The simplest answer is to set the non-roots that should have the highest data rate to Basic/Basic/Yes/Yes on the 1/2/5.5/11 settings and those that should get less bandwidth at Basic/Basic/Yes/No.
Matthew Wheeler
Chief Wireless Architect
Blue Modal

Similar Messages

Voice vlan priority across wireless bridge network

Hello,
If you have a separate voice vlan across a wireless bridged network, how could you configure qos to put the entire voice vlan in priority over the data vlan ?
Thanks.

Hi Antonis,
Have a look at these docs. Hopefully they will help get you started;
Cisco Aironet 1300 Series Outdoor Access Point/Bridge Software Configuration Guide, 12.3(4) JA
Chapter 14 - Configuring QoS
This chapter describes how to configure quality of service (QoS) on your access point/bridge. With this feature, you can provide preferential treatment to certain traffic at the expense of others. Without QoS, the access point/bridge offers best-effort service to each packet, regardless of the packet contents or size. It sends the packets without any assurance of reliability, delay bounds, or throughput.
From this doc;
http://www.cisco.com/en/US/products/ps5861/products_configuration_guide_chapter09186a00804158a6.html
Giving Priority to Voice Traffic
This section demonstrates how you can apply a QoS policy to your wireless network's voice VLAN to give priority to wireless phone traffic.
In this example, the network administrator creates a policy named voice_policy that applies voice class of service to traffic from Spectralink phones (protocol 119 packets). The user applies the voice_policy to the incoming and outgoing radio ports and to the outgoing Ethernet port for VLAN 77.
Use the Apply Policies to Interface/VLANs drop-down menus to apply policies to the access point Ethernet and radio ports. If VLANs are configured on the access point, drop-down menus for each VLANs' virtual ports appear in this section. If VLANs are not configured on the access point, drop-down menus for each interface appear.
From this doc;
http://www.cisco.com/en/US/products/ps5861/products_configuration_guide_chapter09186a00804158a6.html#wp1047736
Hope this helps!
Rob
Please remember to rate helpful posts.......

Problems with SRW224G4 switch and Bridged Network Cards

Hello,
We have recently installed a SRW224G4 switch and have discovered that when we plug our DELL PowerEdge 2900 server into the switch, the switch loses all network connectivity and all of the LED's on the switch start flashing.
The server works perfectly well plugged into another switch, but as soon as we introduce the SRW224G4 into the network, either with the server plugged into that switch or any other, the problem re-occurs.
The only way we found we could eliminate this issue was if we disabled the Bridged Network connection on the two network cards on the server. If we do that, everything is fine, except the network performance of the server has dropped significantly.
The server is plugged into the 1GB ports on the switch, although we tried it on the 100MB ports and received the same problems. The switch reports that the ports are running at full-duplex.
Has anyone noticed this behavior before, and more importantly been able to rectify it.
Thanks in advance for your assistance,
Paul

I had this problem as well with any Linksys 2024 or rackmountable switch.. The trick is, you need to use the network cards management software to "team" or bridged the 2 NIC's otherwise the switch detects a loop and the whole thing locks up. So lame... Windows built in bridge mode stinks dont use it. When you use the Intel management software or Dell or HP's NIc management software you have the option to actually choose "redundant mode" where you can pick a Nic to be the primary, or you can choose Load Balancing where you can essentially double your throughput by joining the 2 nics.
In Windows 2008 Server, you actually do this by going to the Properties on the NIC in Device Manger. the software controls are now built right into the driver. pretty neat. 2003 you can check Device Manager the same way but not sure if it's the same as 2008, you might need to run the actual NIC management app.
Hope this helps
fdigi

Multi company network

Hi!
I’m asked to setup a multi company network. There will be approximately 4-8 small companies around 8-15 people in each company.
These companies will share some resources as printers and probably a nas. Furthermore they will have their own wlan ssid trunked from E0/7 to the AP.
Thinking about using asa5505 security plus license. AP will be this one AIR-SAP1602I-E-K9. As of now to allow more ports for users I will just hock up small simple switches to each Ethernet port on the ASA. When there are no more room I will buy a vlan capable switch.
Each company per vlan.
company1 Vlan10 192.168.10.0/24
company2 Vlan20 192.168.20.0/24
company3 Vlan30 192.168.30.0/24
company4 Vlan40 192.168.40.0/24
Shared Vlan100 192.168.100.0/24, printer ip 192.168.100.10
The companies should be separated from each other and only able to access the internet and the printer vlan. I got public ip in a 248 subnetmask giving me 6 addresses.
Company1 need to have 1 private ip. Also given ability to access their desktop PC from home. Other companies could share the same public IP.
Copmany2 will host a web server so it also needs a public ip accessible from outside.
Setting up Vlan and interfaces is no problem. The problems for me starts when creating NAT rules. Guess I will not use same-security-traffic permit inter-interface and use ACL.
How should you managed the traffic flow?
Br
Fredrik

You're on the right track.
One VLAN per company, each assigned to an interface, no same-security-traffic. Make them all security level 100. Make the printer VLAN 90.
Create a remote access VPN for company 1 with split tunnel and only give them route to their assigned network. Make the nat rule for them as nat(company1,outside) with dynamic translation to the outside interface. Make separate nat rules for the other companies as well with dynamic translation to one of your other public IPs. Make one specific port forwarding NAT rule for the company 2 webserver.

Qemu - Bridged networking with wireless adapter

How can I use bridged networking with wireless on Qemu virtual machine? With virtualbox it can be easily done. I don't why in Qemu it is so complicated, maybe virtualbox have completely difference mechacnism on this. I've read the wiki, it looks like impossible to use wireless for bridged networking. If it is really impossible, why virtualbox can do it?
And, in arch wiki's qemu manual, i didn't see how to use NetworkManager there to do bridged networking. Since, I use NetworkManager and disable the others (like netct and dhcpcd), it make it even more complicated. But, maybe it's because me that don't understand. Maybe someone experienced here can give me a way around this?

bagol wrote:How can I use bridged networking
It's up to you to set up the bridged network - or use TAP, e.g.:
ip tuntap add dev <devname> mode tap user <youruser>
ip lin set <devname> up
ip route ...
... and proxy_arp
... and iptables forwarding & masquerade
It's a good learning experience, to set up the network yourself, rather than have VirtualBox do similar things by *magic*

Bridged networking not working with nested VMware Workstation

I am having an issue that I can't seem to find any answer to....
We are running Vsphere 5.5 and I have 2 Guests each running Windows 7 64-bit. Each of these guests has VMware Workstation 10 running on them. When we P2V the systems we followed all the instructions to allow nested VMware Workstation. However, we are running into an issue where the Bridged Networking will not work. Both of the Win7 guests are on the same vlan and all of the VMs in Workstation are on the same network as well. However, while the 2 Windows 7 guests can ping each other and each of the guests can ping the VMs that are hosted locally, they cannot connect to the systems on the other guest running workstation.
I tried to upgrade the Guest NIC to VMXNet3, but that did not help.
All of the research I have done brings me to people who are having the opposite problem (ESXi nested in VMware Workstation).
How can I get the 2 bridged networks to connect?
Thanks!

The ESXi vSwitch to which the outer guests are connected must be configured for promiscuous mode and forged transmits.

Bridge Network Adapters Always Start Disconnected

I've been working on this for two weeks with no success. Everytime I reboot my server, Windows Server 2008 R2 & VmWare Sever 2.02 any VMs that are set to bridged networking boot with their network adapter set as disconnected. It requires a manual "click" of the checkbox to turn on the network adapter. I have been using VMware server since version 1 and have never had this problem. One unusual thing is the Manager Virtual Networks Auto-Bridging doesn't seem to show any network adapters, although networking continues to work. If I set my VM to NAT or host only my adapter starts connected, as it should.
Things I have tried:
Uninstall VmWare server & Reinstall
Uninstall and create various VM Hosts, all do the same, pre-compiled applicanece and all costum built.
Moved host images to another server (works fine)
Checked to make sure Bridge Protcal is installed on ethernet adapter, even removed and readded.
Uninstalled and reinstalled ethernet adapter (Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20)
This is a Windows Server 2008 R2 box with lots of ram and plenty of resources only running spiceworks & splunk in a test capacity. Using this machine for testing and pre-deployment but it's virtual machines need to act like they would in production.
Any help would be greatly appreciated.
Thanks

Opps typo, I moved the VM images to different hosts, Windows server 2003, 2008 and 2008 R2. My home box runs 2008 R2 and Vmware server nicely together without this issue. Hence why I'm at a loss.
Thanks for your interest.

[Solved]Vbox 3.1.2 - Bridged networking stopped working on Arch guest

After upgrading Virtual Box to 3.1.2 (both ose and puel versions apply here) bridged networking stopped working on an Arch guest which I use as a test server.
While writing this post I solved the problem. What I did was to enable NAT on the first adapter and Bridging on the second. After booting into to the guest I did the following;
# ifconfig eth1 up
# dhcpcd eth1
I shutdown the guest and removed the NAT adapter so only the bridged one remained, booted it and voilá for some mysterious and unfathomable reason bridging now works again.

After upgrading Virtual Box to 3.1.2 (both ose and puel versions apply here) bridged networking stopped working on an Arch guest which I use as a test server.
While writing this post I solved the problem. What I did was to enable NAT on the first adapter and Bridging on the second. After booting into to the guest I did the following;
# ifconfig eth1 up
# dhcpcd eth1
I shutdown the guest and removed the NAT adapter so only the bridged one remained, booted it and voilá for some mysterious and unfathomable reason bridging now works again.

QEMU/KVM bridge networking howto

Hello all,
I had a dialog here: https://bbs.archlinux.org/viewtopic.php?id=145177 but I inadvertently hijacked the OP thread, for that I deeply apologize and decided to start my own thread.
I've been struggling with getting my bridge networking working with QEMU/KVM. I would love to get my KVM Windows 7 install working with bridge network so I can access my internal lan, but so far I am out of luck. When I follow the Wiki's I completely hose my network settings and can't get online with my Arch host.
I've followed the wiki's here:
https://wiki.archlinux.org/index.php/QE … al_network
should I be using this wiki instead:
https://wiki.archlinux.org/index.php/KV … Networking
I'm kinda confused on how to approach this since there are separate wikis for QEMU and KVM.
I have a couple of confusing questions, that I hope someone can answer, or lead me in a direction to help me find a solution. Free internet beer for helping.
From a vanilla install of Arch, if I would like to run Windows 7 64-bit in a VM, should I use QEMU or KVM? I did get the windows 7 up and running, not sure how, but it's not on my internet LAN, the VM can only access the internet.
Can someone help me out step by step or pointing me in a direction that can help get a bridge network set up between my host, which will need a static IP address, and my VM, which I would prefer to have another static IP address on my network.
I've tried using virtualbox but the performance was slower than using QEMU/KVM.
BTW, what's the difference between QEMU and KVM? I'm confused by that as well. I would even be willing to write up a "beginners guide" if I can get help getting mine set up.
any help is greatly appreciated.
--nixIT

I do things manually on my system so, for two VM:
ip tuntap add dev tap0 mode tap user djgera
ip tuntap add dev tap1 mode tap user djgera
brctl addbr br0
brctl setfd br0 0.0
brctl addif br0 eth0
brctl addif br0 tap0
brctl addif br0 tap1
ip link set dev br0 up
ip link set dev tap0 up
ip link set dev tap1 up
ip addr del 192.168.0.77/24 dev eth0
ip addr add 192.168.0.77/24 broadcast + dev br0
ip route add default via 192.168.0.1
then each qemu-kvm instance that I lauch add:
-device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:00 -netdev type=tap,id=net0,ifname=tap0,script=no,downscript=no
-device virtio-net-pci,netdev=net1,mac=52:54:00:12:34:01 -netdev type=tap,id=net1,ifname=tap1,script=no,downscript=no

[SOLVED] KVM and Bridged Networking

I've got KVM working and a Windows 2008 server installed on a image now, but it's only getting a NAT ip address. I need to get this server onto my main network, on Windows I'd use Virtual Box and Bridged Networking, but I thought I'd give KVM a try out.
I've followed the setup at https://wiki.archlinux.org/index.php/KV … Networking
Using Netcfg
Bridged networking is used when you want your VM to be on the same network as your host machine. This will allow it to get a static or DHCP IP address on your network, and then you can access it using that IP address from anywhere on your LAN. The preferred method for setting up bridged networking for KVM is to use the netcfg package. You will also need to install bridge-utils.
Netcfg#Configuring_a_bridge_for_use_with_virtual_machines_.28VMs.29
And this page https://wiki.archlinux.org/index.php/Ne … _.28VMs.29
I've got a bridge working I believe (all my stuff is DHCP by the way)
Output of ifconfig
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 metric 1
inet 192.168.1.52 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::21d:7dff:fea9:bb2f prefixlen 64 scopeid 0x20<link>
ether 00:1d:7d:a9:bb:2f txqueuelen 0 (Ethernet)
RX packets 2966 bytes 520670 (508.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2351 bytes 1874150 (1.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 metric 1
ether 00:1d:7d:a9:bb:2f txqueuelen 1000 (Ethernet)
RX packets 2977 bytes 570261 (556.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2364 bytes 1875202 (1.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 45 base 0xc000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436 metric 1
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 72 bytes 7056 (6.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 72 bytes 7056 (6.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
I've got "bridge" added to my rc.conf as a MODULE which is loaded. (I saw reference to this somewhere else on the forum that this might be needed)
I'm starting my VM with the following command
qemu-kvm -vnc 192.168.1.52:0 -hda Nekomi -m 2048 -smp 2 -net nic
Yet I still can't get an IP outside of the 10.0.0.0 range on the VM.
The VNC line above is because the HOST has not VGA output at all, completely headless.
I'm trying to get this working and trying to learn at the same time. KVM is new to me, as is bridged networking on linux.
Any ideas? Thanks
Last edited by Naijeru (2012-09-18 16:28:20)

Sorry for the delay, bit a PC rebuild occurred :-(
Anyway, I managed to get this working with steps #1-#7 from the linked section. Thanks for that. I did have a few minor issues in getting a DHCP on the host machine itself, turns out I'd missed a single ) from the daemons section of rc.conf. A human error, but difficult to fix as the machine was rendered off the network and without a VGA card... fun!
I diverge, I have this script to bring up a bridge when the qemu-kvm starts
#!/bin/sh
echo "Executing /etc/qemu-ifup"
echo "Bringing up $1 for bridged mode..."
sudo /sbin/ifconfig $1 0.0.0.0 promisc up
echo "Adding $1 to br0..."
sudo /usr/sbin/brctl addif br0 $1
sleep 2
But when the kvm shutdowns it complains it can't find qemu-ifdown script. So I'm thinking of making one but just want to check it over first.
#!/bin/sh
echo "Executing /etc/qemu-ifdown"
echo "Removing $1 from br0..."
sudo /usr/sbin/brctl delif br0 $1
echo "Taking down $1 from bridged mode..."
sudo /sbin/ifconfig $1 0.0.0.0 promisc down
sleep 2
I've reversed the logic here, is the above the correct way to bring down the guest interface?

Tap0.device issues while attempting to start bridged network

i'm trying to get the bridged network working so i can run xen and everytime i try sudo netctl enable xenbridge-dhcp i get this error in journalctl.
-- Logs begin at Wed 2013-05-15 14:16:16 PDT, end at Tue 2013-05-28 18:26:42 PDT. --
May 28 18:25:07 kimbra sudo[23762]: pam_unix(sudo:session): session closed for user root
May 28 18:25:12 kimbra sudo[23764]: jd : TTY=pts/1 ; PWD=/home/jd ; USER=root ; COMMAND=/usr/bin/netctl start xenbridge-dhcp
May 28 18:25:12 kimbra sudo[23764]: pam_unix(sudo:session): session opened for user root by (uid=0)
May 28 18:25:12 kimbra systemd[1]: Expecting device sys-subsystem-net-devices-tap0.device...
-- Subject: Unit sys-subsystem-net-devices-tap0.device has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Unit sys-subsystem-net-devices-tap0.device has begun starting up.
May 28 18:26:42 kimbra systemd[1]: Job sys-subsystem-net-devices-tap0.device/start timed out.
May 28 18:26:42 kimbra systemd[1]: Timed out waiting for device sys-subsystem-net-devices-tap0.device.
-- Subject: Unit sys-subsystem-net-devices-tap0.device has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Documentation: http://www.freedesktop.org/wiki/Softwar … e9d022f03d
-- Unit sys-subsystem-net-devices-tap0.device has failed.
-- The result is timeout.
May 28 18:26:42 kimbra systemd[1]: Dependency failed for xen bridge.
-- Subject: Unit netctl@xenbridge\x2ddhcp.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Documentation: http://www.freedesktop.org/wiki/Softwar … e9d022f03d
-- Unit netctl@xenbridge\x2ddhcp.service has failed.
-- The result is dependency.
May 28 18:26:42 kimbra sudo[23764]: pam_unix(sudo:session): session closed for user root
tap0.device is not working and i can't find the uml_utilities package anywhere.
help?

Sorry for the rather late response, but I've just been through this issue myself. The tunctl & brctl utilities are now part of 'uml_utliities', which is itself deprecated.
I downloaded uml_utilities and installed it.
I've encountered a bug which appears to be common to all bridged netwroking (the inbuilt VirtualBox bridging demonstrates the same problem). The nature of the bug is that if I bridge with the physical ethernet adapter, only a linux guest VM can see the outside world. THis is true whether the guest is running under VirtualBox or KVM so the issue appears to be generic.
Non-linux guests can see each other and the *host*, but not the rest of the world. Speculations as to the reason include the deprecation of Uml_Utilities, but regardless, I tried something different.
I created the bridge and assigned it a separate subnet. I added some tap interfaces. I ran a DHCP server instance listening on the bridge alone. I set forwarding on, and created a static route enabling my router to find the virtual subnet.
I used dnsmasq for the DHCP as it isn't used by my regular network setup, meaning that I can screw around with it trivially without breaking things. Additionally, I set up the config automatically from my vnet script. I can potentially add multiple virtual subnets this way although I haven't included support in the script as yet. The minimal config hands out addresses from the pool specified on the vnet command line, and I can set up static addresses on the same subnet by referencing the contents of /etc/host and /etc/ethers (it identifies vms by mac address).
This works perfectly, and has the advantage that the virtual network traffic will route via wireless as well as cabled ethernet. It also makes it simple to firewall the virtual subnet and reduces the risk of experiencing minor hassle when my broken vnet code stuffs the ethernet interface.
Ping me if you want a copy of the vnet script, although it's still very much a work in progress.
Last edited by salafrance (2013-09-21 20:02:12)

Another KVM Bridged Networking Thread

Hello everyone,
I'm having some trouble getting KVM bridged networking to work following the instructions here:
http://wiki.archlinux.org/index.php/Qem … _with_QEMU
The VM I set up to test is running CentOS 5.5 and is unable to get an IP address. Here's what I run before attempting to start it:
Turn off wireless:
% sudo netcfg -a
Running 'ip link sh' shows that wlan0 is down after this.
Allow forwarding and adjust iptables:
% su -c 'echo 1 > /proc/sys/net/ipv4/ip_forward'
% sudo iptables -P FORWARD ACCEPT
% cd /proc/sys/net/bridge
% su -c 'for f in bridge-nf-*; do echo 0 > $f; done'
Start the bridge:
% sudo brctl addbr br0
% sudo brctl addif br0 eth0
% sudo ip link set up dev eth0
% sudo dhcpcd br0
Occasionally br0 times out and I have to run dhcpcd twice, but it comes up eventually. I can ping out to the Internet at this point.
I believe that when I start my VM at this point tap networking is supposed to work, but obviously I am doing something wrong. I have tried starting it both as root and as my regular user. For reference, here is my run-qemu script:
#!/bin/sh
USERID=`whoami`
IFACE=`sudo tunctl -b -u $USERID`
MAC=`echo -n "FF:FF"; for n in 1 2 3 4; do echo -n ":" && cat /dev/urandom | tr -dc '0-9A-F' | head -c 2; done`
qemu-kvm -daemonize -net nic,macaddr="${MAC}" -net tap,ifname="${IFACE}" \
-k en-us -m 512 -smp 2 $*
sudo tunctl -d $IFACE &> /dev/null
...and my /etc/qemu-ifup script:
#!/bin/sh
echo "Executing /etc/qemu-ifup"
echo "Bringing up $1 for bridged mode..."
sudo ip link set dev $1 up
echo "Adding $1 to br0..."
sudo /usr/sbin/brctl addif br0 $1
sleep 2
I originally used 'sudo /sbin/ifconfig $1 0.0.0.0 promisc up' in place of 'ip link set ...' but without any different results. I have also tried a completely empty iptables ruleset, with all chains set to ALLOW, just in case; no dice.
Does anyone have any ideas? Thanks for any help you can provide, I appreciate your time.

try setting a static ip first for both br0 and the qemu tap interface, and see if the host and VM are able to communicate properly, if they cant, dont add the tap interface to br0, assign the tap interface an ip, and see if you are able to communicate with the VM.

BlackMagic Multi Bridge Pro. Vs. Kona 3

I am looking to purchase a new HD Capture Card for my edit suite.
Currently I am using the BlackMagic 6.6.2 SD card. I have been looking at the Blackmagic Multi Bridge Pro and the Kona 3.
It looks like the Blackmagic card connects to its breakout box using a PCI Express Connection rather then the Mini HD SDI connectors on the Kona3. Is there a benefit to one over the other? Also can you capture your footage using Pro Res with both cards?
Within a lot of the posts that I have read I have been steered towards getting the Kona3, if anyone knows why this would be a better choice then the BlackMagic Multi Bridge could you fill me in.
Thanks!
Jesse

The Kona 3 can upconvert SD to 720p and 1080i. THe Decklink can only upconvert SD to 1080i.
The Kona 3 can cross convert 720p 23.98 to 1080p 23.98 upon output...in real time. So DVCPRO HD 720p24 to HDCAM 1080psf23.98. The Decklink cannot.
The Kona 3 does not have Analog inputs...the Decklink does. For that, you will need the HD10AVA adapter.
Or get the AJA I/O HD...it does absolutely EVERYTHING but uncompressed 4:4:4 HD or 4:2:2 HD. IT will do Pro Res and DVCPRO HD, but it cannot capture uncompressed HD. No biggie for some. But...just letting ya know.
Shane

Has anyone used the Black-Magic Design Multi Bridge?

Currently I have a Black Magic Multi Bridge Extreme. It works, but there seems to be an issue with a very (hot) running unit. The fan is running (very loud I might add), and does seem to cool down the unit, just a bit. If there is anyone using this or simular unit, could you provide some feed back. Thanks

brett austin wrote:
I've got a new Mac Mini running HDMI to a 40" Sony Bravia Flat Panel... works fine.
I do have an issue when I turn on the TV and wake the Mini from sleep... the screen stays really dim. Not sure if it's the Mini or the TV that's the issue. After the Mini is fully on... a power cycle of the TV seems to bring everything back to normal.
Brett, I have the same problem when I bring the mac out of sleep mode. Have you managed to find out why we have to switch the TV Off then On again to get the picture? Or another solution? Very annoying when you have 1000's $ worth of equipment but the solution is still "Have you tried switching it Off and On again" (All due respects to the "IT CROWD").

Bridged network only gets UDP broadcast traffic?

I've created a bridged network Mac OS X 10.8.5 using ifconfig and TUNTAP for OS X to bridge my wireless connection, en0, with a virtual interface, tap0, which I can use for guest VMs:
        $ sudo sysctl -w net.inet.ip.forwarding=1
        $ sudo sysctl -w net.link.ether.inet.proxyall=1
        $ sudo sysctl -w net.inet.ip.fw.enable=1
        $ sudo ifconfig bridge0 create
        $ sudo ifconfig bridge0 addm en0 addm tap0
        $ sudo ifconfig bridge0 up
        $ ifconfig
        en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
                  ether 28:cf:xx:xx:xx:xx
                  inet6 xxxx::xxxx:xxxx:xxxx:xxxx%en0 prefixlen 64 scopeid 0x4
                  inet 192.168.100.64 netmask 0xffffff00 broadcast 192.168.100.1
                  media: autoselect
                  status: active
        bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
                  ether ac:de:xx:xx:xx:xx
                  Configuration:
                            priority 0 hellotime 0 fwddelay 0 maxage 0
                            ipfilter disabled flags 0x2
                  member: en0 flags=3<LEARNING,DISCOVER>
                           port 4 priority 0 path cost 0
                  member: tap0 flags=3<LEARNING,DISCOVER>
                           port 8 priority 0 path cost 0
        tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
                  ether ca:3d:xx:xx:xx:xx
                  open (pid 88244)
I'm using this with QEMU and the guest VM never gets a DHCP lease. If I `tcpdump -i tap0`, I only see broadcast traffic. Shouldn't I see a mirror of everything on en0? (192.168.100.33, the host doing the broadcasting, is another unrelate, noisy server on my LAN.)
Any ideas?

IGMP snooping may be enabled by default on the 6509. Disabling it may solve your problem.
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/122sx/swcg/snooigmp.htm#wp1020466

QoS in multi-bridge network

Similar Messages

Maybe you are looking for