similar to: [Bridge] two fields are missing in brctl output when using /sys

Hi, I noticed that brctl (or more accurately, libbridge) is using the wrong path when doing various lookups in sysfs: e.g. /sys/class/net/brXXX/stp_state when it should use /sys/class/net/brXXX/bridge/stp_state. This doesn't cause any problems on most systems as it falls back to the ioctl when the sysfs attempt fails; however the ioctl method is apparently deprecated. I believe the

Good day Folks! Working on a bridging firewall/gateway and attempting to solve the age-old mystery of whether I can get NAT to work across a gateway that has 2 NICs and requires a bridge... Upside is, I have the gateway working, bridging works (as does OpenVPN using that bridge). But NAT does not in Fedora Core 4... >From dmesg: Linux version 2.6.11-1.1369_FC4 So I went to the website and

Hello, I''ve applied ``bridge-utils-0.9.5-ipmode-1.diff'''' to be able to use my shaper as bridge and don''t lose the netfilter capabilities, the patch applies with no error messages, which makes me supose everything is working fine. But when i try to recompile the bridge-utils utilities i get the message transcript below:

I had an odd situation yesterday, klibc 1.5.17 ipconfig was trying DHCP on all 3 NICs in the server, but one has a bad switch that causes the link on eth2 to go up/down every 10 seconds. IPconfig would just time out. If I tell ipconfig to only try eth0, then DHCP address is configured, and the netboot proceeds 100%. I'll take a peek at the code but maybe someone here is familiar with the

I noticed that when I type brctl - it does insmod when the bridge module is not loaded. Where can I find the code (in the brctl or libbridge code) which does that? Thanks, Abhijit

Hi, The attached patches enables the bridge to filter and forward packets according to their IEEE 802.1q headers. The goals behind this change include : - Enable running STP on 802.1q tagged networks. STP packets must be untagged. It isn't obvious how else to enable STP with the current bridge and vlan code. - Add native support for an untagged vlan. Currently an untagged vlan can

The current "ipconfig -i any" option waits for all interfaces, however a feature that I would really like is to continue after the first interface that gets a valid configuration. This is useful in the scenario where an (diskless) host with 2 or more NICs giving redundant connectivity is being network booted. It is valid to continue booting as long as at least one NIC is functional, in

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

Hi, I use the libbridge and an other lib (libnl) in a same project. I include the headers files of the two lib (libnl first and libbridgge after) and I've a conflict with the inclusion of linux/if.h (in libnl headers) and net/if.h (in libbridge.h), I've this error : /usr/include/net/if.h:45: error: parse error before numeric constant /usr/include/net/if.h:111: error: redefinition of

Under newer kernels the bridge configuration parameters are located under /sys/class/net/$bridgename/bridge/$param, while the current bridge-utils code is trying to access them under /sys/class/net/$bridgename/$param. This patch fixes this issue in the bridge-utils code and so allows setting of bridge configuration parameters using sysfs under newer kernel versions. Signed-off-by: Anna Fischer

Under newer kernels the bridge configuration parameters are located under /sys/class/net/$bridgename/bridge/$param, while the current bridge-utils code is trying to access them under /sys/class/net/$bridgename/$param. This patch fixes this issue in the bridge-utils code and so allows setting of bridge configuration parameters using sysfs under newer kernel versions. Signed-off-by: Anna Fischer

Under newer kernels the bridge configuration parameters are located under /sys/class/net/$bridgename/bridge/$param, while the current bridge-utils code is trying to access them under /sys/class/net/$bridgename/$param. This patch fixes this issue in the bridge-utils code and so allows setting of bridge configuration parameters using sysfs under newer kernel versions. Signed-off-by: Anna Fischer

Hi, I think I detected some bugs in libbridge 1.2. Probably none detected them so far because of the fallback to ioctl() whenever anything fails. On my system (user 32 bits, kernel 64 bits) the fallback doesn't work. It would be nice BTW to have a compile time option that leaves the ioctl fallback out... Here's what I've found (first patch is a compilation patch I posted last

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

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

Dear Sir, I was trying to install bridge as we are installing scps gateway in our testbed.This requires us to install the bridge. Our Linux version is 2.4.18 ~3 and we are using redhat 7.2 Please let me know which is the bridge I should install and how to configure it. Before configuring the bridge what I should check in my configuration. Thanks for your time, Sincerely Rama ===== I hear