[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#772650: general: Debian could not use gateway in 169.254.0.0 ip range



On Wed, 10 Dec 2014, Maciej Kotliński wrote:
> Finally I found the easiest and trivial resolution of the problem.  You
> just can set scope 0 with ip command.
> 
> The interface with address 169.254.x.x gets scope link (253), so the
> packets won't be send outside NAT.  Configuring interface with ip a a
> 169.254.x.x dev ethX scope 0 After that the packages are sent as before.
> 
> I'm sure that after release of Jessie as stable some other people will
> have such problem.  Could somebody add my comment to the closed bug
> report? It could help somebody with the networki simillar to mine.

Done.

However, here are the warnings for other users that also have the same
"problem" ("broken as designed" network addressing using link-local scope
to reach through routers/gateways).

1. This is not a proper fix, it is a gross hack that breaks things
   further, useful only to perpetuate broken network designs.

2. Changing the scope of 169.254.0.0/16 has security implications,
   none of them good.

3. The end result is utterly unsupported by Debian and by the IP
   networking standards.  In fact, it is an *explicitly forbidden*
   configuration.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


Reply to: