similar to: [Bridge] [PATCH] Crash on "brctl stp br0"

This patch adds basic Virtual Ethernet Port Aggregator (VEPA) capabilities to the Linux Ethernet bridging utilities. The patch provides functionality that depends on the Linux kernel patch 'net/bridge: add basic VEPA support'. This patch relies on the patch 'bridge-utils: fix sysfs path for setting bridge configuration parameters'. A Virtual Ethernet Port Aggregator (VEPA) is

This patch adds basic Virtual Ethernet Port Aggregator (VEPA) capabilities to the Linux Ethernet bridging utilities. The patch provides functionality that depends on the Linux kernel patch 'net/bridge: add basic VEPA support'. This patch relies on the patch 'bridge-utils: fix sysfs path for setting bridge configuration parameters'. A Virtual Ethernet Port Aggregator (VEPA) is

This patch adds basic Virtual Ethernet Port Aggregator (VEPA) capabilities to the Linux Ethernet bridging utilities. The patch provides functionality that depends on the Linux kernel patch 'net/bridge: add basic VEPA support'. This patch relies on the patch 'bridge-utils: fix sysfs path for setting bridge configuration parameters'. A Virtual Ethernet Port Aggregator (VEPA) is

This patch adds a 'hairpin' (also called 'reflective relay') mode port configuration to the Linux Ethernet bridge utilities. A bridge supporting hairpin forwarding mode can send frames back out through the port the frame was received on. Hairpin mode is required to support basic VEPA (Virtual Ethernet Port Aggregator) capabilities. You can find additional information on VEPA

This patch adds a 'hairpin' (also called 'reflective relay') mode port configuration to the Linux Ethernet bridge utilities. A bridge supporting hairpin forwarding mode can send frames back out through the port the frame was received on. Hairpin mode is required to support basic VEPA (Virtual Ethernet Port Aggregator) capabilities. You can find additional information on VEPA

This patch adds a 'hairpin' (also called 'reflective relay') mode port configuration to the Linux Ethernet bridge utilities. A bridge supporting hairpin forwarding mode can send frames back out through the port the frame was received on. Hairpin mode is required to support basic VEPA (Virtual Ethernet Port Aggregator) capabilities. You can find additional information on VEPA

I am doing some testing of openwrt'd wireless access points, using madwifi-ng'd atheros radios. In the test configuration, I have three devices in a triangle, each has wds links to the other two devices. The ath0 interface is in ap mode, ath1 is a wds link to one device, and ath2 is a wds link to the other device. All three interfaces (and an ethernet interface) are in a bridge (br-lan)

I've noticed for a while that # brctl showstp output is showing 0 for port_no and port_id It seems that somewhere in 2.6 sysfs land the following items got printed in hexadecimal, and brctl code was parsing for decimal only doug:/sys/class/net/eth0/brport# cat port_id 0x8001 doug:/sys/class/net/eth0/brport# cat port_no 0x1 The following patch to bridge-utils (git and 1.2 release) lets

On Wed, 16 Jun 2004 17:53:08 +0800 (CST) "vanyew" <vanyew@mail2000.com.tw> wrote: > Dear Stephen, > > I'm a Linux embedded developer. > We want to build the bridge function on our product. > > We use brctl to build the bridge device. > > [root@localhost /]# brctl show > bridge name bridge id STP enabled interfaces >

It appears that interfaces participate in STP's forwarding delay even when STP is disabled for a given bridge. I can remedy by setting the FD to 0 for each new bridge, but I'm wondering if this is by design or oversight. [root@ ~]# brctl show bridge name bridge id STP enabled interfaces br0.690 8000.00065b8bce3e no eth1.690

Hi, we're running the standard linux bridge setup (redundant bridge) for 5 years now. So first of all, thanks to everyone involved for implementing the bridging feature in Linux. Now I'm trying to bridge hosts connected to VLAN'ed Cisco switches using linux bridge. I'm testing the following setup (Kernel 2.6.19, bridge-utils 1.2 on both bridges)

All is in subject. Example : root@harobed:~ # brctl show bridge name bridge id STP enabled interfaces root@harobed:~ # ifconfig lo Lien encap:Boucle locale inet adr:127.0.0.1 Masque:255.0.0.0 adr inet6: ::1/128 Scope:H?te UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:16510 errors:0 dropped:0 overruns:0 frame:0

Hi! Jens Seidel reported a bug to Debian about a wrong message on brctl, you can see it at http://bugs.debian.org/383938, it is kind of the continuation of the ENODEV bug #348617 that was already patched by Stephen on the git. I have applied the same solution that Stephen applied for the first one, follows the patch against git plus a minor exclamation mark modification I did so that all ENODEV

hi: my box use eth0 connect my pc. but I type command "./brctl showmacs br0", no mac addr display and the" brctl showmacs program" not exit,always exec # ./brctl show bridge name bridge id STP enabled interfaces br0 8000.000123456789 no eth0 hdlc0 # ./brctl showmacs br0

I have been playing around with the STP settings of brctl and saw something strange. I was setting the hello time, so I executed the following: # brctl sethello br0 30 Then I had a look at the value that was set: # cat /sys/class/net/br0/bridge/hello_time 2999 Much bigger than expected. I started looking at the source. In the libbridge/libbridge_devif.c file of brctl, we have the following

Bridge locking for /sys/class/net/br0/bridge/stp_enabled was wrong. Another bug in bridge utilities makes it such that this interface, meant it wasn't being used. The locking needs to be removed from set_stp_state(), the lock is already acquired down in br_stp_start()/br_stp_stop. Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> --- a/net/bridge/br_sysfs_br.c

- Default NETWORKING=no in /etc/sysconfig/network - Update to yes when configuring network through TUI or firstboot - After configuration in TUI, (re)start ntp daemons rhbz#675870 Signed-off-by: Mike Burns <mburns at redhat.com> --- recipe/common-post.ks | 6 ++++++ scripts/network.py | 10 +++++++++- scripts/ovirt-config-networking | 1 + 3 files

--- scripts/network.py | 207 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 207 insertions(+), 0 deletions(-) create mode 100644 scripts/network.py diff --git a/scripts/network.py b/scripts/network.py new file mode 100644 index 0000000..28e32f2 --- /dev/null +++ b/scripts/network.py @@ -0,0 +1,207 @@ +#!/usr/bin/python + +from ovirtfunctions import * +import tempfile

On Wed, 13 Apr 2005 10:50:15 +0100 "Andre Santos \(Ecofilmes\)" <andre.santos@ecofilmes.pt> wrote: > Hi there, > > I want to have a computer betwen the internet and the network to see the trafic and control. > I used windows, but its somehow limited, and want to try linux... > I installed Fedora linux in server mode, and now Im trying to put 2 nics in bridge.

Hi, today a couple of Hypervisors got restarted due to a power outage. While the systems and the VMs on the are running fine multicast traffic between the guests is no longer working. I generate multicast udp packet using iperf in the guest and check on the host using tcpdump: tcpdump vnet0 => multicast packets are visible tcpdump vlanbr8 => multicast packets are visible tcpdump em1.8