Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 5 Feb 2001 00:54:53 -0800
From:      Alfred Perlstein <bright@wintelcom.net>
To:        Masachika ISHIZUKA <ishizuka@ish.org>
Cc:        freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject:   Re: BRIDGE breaks ARP?
Message-ID:  <20010205005453.L26076@fw.wintelcom.net>
In-Reply-To: <20010205170801Q.ishizuka@onion.ish.org>; from ishizuka@ish.org on Mon, Feb 05, 2001 at 05:08:01PM %2B0900
References:  <20010205043816.18207.richw@wyattearp.stanford.edu> <200102050629.f156Tel18525@iguana.aciri.org> <20010205170801Q.ishizuka@onion.ish.org>

next in thread | previous in thread | raw e-mail | index | archive | help
* Masachika ISHIZUKA <ishizuka@ish.org> [010205 00:09] wrote:
> > May i suggest to try a recent (feb.2, 2001) version of the code ?
> > there have been long-standing problems with bridging on 4.x and
> > in particular some related to the handling of broadcast packets (ARP
> > requests are among them) which hopefully are fixed now.
> > You need to default your firewall to open.
> 
>   I cvsuped three hours ago and the same ARP troubles happened.
> The RCS header of /sys/net/bridge.c is
> "$FreeBSD: src/sys/net/bridge.c,v 1.16.2.12 2001/02/01 20:25:08 luigi Exp $".
> 
>   I use two fxp (Intel Pro100B) NICs.  This machine was worked
> fine with about two weeks older codes.

I had a problem recently (it wound up being a bad network cable),
but while going through the code I noticed that one of the routines
was changed to return 0x40000, which may somehow conflict with
'normal' return values.  In any case the 0x40000 should be a
#define.

-- 
-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org]
"I have the heart of a child; I keep it in a jar on my desk."


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010205005453.L26076>