From owner-freebsd-current Mon Jul 8 10:49:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA25180 for current-outgoing; Mon, 8 Jul 1996 10:49:41 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA25175 for ; Mon, 8 Jul 1996 10:49:39 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA00653; Mon, 8 Jul 1996 13:49:34 -0400 Date: Mon, 8 Jul 1996 13:49:34 -0400 From: Garrett Wollman Message-Id: <9607081749.AA00653@halloran-eldar.lcs.mit.edu> To: Nate Williams Cc: Garrett Wollman , FREEBSD-CURRENT-L Subject: Re: "ifconfig -arp" doesn't work? In-Reply-To: <199607081706.LAA13585@rocky.mt.sri.com> References: <199607080551.IAA05292@office.elvisti.kiev.ua> <9607081633.AA02857@halloran-eldar.lcs.mit.edu> <199607081706.LAA13585@rocky.mt.sri.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: >> if (ac->ac_if.if_flags & IFF_NOARP) { >> m_freem(m); >> return; >> } > Should this code be committed to -current? Well, that's problematic. There are a number of different meanings one could attribute to IFF_NOARP: 1) Ignore incoming ARP requests. 2) Do not send ARP requests. 3) Do not do any ARP processing at all. The fragment above only attempts to implement (1), and I have no idea whether it actually works or not. I don't know what other systems do. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant