similar to: [Bridge] daemons are dropped

On Sun, 27 Jun 2004 15:43:30 +0700 <arkady-parabel@ngs.ru> wrote: > Hi. > > I'm using a powerpc-based board (CPU - Motorolla 82855, 50 > Mhz) with 32 Mb of RAM, Big Endian. > Linux kernel - 2.4.22, bridge - statically linked & as a > module > brctl - 0.9.6 > Ethernet - fec (arch/ppc/8xx_io/fec.c) > All this was compiled with gcc version 3.2.2 20030217

Hello, I'm having a problem getting two (working) NICs enslaved to a bridge to both work in the bridge. The setup is just for testing and looks like this: (NETWORK)-------|bridge|---------|test PC| I'm building a bridge from an old Dell Optiplex GX1 desktop. Using kernel-2.6.9-gentoo-r4, with bridging and ebtables compiled into the kernel; the two PCI NICs are Intel, and the e100

hi @all sometimes after a reboot the complete network is down the difference in the logs shows: in a failed reboot the eth0 does not entering promiscuous mode; in both cases the eth0 gets sucessful its ip configuration via dhcp - any idea ? the nic is a 3com 3c905C-TX/TX-M and the configuration is a suse 9.3 with xen-kernel 2.6.11.4-21.10-xen and xen 2.0.5.c ----------------[ failed reboot ]

Hello all, I'm trying to bridge the wlan0 and eth0 on an embedded system. I used the following commands to setup the bridge: ifconfig eth0 0.0.0.0 promiscuous ifconfig wlan0 0.0.0.0 promiscuous brctl addbr br0 brctl addif br0 eth0 brctl addif br0 wlan0 brctl sethello br0 1 brctl setmaxage br0 4 brctl setfd br0 4 ifconfig br0 up The eth0 is connected to a local network, and wlan0 is set to

Hello, I have been using the bridging facilities provided by Linux (vanilla 2.6.7 SMP with UML skas host patch applied) to bridge a regular physical ethernet network (on interface eth0) with a virtual network (on interface tap0, cf uml_switch, http://user-mode-linux.sourceforge.net/networking.html). A couple of virtual machines (run using user-mode linux, a tool that enables you to run linux

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

TL;DR: Is there a way to force a bridge to forward anything and everything on all ports (except the ingress port) *regardles* of any permanent FDB entries (such as the MAC addresses of interfaces acting as bridge ports)? For context, I'm using a network-namespace (container) based simulator (think GNS3 or CORE), which allow me to run multiple FRR instances in their own dedicated netns,

When the following commands are executed: brctl addbr br0 ifconfig br0 hw ether <addr> rmmod bridge The calltrace will occur: [ 563.312114] device eth1 left promiscuous mode [ 563.312188] br0: port 1(eth1) entered disabled state [ 563.468190] kmem_cache_destroy bridge_fdb_cache: Slab cache still has objects [ 563.468197] CPU: 6 PID: 6982 Comm: rmmod Tainted: G O

When the following commands are executed: brctl addbr br0 ifconfig br0 hw ether <addr> rmmod bridge The calltrace will occur: [ 563.312114] device eth1 left promiscuous mode [ 563.312188] br0: port 1(eth1) entered disabled state [ 563.468190] kmem_cache_destroy bridge_fdb_cache: Slab cache still has objects [ 563.468197] CPU: 6 PID: 6982 Comm: rmmod Tainted: G O

I am having trouble with recovery. Today due to electrical work I powered down my networks Router / DHCP server. My Centos 7 host machines lost their DHCP lease (they are actually static leases). Once I power my Router / DHCP server back up none of my virtual machine were accessible. It appears that when the DHCP lease was lost on the virt server the bridge of the KVM guest were all losts. A

Hi there :) I would like to submit a use case we are here: our company make network probes with 1 administravia interface and the rest in promiscuous mode to listen traffic. I've made virtualized server with Qemu. All Qemu instances (with 2 tap) listen on: br0 (admin int) br1 (receive traffic) The need is each tap on br1 must listen *all* traffic (unicast, multicast...). For this, I sets

Hi, I recently upgraded the kernel in my Debian server from 2.4.22 to 2.6.9. This server acts as router and has an ethernet bridge (br0) that combines eth1 and eth2. Each of these two network cards is connected to one Windows PC. Since I booted kernel 2.6.9 it takes more than one minute for a client pc to receive its IP address when that one starts up. I noticed that the kernel messages (shown

Dear Centos-Virt: Help! Guest=XP Pro, SP2 Host=CentOS5; # uname -r; 2.6.18-8.1.8.el5 VirtualBox-1.4.0_21864_rhel5-1.i586 http://www.virtualbox.org/download/1.5.0/VirtualBox-1.5.0_24069_rhel5-1.i586.rpm.run I have two nic: eth0 is the internal network; eth1 connects to a DSL modem. I also have a fully functioning DHCP server on eth0 (works perfectly with Parallels for Linux). The directions

Pavel, you may be interested in my work on Cisco HDLC bridging: http://marc.theaimsgroup.com/?l=linux-netdev&m=108802311131855&w=2 I have used it with the bridge driver (in 2.4) without any problems (yet ;)), and I am sure Krzysztof Halasa, the HDLC maintainer, would be thrilled if you managed to port it to a recent version of the kernel and make it a compile-time option. Oh, it also

Hello all, I'm using libvirt 0.8.3 on Debian Lenny (package provided in lenny-backports). After restarting libvirtd, I cannot start VM anymore. The daemon is restarted, but each time I try to start a domain, I get this message : virsh # start vm2 error: Failed to start domain vm2 error: internal error Process exited while reading console log output: When daemon is started with -v

Scratch that last comment. The kernel code I have now is identical to what I posted. Sorry for the misinformation. > -----Original Message----- > From: bridge-bounces@lists.osdl.org > [mailto:bridge-bounces@lists.osdl.org] On Behalf Of Eble, Dan > Sent: Tuesday, June 29, 2004 12:57 PM > To: 'arkady-parabel@ngs.ru' > Cc: bridge@osdl.org > Subject: RE: [Bridge] Re:

Hi, I've set up a bridge using the 2.6.11.6 kernel. The machine is running Debian testing with three NICs in it. eth0 is a standard 100Mb Intel NIC, eth1 and eth2 are both Intel gigabit cards using the e1000 driver. I tested everything at 100Mb and it worked fine. I moved the machine into production, eth1 plugging into a dumb 100Mb D-link switch, eth2 plugging into a shiney new Cisco

Hi, I''ve bit the bullet and gone with Xen, but I get some odd networking. Basically, this was the original idea. eth0 external eth1 internal create bridge br0 for eth0 create bridge br1 for eth1 Strip IP addresses for eth0 and eth1 and assign to br0 and br1 respectively. Worked great in a non-xen kernel under Fedora 8 in KVM/Qemu. Booting into Xen, my eth1 becomes eth2, I also get

Could the problem be that the e100 can do IP receive checksumming on the board, but the eepro driver doesn't enable it. When the board is doing checksum offload, then the csum field isn't set. Please try disabling receive checksumming on the e100 driver modprobe e100 XsumRX=0 If this is the problem, it exists both 2.4 and 2.6. On Wed, 27 Aug 2003 18:24:57 +0200 Hannes Schulz

Hi, I'm not sure but I think I suffer under the same problem with a bit different setup with squeeze testing and xen 4.0rc5. In fact I'm using bridges in the dom0 and the connections to the domU get lost sporadically. In don't see where's a solution to the problem... Is it now a bug? When it's an iptables bug, where's the corresponding bug in the iptables bugtracker