From owner-freebsd-hackers Wed Jul 14 8:28:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.webnology.com (mercury.webnology.com [209.155.51.2]) by hub.freebsd.org (Postfix) with ESMTP id 7D65314CBA for ; Wed, 14 Jul 1999 08:28:06 -0700 (PDT) (envelope-from jooji@webnology.com) Received: from localhost (jooji@localhost) by mercury.webnology.com (8.9.2/8.9.2) with SMTP id JAA20222 for ; Wed, 14 Jul 1999 09:29:10 -0500 (CDT) Date: Wed, 14 Jul 1999 09:29:10 -0500 (CDT) From: "Jasper O'Malley" To: freebsd-hackers@freebsd.org Subject: Final (maybe) ARP breakage plea Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I realize it's not real high on the list of things to fix, but proxy ARP is still broken in -STABLE. If anyone know the answers to any of these questions, please drop me a line so I can try fixing it: 1) Can anyone explain the difference between "published" ARP table entries, and "published (proxy only)" ARP table entries? 2) What purpose does the sin_other parameter of the sockaddr_inarp structure serve (defined in /usr/include/netinet/if_ether.h, and set to SIN_PROXY for "proxy only" ARP entries)? 3) How about the significance of the RTF_HOST routing message flag (i.e. how does an IP "host" route functionally differ from a "net" route with a /32 netmask)? Or does this only have significance for non-IP routes? 4) What's the purpose of this snippet of code from rtmsg() in src/usr.sbin/arp/arp.c? if (doing_proxy) { if (export_only) sin_m.sin_other = SIN_PROXY; else { rtm->rtm_addrs |= RTA_NETMASK; rtm->rtm_flags &= ~RTF_HOST; } } Cheers, Mick The Reverend Jasper P. O'Malley dotdot:jooji@webnology.com Systems Administrator ringring:asktheadmiral Webnology, LLC woowoo:http://www.webnology.com/~jooji To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message