| 1 |
On Sun, 28 Oct 2007 12:19:13 +0000 |
| 2 |
Mick <michaelkintzios@×××××.com> wrote: |
| 3 |
|
| 4 |
> On Saturday 27 October 2007, Dan Farrell wrote: |
| 5 |
> > On Sat, 27 Oct 2007 21:58:11 +0930 |
| 6 |
> > |
| 7 |
> > Iain Buchanan <iaindb@××××××××××××.au> wrote: |
| 8 |
> > > is it by any chance assigning you a 169... address? Did you |
| 9 |
> > > recently upgrade dhcpcd to ... around ... 3.1.6 I think? Anyway, |
| 10 |
> > > it now tries "zeroconf" or whatever it's called, to give you an |
| 11 |
> > > address when there's no server around. Personally I don't like |
| 12 |
> > > it, but you can decide :) |
| 13 |
> > |
| 14 |
> > This behaviour is called APIPA (Automatic PRivate IP Addressing) |
| 15 |
> > (from /etc/conf.d/net.example): |
| 16 |
> > # APIPA is a module that tries to find a free address in the range |
| 17 |
> > # Automatic Private IP Addressing (APIPA) |
| 18 |
> > # use APIPA to find a free address in the range |
| 19 |
> > # 169.254.0.0-169.254.255.255 |
| 20 |
> > |
| 21 |
> > It provides DHCP-like functionality without a DHCP server. Pretty |
| 22 |
> > useless, unless you use it to configure all your IPs or a route for |
| 23 |
> > that subnet. |
| 24 |
> |
| 25 |
> Even worse, if your DHCP server comes up later, your PC will still |
| 26 |
> hold on to APIPA - not sure how this feature can be of any use to be |
| 27 |
> honest, but most devices these days from MS Windows to PDAs tend to |
| 28 |
> behave like this. |
| 29 |
|
| 30 |
I was also wondering what kind of useful purpose this would serve. I |
| 31 |
am guessing that it would be enough for a network on one broadcast |
| 32 |
domain, if there is no need for any routing information. |
| 33 |
-- |
| 34 |
gentoo-user@g.o mailing list |
Archives