From owner-freebsd-net@FreeBSD.ORG  Tue Mar  2 06:48:43 2004
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6B2B616A4CE; Tue,  2 Mar 2004 06:48:43 -0800 (PST)
Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 3E12E43D1F; Tue,  2 Mar 2004 06:48:41 -0800 (PST)
	(envelope-from smithi@nimnet.asn.au)
Received: from localhost (smithi@localhost)
	by gaia.nimnet.asn.au (8.8.8/8.8.8R1.3) with SMTP id BAA01631;
	Wed, 3 Mar 2004 01:48:36 +1100 (EST)
	(envelope-from smithi@nimnet.asn.au)
Date: Wed, 3 Mar 2004 01:48:35 +1100 (EST)
From: Ian Smith <smithi@nimnet.asn.au>
To: Andre Oppermann <andre@freebsd.org>
In-Reply-To: <4044928C.AF49FD38@freebsd.org>
Message-ID: <Pine.BSF.3.96.1040303012627.26013L-100000@gaia.nimnet.asn.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-net@freebsd.org
Subject: Re: My planned work on networking stack
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Mar 2004 14:48:43 -0000

[-current out of ccs, I'm not subscribed]

On Tue, 2 Mar 2004, Andre Oppermann wrote to Wes Peters:

 > > Wowsers.  I can't wait to hear more.  When do you expect to have a design
 > > for the ARP stuff and TCP buffer sizing, since they are underway?
 > 
 > The ARP stuff is pretty simple and is a hash list IP->MAC per ethernet
 > (actually 802.1) broadcast domain.  The harder part is to move all the
 > code to one place from it's various net/* and netinet/* files.  As a
 > nice side effect we get per-MAC accounting (octets, frames) for free.

What about bridged interfaces that have a MAC, but no IP address?  I'm
still trying to figure this one out for a (4.8-R) bridge that's working
fine but still has some issues with ARP confusion and thus repeated ARP
requests from the upstream / outside router, esp regarding broadcast UDP
traffic, where the inside interface has the one IP and thus broadcast
address, for broadcast packets delivered locally to the bridge's IP? 

I realise this is a bridge issue, but it's how it interacts with ARP.

The rest of this is well out of my league, but fascinating reading :)

Cheers, Ian