Re: [gentoo-user] Why my wierd ifconfig setup won't work in iproute2... ever.

[Mick]

On Sunday 01 Mar 2015 03:22:03 Walter Dnes wrote:
> On Thu, Feb 26, 2015 at 11:27:56PM -0500, Walter Dnes wrote
>
> > But if I include the line...
> >
> > modules="!iproute2"
> >
> > ...it works perfectly.  What's frustrating is that it works under
> > ifconfig, but not under iproute2.  I'll check with the local linux
> > user group in town (mailing list) to see if I can get any hints.
>
>   I now have the answer.  It's not what I wanted to hear, but at least I
> can stop pounding my head against a brick wall.  I found out from the
> networking gurus on the local Linux mailing list that...
>
> * ifconfig is ancient (goes back to before 2005)
>
> * back then 169.254.0.0/16 was just another address block, and ifconfig
>   happily treats it as such
>
> * in May 2005, RFC3927 was done http://www.ietf.org/rfc/rfc3927.txt
>   It defined IPV4 link-local networking in 169.254.0.0/16
>
> * it says, amongst other things...
>
> > This document does not recommend that IPv4 Link-Local addresses and
> > routable addresses be configured simultaneously on the same interface.
>
> * iproute2 is relatively new, and follows that recommendation.  It's
>   probably hard-coded not to support link-local and non-link-local
>   addresses simultaneously on the same NIC.
>
> * My only option in an iproute2-only environment would be to get a 2nd
>   NIC and attach the TV tuner to it.
>
> * My HDHomerun tuner is almost a museum-piece (spring of 2010).  I
>   figure that by the time ifconfig support is finally deprecated, I'll
>   be looking for a new tuner, rather than buying another NIC.
>
>   So I'll keep going with 'modules="!iproute2"' until ifconfig is
> deprecated.

Out of interest, you didn't say if you tried adding manually a route in your 
/etc/conf.d/net for the link-local address space to see if it works:

routes_eth0="
default via 192.168.123.254
169.254.0.0/16 via 169.254.1.1"  <==Add this route for 169.254.0.0/16==

-- 
Regards,
Mick