Displaying 20 results from an estimated 400 matches similar to: "[Bridge] [PATCH] bridge-utils: fix sysfs path for setting bridge configuration parameters"
2007 Jul 31
1
[Bridge] brctl uses incorrect sysfs path
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
2007 Apr 18
0
[Bridge] libbridge<->sysfs interface - some bugs
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
2009 Jun 15
0
[Bridge] [PATCH][RFC] bridge-utils: add basic VEPA support
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
2009 Jun 15
0
[Bridge] [PATCH][RFC] bridge-utils: add basic VEPA support
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
2009 Jun 15
0
[Bridge] [PATCH][RFC] bridge-utils: add basic VEPA support
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
2007 Apr 18
1
[Bridge] Building 1.1 ?
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
2009 Aug 13
0
[Bridge] [PATCH] bridge-utils: Add 'hairpin' port forwarding mode
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
2009 Aug 13
0
[Bridge] [PATCH] bridge-utils: Add 'hairpin' port forwarding mode
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
2009 Aug 13
0
[Bridge] [PATCH] bridge-utils: Add 'hairpin' port forwarding mode
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
2002 Sep 17
1
Problems compiling patched bridge-utils
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:
2007 Apr 18
1
[Bridge] two fields are missing in brctl output when using /sys
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
2007 Apr 18
0
[Bridge] setting STP values via brctl
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
2005 Jan 06
0
skip unconnected interfaces
This patch makes it so that ipconfig only configures devices that are
connected:
--- klibc-0.194/ipconfig/main.c.orig 2005-01-06 15:20:24.749525888 -0700
+++ klibc-0.194/ipconfig/main.c 2005-01-06 15:24:48.038499880 -0700
@@ -27,6 +27,7 @@
static char do_not_config;
static unsigned int default_caps = CAP_DHCP | CAP_BOOTP | CAP_RARP;
static int loop_timeout = -1;
+static int only_connected = 0;
2013 Mar 05
0
[Bridge] [PATCH] bridge-utils: Fix compile against linux-3.8.x
Linux 3.8 has a header, include/uapi/linux/if_bridge.h that uses a
struct in6_addr but doesn't define it. The trivial seeming fix of
including the header that does define it causes more problems. The
problem was discussed on mailing lists in January 2013. The final
suggestion I found was here:
http://www.redhat.com/archives/libvir-list/2013-January/msg01253.html
This is intended to
2007 Nov 22
1
[Bridge] Conflict between net/if.h and linux/if.h
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
[PATCH node-image] Fix create-ovirt-iso-nodes to allow manual specification of network bridge to use
2009 Jul 05
2
[PATCH node-image] Fix create-ovirt-iso-nodes to allow manual specification of network bridge to use
Since create-ovirt-network script has been deprecated (was part of
ovirt-appliance repo) we can't default to bridge on the host of ovirtbr0 for
doing fake node testing. So default to network:default and allow manual override
to something like bridge:breth0
Signed-off-by: Perry Myers <pmyers at redhat.com>
---
create-ovirt-iso-nodes | 11 +++++++----
1 files changed, 7 insertions(+),
2007 Apr 18
1
[Bridge] bridge-utils compilation bug
Hi,
I tried to cross-compile bridge-utils, and think I have found a bug in
Makefile.in:
--- /cygdrive/d/sources/bridge-utils-1.1/libbridge/Makefile.in
2004-06-02 20:38:20.000000000 +0300
+++ libbridge/Makefile.in 2006-12-28 11:56:56.576468700 +0200
@@ -5,7 +5,8 @@
RANLIB=@RANLIB@
CC=@CC@
-CFLAGS = -Wall -g $(KERNEL_HEADERS)
+CFLAGS = -Wall @CFLAGS@
+INCLUDE=$(KERNEL_HEADERS)
2007 Apr 18
1
[Bridge] brctl insmod
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
2007 May 09
0
[patch 9/9] lguest: the documentation, example launcher
From: Rusty Russell <rusty@rustcorp.com.au>
A brief document describing how to use lguest. Because lguest doesn't have an
ABI we also include an example launcher in the Documentation directory.
[jmorris@namei.org: Fix up nat example in documentation]
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andi Kleen <ak@suse.de>
Signed-off-by: James Morris
2007 May 09
0
[patch 9/9] lguest: the documentation, example launcher
From: Rusty Russell <rusty@rustcorp.com.au>
A brief document describing how to use lguest. Because lguest doesn't have an
ABI we also include an example launcher in the Documentation directory.
[jmorris@namei.org: Fix up nat example in documentation]
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andi Kleen <ak@suse.de>
Signed-off-by: James Morris