Hallo RPI-Fans,
ich habe einen RPI2 und folgendes Problem:
Trotz in der /etc/network/interfaces eingetragenen statischen IPv4 (DHCP dort logischerweise aus) holt sich mein RPI2 _zusätzlich_ noch eine 2. IPv4 per DHCP vom Router.
Komisch ist, er zeigt das mit ifconfig nicht an, ABER diese IP ist pingbar und lt arp-Abfrage auch dem RPI2 zugewiesen (gleiche MAC wie eth0).
Hat dieses Problem auch jemand oder ist das schon mal jemanden aufgefallen ??
Ich habe ja den avahi-daemon stark in Verdacht...
/etc/network/interfaces:
auto lo
iface lo inet loopback
auto eth0
allow-hotplug eth0
# iface eth0 inet manual
iface eth0 inet static
address 192.168.254.5
netmask 255.255.255.0
gateway 192.168.254.1
dns-nameservers 192.168.254.1
iface eth0 inet6 Auto
Auszug aus /var/log/daemon.log (DHCP IPv6 ist gewollt)
Jun 9 17:05:16 PI dhcpcd[2043]: DUID 00:01:00:01:1c:dd:60:5f:b8:27:eb:53:2d:df
Jun 9 17:05:16 PI dhcpcd[2043]: eth0: IAID eb:53:2d:df
Jun 9 17:05:16 PI dhcpcd[2043]: eth0: soliciting an IPv6 router
Jun 9 17:05:16 PI dhcpcd[2043]: eth0: Router Advertisement from fe80::a96:d7ff:fee3:32c8
Jun 9 17:05:16 PI dhcpcd[2043]: eth0: adding address 2001:4dd0:ff00:9218:a047:d2a2:57fc:34d2/64
Jun 9 17:05:16 PI dhcpcd[2043]: eth0: adding route to 2001:4dd0:ff00:9218::/64
Jun 9 17:05:16 PI dhcpcd[2043]: eth0: adding default route via fe80::a96:d7ff:fee3:32c8
Jun 9 17:05:16 PI dhcpcd[2043]: eth0: confirming prior DHCPv6 lease
Jun 9 17:05:16 PI ntpd[2255]: ntpd 4.2.6p5@1.2349-o Sun Apr 12 22:37:22 UTC 2015 (1)
Jun 9 17:05:16 PI ntpd[2305]: proto: precision = 0.833 usec
Jun 9 17:05:16 PI ntpd[2305]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Jun 9 17:05:16 PI ntpd[2305]: Listen and drop on 1 v6wildcard :: UDP 123
Jun 9 17:05:16 PI ntpd[2305]: Listen normally on 2 lo 127.0.0.1 UDP 123
Jun 9 17:05:16 PI ntpd[2305]: Listen normally on 3 eth0 192.168.254.5 UDP 123
Jun 9 17:05:16 PI ntpd[2305]: Listen normally on 4 lo ::1 UDP 123
Jun 9 17:05:16 PI ntpd[2305]: Listen normally on 5 eth0 fe80::ba27:ebff:fe53:2ddf UDP 123
Jun 9 17:05:16 PI ntpd[2305]: Listen normally on 6 eth0 2001:4dd0:ff00:9218:ba27:ebff:fe53:2ddf UDP 123
Jun 9 17:05:16 PI ntpd[2305]: peers refreshed
Jun 9 17:05:16 PI ntpd[2305]: Listening on routing socket on fd #23 for interface updates
Jun 9 17:05:17 PI dhcpcd[2043]: eth0: rebinding lease of 192.168.254.44 <-- WIESO ???!?
Jun 9 17:05:17 PI dhcpcd[2043]: eth0: REPLY6 received from fe80::a96:d7ff:fee3:32c8
Jun 9 17:05:17 PI dhcpcd[2043]: eth0: adding address 2001:4dd0:ff00:9218:13c4:baf8:7b48:b66a/128
Jun 9 17:05:17 PI dhcpcd[2043]: eth0: renew in 1800 seconds, rebind in 2880 seconds
Jun 9 17:05:17 PI avahi-daemon[2621]: Found user 'avahi' (UID 103) and group 'avahi' (GID 105).
Jun 9 17:05:17 PI avahi-daemon[2621]: Successfully dropped root privileges.
Jun 9 17:05:17 PI avahi-daemon[2621]: avahi-daemon 0.6.31 starting up.
Jun 9 17:05:17 PI avahi-daemon[2621]: Successfully called chroot().
Jun 9 17:05:17 PI avahi-daemon[2621]: Successfully dropped remaining capabilities.
Jun 9 17:05:17 PI avahi-daemon[2621]: Loading service file /services/udisks.service.
Jun 9 17:05:17 PI avahi-daemon[2621]: Joining mDNS multicast group on interface eth0.IPv6 with address 2001:4dd0:ff00:9218:ba27:ebff:fe53:2ddf.
Jun 9 17:05:17 PI avahi-daemon[2621]: New relevant interface eth0.IPv6 for mDNS.
Jun 9 17:05:17 PI avahi-daemon[2621]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.254.5.
Jun 9 17:05:17 PI avahi-daemon[2621]: New relevant interface eth0.IPv4 for mDNS.
Jun 9 17:05:17 PI avahi-daemon[2621]: Network interface enumeration completed.
Jun 9 17:05:17 PI avahi-daemon[2621]: Registering new address record for 2001:4dd0:ff00:9218:ba27:ebff:fe53:2ddf on eth0.*.
Jun 9 17:05:17 PI avahi-daemon[2621]: Registering new address record for 2001:4dd0:ff00:9218:a047:d2a2:57fc:34d2 on eth0.*.
Jun 9 17:05:17 PI avahi-daemon[2621]: Registering new address record for 2001:4dd0:ff00:9218:13c4:baf8:7b48:b66a on eth0.*.
Jun 9 17:05:17 PI avahi-daemon[2621]: Registering new address record for 192.168.254.5 on eth0.IPv4.
Jun 9 17:05:17 PI avahi-daemon[2621]: Registering HINFO record with values 'ARMV7L'/'LINUX'.
Fakt ist, der RPI2 ist unter der DHCP-Adresse auch ansprechbar (SSH) und pingbar.
Hat jemand eine Idee ??!?
Gruss Heiko