From owner-freebsd-stable@FreeBSD.ORG Wed Jun 9 12:28:29 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93333106566C for ; Wed, 9 Jun 2010 12:28:29 +0000 (UTC) (envelope-from reko.turja@liukuma.net) Received: from www.liukuma.net (www.liukuma.net [62.220.235.15]) by mx1.freebsd.org (Postfix) with ESMTP id 4DD1D8FC1C for ; Wed, 9 Jun 2010 12:28:29 +0000 (UTC) Received: from rivendell (a91-155-174-194.elisa-laajakaista.fi [91.155.174.194]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) (Authenticated sender: ignatz@www.liukuma.net) by www.liukuma.net (Postfix) with ESMTPSA id A381D1CC63; Wed, 9 Jun 2010 15:37:49 +0300 (EEST) Message-ID: <4A84438AC2044DEF873A7341CF0CF2F0@rivendell> From: "Reko Turja" To: References: <4C0E81D7.8020209@earthlink.net> <20100608180506.GA9340@icarus.home.lan> <4C0E8B42.70603@earthlink.net> <20100608184429.GA12052@icarus.home.lan> <20100608184919.GY63749@cesium.hyperfine.info><4C0E935E.1020409@earthlink.net> <4C0F8214.3090104@earthlink.net> In-Reply-To: <4C0F8214.3090104@earthlink.net> Date: Wed, 9 Jun 2010 15:28:36 +0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8089.726 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726 Cc: FreeBSD Stable Subject: Re: FreeBSD eats 169.254.x.x addressed packets X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jun 2010 12:28:29 -0000 > One final comment - I still don't understand why FreeBSD "won't"=20 > respond to pings > when it has an address like 169.254.1.1. I can ssh to the unit but=20 > it won't > respond to pings. I tried setting up a linux box with an address=20 > like > 169.254.1.2 and it "would" respond to pings. Linux is not really any measuring stick in standard compliance... -Reko=20