[LBo] Link-local.

Lonnie Mullenix buckshot at scicable.com
Fri Feb 2 16:02:02 CET 2007


On Fri, 2007-02-02 at 14:13 +0000, Geoff Jones wrote:
> I have a small home network using a wired/wireless router as dhcp server.
> On my deb etch machine, I recently noticed I have 2 ip  addresses -
> 192.168.x.x and 169.254.x.x .
> A search revealed the second as a "link-local". I read that link-local was to 
> allow networking where there is no dhcp server? This machine is wired to the 
> router and seems to use the 169 address to link to the other wired machine 
> and use 192 for wireless connections ( I think ) - despite having a dhcp 
> assigned address?
> I wondered if some-one could explain the reasons / configuration / advantages 
> or disadvantages of this behaviour?
> Thanks,
> 
> Geoff.
> 
> p.s. I too decided to drop Iceweasel + use firefox direct from Mozilla in 
> order to get immediate security updates - first I'd seen of the Deb v. 
> Mozilla debate - seems a pity to have a fork in such a successful piece 
> of "free" software!

>From my experience, I would assume that the system is using the
192.X.x.X address for the network.  I have Never gotten  any sort of
connection with the 169.x.x.x IP addresses.  As Billy mentioned, with a
windows system you would be getting the 'limited or no connectivity'
with the 169.x.x.x address and in six plus years of running various
Linux distros, I do not recall ever running into the 169.x.x.x address
scheme.

So, that leads to a couple of questions.  Does that Debian box have
wireless capabilities?  Does the Debian box have two or more NIC cards
installed?  (Now I remember seeing the 169.x.x.x IP on a Linux box, the
un-configured NIC on a router box.)

Maybe that will answer a question, and maybe it will just lead to more.

Later.

Lonnie

-- 
Running Gentoo and
Debian, enjoying the
MS free life on the
internet.



More information about the QnA mailing list