dhcpd: route to 169.254.0.0/16??
in [Slackware]
|
Prev: What's the state of bluetooth?
Next: booting from dvd
From: LostInTheLoop on 20 Mar 2010 07:16 Hi all, I've got dhcpd running on a local machine. In all other workstations, which get their IP correctly in a 192.168.1.0/24 subnet, I find this entries in /var/log/messages, at each lease renewal: Mar 20 08:54:49 workstation6 dhcpcd[2499]: eth0: renewing lease of 192.168.1.6 Mar 20 08:54:49 workstation6 dhcpcd[2499]: eth0: leased 192.168.1.6 for 43200 seconds Mar 20 08:54:50 workstation6 dhcpcd[2499]: eth0: removing route to 169.254.0.0/16 metric 0 Mar 20 08:54:50 workstation6 dhcpcd[2499]: eth0: adding IP address 192.168.1.6/24 Mar 20 08:54:50 workstation6 dhcpcd[2499]: eth0: adding default route via 192.168.1.1 metric 0 Mar 20 08:54:50 workstation6 dhcpcd[2499]: eth0: adding route to 169.254.0.0/16 metric 0 Why does dhcpcd keep removing and reassigning this 169.254* route? It's a subnet who gets assigned at boot to any machine when there's no dhcp server. I can't understand why it keeps popping up when a dhcp-assigned IP is in place and working well. Am I doing something wrong? TIA
From: Grant on 20 Mar 2010 11:06 On Sat, 20 Mar 2010 12:16:19 +0100, LostInTheLoop <bumping(a)ro.und> wrote: >Hi all, > >I've got dhcpd running on a local machine. In all other >workstations, which get their IP correctly in a 192.168.1.0/24 >subnet, I find this entries in /var/log/messages, at each lease renewal: > >Mar 20 08:54:49 workstation6 dhcpcd[2499]: eth0: renewing lease of >192.168.1.6 >Mar 20 08:54:49 workstation6 dhcpcd[2499]: eth0: leased 192.168.1.6 >for 43200 seconds >Mar 20 08:54:50 workstation6 dhcpcd[2499]: eth0: removing route to >169.254.0.0/16 metric 0 >Mar 20 08:54:50 workstation6 dhcpcd[2499]: eth0: adding IP address >192.168.1.6/24 >Mar 20 08:54:50 workstation6 dhcpcd[2499]: eth0: adding default >route via 192.168.1.1 metric 0 >Mar 20 08:54:50 workstation6 dhcpcd[2499]: eth0: adding route to >169.254.0.0/16 metric 0 > >Why does dhcpcd keep removing and reassigning this 169.254* route? >It's a subnet who gets assigned at boot to any machine when there's >no dhcp server. I can't understand why it keeps popping up when a >dhcp-assigned IP is in place and working well. > >Am I doing something wrong? Dunno. What machine and daemon is providing the DHCP service? Is there a windows domain controller on localnet (MSFT or samba)? Configuration file? Do all clients do this, or just one, I'm unclear what you mean above. What firewall rules in place for '--sport 68 --dport 67'? Grant.
From: LostInTheLoop on 20 Mar 2010 14:38 Grant, on 03/20/2010 04:06 PM, wrote: > What machine and daemon is providing the DHCP service? dhcpd on 192.168.1.2 running slackware 13, slackware 13 also in every other client. > > Is there a windows domain controller on localnet (MSFT or samba)? > Microsoft free floor! :-) > Configuration file? Do all clients do this, or just one, I'm > unclear what you mean above. All of them. Apparently each local dhclient wants to have its say at each lease confirmation. Configuration file on dhcp server 192.168.1.2: #======== /etc/dhcpd.conf ===================== option domain-name "spectrecentral"; option domain-name-servers 192.168.1.2; default-lease-time 43200; max-lease-time 57600; ddns-update-style interim; authoritative; log-facility authpriv; # Original comment: # No service will be given on this subnet, but declaring it helps # the DHCP server to understand the network topology. subnet 10.152.187.0 netmask 255.255.255.0 { } subnet 192.168.1.0 netmask 255.255.255.0 { range 192.168.1.11 192.168.1.254; option routers 192.168.1.1; } # A few assigned IPs... host workstation10 { hardware ethernet xx:xx:xx:xx:xx:xx; fixed-address 192.168.1.10; server-name workstation10; } > > What firewall rules in place for '--sport 68 --dport 67'? No firewall at all inside the local network served by 192.168.1.2 Thanks
From: Steve Masta on 20 Mar 2010 18:35 LostInTheLoop wrote: > Grant, on 03/20/2010 04:06 PM, wrote: > >> What machine and daemon is providing the DHCP service? > > dhcpd on 192.168.1.2 running slackware 13, slackware 13 also in > every other client. > >> >> Is there a windows domain controller on localnet (MSFT or samba)? >> > Microsoft free floor! :-) > >> Configuration file? Do all clients do this, or just one, I'm >> unclear what you mean above. > > All of them. Apparently each local dhclient wants to have its say at > each lease confirmation. <snip> I'm no expert, but it sounds like a client configuration problem to me. From the dhcpcd man page: ------ Local Link configuration If dhcpcd failed to obtain a lease, it will probe for a valid IPv4LL address (aka Zeroconf, aka APIPA). Once obtained it will probe every 10 seconds for a DHCP server to get a proper address. Even when dhcpcd obtains a proper lease, it will still add a Local Link route (165.254.0.0/16) so that the host can communicate with clients using these addresses. When using IPv4LL, dhcpcd will always succeed and return a 0 exit code. To disable this behaviour, you can use the -L, --noipv4ll option. ------ Steve
From: LostInTheLoop on 21 Mar 2010 12:15
Steve Masta, on 03/20/2010 11:35 PM, wrote: > When using IPv4LL, dhcpcd will always succeed and return a 0 exit > code. To disable this behaviour, you can use the -L, --noipv4ll option. Good point. I've tried adding noipv4ll; or option noipv4ll; in my client's /etc/dhclient.conf, but nothing changed, even rebooting. |