Date: Wed, 21 May 2003 21:01:16 -0400 From: Chuck Swiger <cswiger@mac.com> To: freebsd-net@freebsd.org Subject: Re: Bridge + arp messages... Message-ID: <3ECC215C.7040309@mac.com> In-Reply-To: <20030521110342.D50883@news1.macomnet.ru> References: <1159.192.168.1.194.1053360712.squirrel@intranet.el.com.br> <1254.192.168.1.194.1053435227.squirrel@intranet.el.com.br> <3ECA74B8.8010108@mac.com> <20030521110342.D50883@news1.macomnet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Maxim Konovalov wrote: [ ... ] > It doesn't but it does support a simple loop detection algorithm: > > sys/net/bridge.c, line #707 Which is the code that produces the warning messages Gilson de Paiva saw, of course. I'm quite willing to believe that FreeBSD's loop detection works great for the situation where bridged interfaces are put on the same subnet. -- -Chuck #if defined(SENSE_OF_HUMOR) Spanning tree protocol, link aggregation (or "port trunking", etc), and other layer-2 stuff found in managed switches still have their uses. For some odd reason, a Tom Lehrer song about Werner von Braun is coming to mind-- "FreeBSD forwards the packets, who cares whether they loop around." :-) #endif
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3ECC215C.7040309>