similar to: Problems compiling patched bridge-utils

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

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

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

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

imq and htb are used to control traffic. When I create a bridge with the bridge-utils, I get a new device : br0. I can shape traffic on this device, but I can not use iptables to mark packets. I used ipmode http://www.linuxvirtualserver.org/~julian/#bridging my kernel is 2.4.19 when i compile kernel I get the following error: br_forward.o error 1 first_rule error 2 if I used ipmode, then I can

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

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

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

Hello, I''m playing with tc, htb, and other QoS features on an old pc I have. The PC runs, by now, a shrinked version of Debian Woody, with patched versions of kernel 2.4.18 and iproute in order to support HTB. What i''m wondering is if with a AMD 100Mhz (stealed from a museum ;-), 16Mbps RAM i can do bandwidth management to 20 network hosts, which connect wirelessly (not all,

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

Hola buenos días, una pregunta que quiero realizar de R sobre el tema de la licencia y que me inquieta un poco, a ver si alguien me la puede responder de un modo suficientemente claro o referirme a algún sitio donde informarme porque yo por el momento estoy un poco liado. Imaginemos el siguiente ejemplo. Una empresa crea un software totalmente basado en R para comercializarlo o alguien realiza