Bug#772650: general: Debian could not use gateway in 169.254.0.0 ip range
Package: general
Severity: important
I have a NAT-ed network which uses 169.254.1.0/24 range (private/zeroconf
range). The network has dhcp and gateway (169.254.1.1). From some time
(probably few months) Debian Jessie is not able to use the gateway.
It is possible to ping the gateway and other computers in 169.254.1.0/24
network. The packets are not routed by the nat.
Tcpdump on the gateway does not see any incoming packets when I try to send
packets from Debian box outside 169.254.1.0 network.
The gateway works fine, there is >30 computers using this nat and dhcp
(Windows, Androids, Mac, Ubuntu, etc.).
Few days ago I have installed a fresh copy of Jessie on a laptop connected to
my 169.254.1.0 network. Debian installer (netinst) correctly downloads the
packages with use of this network. After firs reboot the system lose the
connectivity with the Internet.
I made a virtual machine to test the problem — it behaves exactly the same
(could connect internet witch other ip ranges could not connect internet when
connected to 169.254.1.0/24).
The re is no avahi and any avahi-configured routes to 169.254.x.x. There is
only the route configured by dhcp.
I don't know where is the problem. I know that 169.254.x.x range is assigned to
zeroconf and avahi like stuff. Still it should be possible to configure/use the
gateway in any ip range you want. It would be very difficult to change the
addressing here.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.17.4MK (SMP w/4 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Reply to: