similar to: [Bridge] patch for a message bug

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

Hi! We have received at Debian a couple of bugs and typos that apply to the bridge-utils code and I'd like to share them with the community so that they can be fixed for everybody, most of the bugreports have patches or show the typos made on doc. Here they are: http://bugs.debian.org/296881 http://bugs.debian.org/348617 http://bugs.debian.org/376914 Last one seems quite important, I'm

Hi! Since the change to 2.4.22 I've been experimenting problems here, after many tests I have seen what I think is the problem that is causing this. The problem I'm seing is the loopback starts loosing packages, I don't know if this could also happen on other interfaces. I'm testing this by starting a: tcpdump -n -i lo port then a: nc -n -l port >/dev/null and a: nc

Hi! I was doing some tests with a samba 3.0.2a server set up to be a wins server and to do dns proxy, and I have found that when you queried nmbd for a name ahta was not on wins db or found on DNS, the negative response is cached either for a really long time or forever, in such a way that even though you add the name to the DNS, you won't get a positive answer out of nmbd anymore. I have

Hi! As noted by Chris Rankin on a mail to netfilter-devel and to the linux-kernel mailing list (subject: 2.6.12: connection tracking broken?), there is a problem with the connection tracking of iptables when one of the interfaces is a bridge. On my tests here I have setup a connection between two machines using a real interface (eth0) and then the same setup using a bridge interface (br0) to

Folks, For what it's worth I used to have the hang at shutdown with brnf and kernel 2.4.26. An fsck on the boot drive fixed it (telling me it had nothing to do with whatever kernel I was running)...have you tried that? James -----Original Message----- From: Santiago Garcia Mantinan [mailto:bridge@manty.net] Sent: Saturday, February 05, 2005 5:51 AM To: Mirko Parthey Cc:

Hi! I'm the current maintainer of swfdec on Debian, as such I have written the man pages for swfdec-gnome and swfdec-player based on the doc that comes with them. I just wanted to let you know that I'm the new maintainer and that these man pages are available as part of the Debian package, and are of course free so you could add them to the upstream package and make the changes you want.

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

The current diagnostic is terrible. This one tells the user how to diagnose and fix the problem. --- src/launch-libvirt.c | 47 +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 47 insertions(+) diff --git a/src/launch-libvirt.c b/src/launch-libvirt.c index 1c0bfac..d4c4c47 100644 --- a/src/launch-libvirt.c +++ b/src/launch-libvirt.c @@ -181,6 +181,7 @@ static int is_blk (const

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

We've been carrying this exact patch in RHEL 7 for several years. It reverts the change made in 2014 where we switched to using the virbr0 bridge for libguestfs networking instead of SLIRP. We thought SLIRP was going to become unsupported in qemu, but recently there have been more encouraging signs since it looks like SLIRP will be spun off as a separate project, running as a modular process

Hi all, Windows Vista Home Premium VC++ 9 According to MSDN, the if_indextoname() function should be included on Vista: http://msdn.microsoft.com/en-us/library/bb408408%28VS.85%29.aspx However, I can''t get mkmf to see it. I tried all of these: require ''mkmf'' if have_header(''netioapi.h'') # yes have_func(''if_indextoname'',

Hello! "brctl stp br0" would crash brctl provided that br0 is a bridge. This is caused by incorrect number of arguments in the commands table. "stp" needs at least 2 arguments after "stp". The patch against version 1.0.4 is attached. -- Regards, Pavel Roskin -------------- next part -------------- --- brctl/brctl_cmd.c +++ brctl/brctl_cmd.c @@ -394,7 +394,7 @@

- 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

Hi, since a few days all the dependencies for compiling and running swfdec 0.5.90 and newer are met in debian experimental. So after adding the experimental repository in /etc/apt/sources.list and doing apt-get -t experimental install libsoup2.4-dev libglib2.0-dev you can continue to test latest and greatest swfdec. cheers, Riccardo