From owner-freebsd-security@FreeBSD.ORG  Wed Sep 24 10:12:26 2003
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3A4C516A4B3
	for <security@freebsd.org>; Wed, 24 Sep 2003 10:12:26 -0700 (PDT)
Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua
	[212.110.138.65])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 30E3C43FB1
	for <security@freebsd.org>; Wed, 24 Sep 2003 10:12:17 -0700 (PDT)
	(envelope-from ru@sunbay.com)
Received: from whale.sunbay.crimea.ua (ru@localhost [127.0.0.1])
	h8OHC8rX032213
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 24 Sep 2003 20:12:08 +0300 (EEST)	(envelope-from ru@sunbay.com)
Received: (from ru@localhost)
	by whale.sunbay.crimea.ua (8.12.9/8.12.8/Submit) id h8OHC8AG032212;
	Wed, 24 Sep 2003 20:12:08 +0300 (EEST)
	(envelope-from ru)
Date: Wed, 24 Sep 2003 20:12:08 +0300
From: Ruslan Ermilov <ru@freebsd.org>
To: Michael Sierchio <kudzu@tenebras.com>
Message-ID: <20030924171208.GA31618@sunbay.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>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="WIyZ46R2i8wDzkSu"
Content-Disposition: inline
In-Reply-To: <3F71D007.3040406@tenebras.com>
User-Agent: Mutt/1.5.4i
cc: security@freebsd.org
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-03:14.arp
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Security issues [members-only posting]
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Sep 2003 17:12:26 -0000


--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--