Date: Wed, 9 Jun 2010 15:28:36 +0300 From: "Reko Turja" <reko.turja@liukuma.net> To: <sclark46@earthlink.net> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: FreeBSD eats 169.254.x.x addressed packets Message-ID: <4A84438AC2044DEF873A7341CF0CF2F0@rivendell> In-Reply-To: <4C0F8214.3090104@earthlink.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A84438AC2044DEF873A7341CF0CF2F0>