em driver + VLAN's
I'm having an interesting problem at the moment. I want to bridge
between two cisco switches on trunk ports. Basically bridging vlans - if I
bridge my two main interfaces it works fine if they are fxp, but not when I
use em cards...
Could this be related to the driver, or BSD in some way?
freebsd-net@xxxxxxxxxxx mailing list
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- Re: em driver + VLANs
... D> bridge my two main interfaces it works fine if they are fxp, ... GLEBIUS-RIPN GLEB-RIPE ...
- Re: distributed bridging [script]
... >> I'm trying to create a configuration that would bridge interfaces on ... Each host would have at least two interfaces, ... here's a completely untested script. ...
- Re: bridge with access on both interfaces
... >>'inside' and 'outside' IPs separately on each bridge interface, ... Some tcpdumps on both in and outside interfaces suggest an ARP ... > If you want to use IP while bridging, ... and net4801 is that the 3 ethernet controllers now share one interrupt. ...
- Re: Bridge, dpcpd, sshd
... I have a server machine that I use as DHCP server, ... interfaces on it, I would like to use two of those for the ... I set up a bridge interface as per the FreeBSD ... If I manually start dhcpd with the same parameters ...
- [BUG][debian-2.6.20-1-686] bridging + vlans + "vconfig rem" == stuck kernel
... I've managed to fairly reliably trigger a deadlock in some portion of the linux networking code on my Debian test box. ... I'm pretty sure that it's a race condition of some sort as it doesn't trigger if I ifdown the interfaces one by one, but if I run "ifdown -a" then it triggers halfway through reliably. ... Just for a bit of background on why this is so complex: When I get this networking problem sorted out I'm going to set up heartbeat and a dummy "world1" interface with a shared MAC which is added to the "world" bridge when the current system is the DHCP-client master. ...