Date: Wed, 24 Sep 2003 20:12:08 +0300 From: Ruslan Ermilov <ru@freebsd.org> To: Michael Sierchio <kudzu@tenebras.com> Cc: security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-03:14.arp Message-ID: <20030924171208.GA31618@sunbay.com> In-Reply-To: <3F71D007.3040406@tenebras.com> References: <200309241429.h8OETrhk097904@freefall.freebsd.org> <3F71ADCA.7090408@tenebras.com> <20030924162111.GA23542@sunbay.com> <3F71C733.6070708@tenebras.com> <20030924170442.GC23542@sunbay.com> <3F71D007.3040406@tenebras.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 24, 2003 at 10:10:31AM -0700, Michael Sierchio wrote: > Ruslan Ermilov wrote: >=20 > >Right. But static ARP means something different. It means > >that the APR table is frozen, but system will still reply > >to ARP requests for its addresses, which is not done if > >IFF_NOARP flag is set on an interface. >=20 > Okay, I may have been misusing the term. I meant *permanent* and > *manual* entries in the ARP table, via the arp command, and > disabling ARP on the interface. >=20 > That seems to work. What does your lexicon say for "static arp?" >=20 Read what I have said -- static ARP means that ARP is functional, but no updates are allowed based on information from the network. Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software Ltd, ru@FreeBSD.org FreeBSD committer --WIyZ46R2i8wDzkSu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE/cdBoUkv4P6juNwoRAk9fAJ9zf2GhmpfDsWPYCeLsGAYdseri/ACfVFHq OiBuBnF6dBLA4J4pBR7XtW0= =b5iE -----END PGP SIGNATURE----- --WIyZ46R2i8wDzkSu--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030924171208.GA31618>