Date: Wed, 09 Jun 2010 18:18:30 +0200 (CEST) From: sthaug@nethelp.no To: reko.turja@liukuma.net Cc: sclark46@earthlink.net, freebsd-stable@freebsd.org Subject: Re: FreeBSD eats 169.254.x.x addressed packets Message-ID: <20100609.181830.74726190.sthaug@nethelp.no> In-Reply-To: <4A84438AC2044DEF873A7341CF0CF2F0@rivendell> References: <4C0E935E.1020409@earthlink.net> <4C0F8214.3090104@earthlink.net> <4A84438AC2044DEF873A7341CF0CF2F0@rivendell>
next in thread | previous in thread | raw e-mail | index | archive | help
> > One final comment - I still don't understand why FreeBSD "won't" > > respond to pings > > when it has an address like 169.254.1.1. I can ssh to the unit but > > it won't > > respond to pings. I tried setting up a linux box with an address > > like > > 169.254.1.2 and it "would" respond to pings. > > Linux is not really any measuring stick in standard compliance... If 169.254.0.0/16 addresses are supposed to be link local then I'd definitely expect a reply to a ping from another box on the same LAN, sourced from another 169.254.0.0/16 address. Steinar Haug, Nethelp consulting, sthaug@nethelp.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100609.181830.74726190.sthaug>