From owner-freebsd-questions Mon Nov 26 7:13:45 2001 Delivered-To: freebsd-questions@freebsd.org Received: from web.cs.ndsu.nodak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7]) by hub.freebsd.org (Postfix) with ESMTP id 71B0537B416 for ; Mon, 26 Nov 2001 07:13:43 -0800 (PST) Received: (from tinguely@localhost) by web.cs.ndsu.nodak.edu (8.11.4/8.11.4) id fAQFDfU18648; Mon, 26 Nov 2001 09:13:41 -0600 (CST) (envelope-from tinguely) Date: Mon, 26 Nov 2001 09:13:41 -0600 (CST) From: mark tinguely Message-Id: <200111261513.fAQFDfU18648@web.cs.ndsu.nodak.edu> To: joost@bps.jodocus.org, tedm@toybox.placo.com Subject: RE: IPFW/VLAN Cc: freebsd-questions@FreeBSD.ORG, puga@mauibuilt.com In-Reply-To: <000101c17649$90e06600$1401a8c0@tedm.placo.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > In reality, what they are actually doing here is tying ipfw specifically > to Ethernet when it comes to treatment of ARP packets. This > is philosophically wrong as a FreeBSD system could theoredically have > a broadcast-type interface on it in which ARP had meaning and Ethernet > typing didn't. (for example, if someone wrote an ARCnet driver for it, > which is highly unlikely) Actually, there are now a couple ARCnet drivers for FreeBSD. The existing ARP code in the network stack is ethernet length-centric, but there are patches to correct that. Possibly the ipfw code can adapt these changes also. --mark tinguely. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message