From owner-freebsd-hackers Mon Jan 8 08:19:01 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA18440 for hackers-outgoing; Mon, 8 Jan 1996 08:19:01 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA18431 for ; Mon, 8 Jan 1996 08:18:55 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id JAA10702; Mon, 8 Jan 1996 09:21:11 -0700 Date: Mon, 8 Jan 1996 09:21:11 -0700 From: Nate Williams Message-Id: <199601081621.JAA10702@rocky.sri.MT.net> To: phil@zipmail.co.uk Cc: hackers@freebsd.org Subject: Re: Losing arp entries... In-Reply-To: <199601081023.KAA21804@wbsmail.zipmail.co.uk> References: <199601081023.KAA21804@wbsmail.zipmail.co.uk> Sender: owner-hackers@freebsd.org Precedence: bulk > Having read the thread about the proxy arp problem with interest, I > now have a problem... Congratulations! > Now I seem to have a problem that arp stops publishing entries in 2.1.0R > (it loses the pub flag) or it creates another proxy entry with > {incomplete} which causes quite a number of problems. That's the 'arp' bug. > Is there a way to TOTALLY disable proxy arp (at least until the bug > is fixed !!!) so that this problem wont occur. I'm not sure what you mean. It's not a 'proxy' arp bug, but a generic arp bug. Any arp entry created by the routing protocol (and not by the underlying ethernet address resolution protocol) will give you problems. This means that regular 'arp' entries created by arp(8) will also give you the same problems as static proxy-arp entries. Nate