ob2s
Posts: 3
Joined: Thu Mar 12, 2020 4:11 pm

Pi taking many IPs from Router DCHP pool

Thu Mar 12, 2020 4:22 pm

My pi has a static ip address on wlan0 and is not connected to ethernet, this address is persistent and comes up each time thanks to dhcpdc.conf. This static ip is not part of the router's dhcp pool, but every time the pi boots it requests a new ip address from the router with a new mac address. I don't want to use up my dhcp pool. The mac addresses do not match the ones in ifconfig. What can I do to make this behaviour stop ? By the way, these ip addresses are not pingable also I own only one pi.
Image

Thanks

epoch1970
Posts: 5130
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: Pi taking many IPs from Router DCHP pool

Thu Mar 12, 2020 5:45 pm

So that machine has 9 interfaces?
In this case, using 6 IPs sounds almost reasonable...

Which OS is that?
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

ob2s
Posts: 3
Joined: Thu Mar 12, 2020 4:11 pm

Re: Pi taking many IPs from Router DCHP pool

Thu Mar 12, 2020 5:59 pm

epoch1970 wrote:
Thu Mar 12, 2020 5:45 pm
So that machine has 9 interfaces?
In this case, using 6 IPs sounds almost reasonable...

Which OS is that?
OS -> Linux raspberrypi 4.19.97-v7l+ #1294 SMP Thu Jan 30 13:21:14 GMT 2020 armv7l GNU/Linux

I don't understand where the mac addresses the router sees are created.

Here is ifconfig

docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:18:34:67:ea txqueuelen 0 (Ethernet)

eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether dc:a6:32:1c:6b:13 txqueuelen 1000 (Ethernet)

hassio: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.30.32.1 netmask 255.255.254.0 broadcast 172.30.33.255
ether 02:42:c8:1b:dd:52 txqueuelen 0 (Ethernet)

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 1000 (Local Loopback)

veth87db9b6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.1.231 netmask 255.255.0.0 broadcast 169.254.255.255
ether f6:4f:56:29:74:f7 txqueuelen 0 (Ethernet)

veth9f26195: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.206.203 netmask 255.255.0.0 broadcast 169.254.255.255
ether ce:e3:99:28:2f:60 txqueuelen 0 (Ethernet)

vetha722cff: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.224.18 netmask 255.255.0.0 broadcast 169.254.255.255
ether 1e:a2:f3:44:a6:62 txqueuelen 0 (Ethernet)

vethbe9bbaf: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.81.242 netmask 255.255.0.0 broadcast 169.254.255.255
ether c6:17:f6:6c:21:40 txqueuelen 0 (Ethernet)

vethc1c8c91: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.167.57 netmask 255.255.0.0 broadcast 169.254.255.255
ether ee:9b:d3:3e:4a:61 txqueuelen 0 (Ethernet)

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.1.10.101 netmask 255.255.255.0 broadcast 10.1.10.255
ether 8e:15:f0:b9:4e:e2 txqueuelen 1000 (Ethernet)

User avatar
B.Goode
Posts: 10356
Joined: Mon Sep 01, 2014 4:03 pm
Location: UK

Re: Pi taking many IPs from Router DCHP pool

Thu Mar 12, 2020 6:07 pm

Possibly a consequence of the unspecified tasks (are they called containers?) that are being invoked by Docker?

(I think that might have been a useful detail to add to your introduction... )

epoch1970
Posts: 5130
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: Pi taking many IPs from Router DCHP pool

Thu Mar 12, 2020 6:09 pm

Hassio has a support forum. Did you try it?
https://community.home-assistant.io
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

BobHamil
Posts: 76
Joined: Sun Mar 08, 2020 9:37 pm

Re: Pi taking many IPs from Router DCHP pool

Thu Mar 12, 2020 6:12 pm

Being that the addresses are APIPA addresses (169.254.x.x), they shouldn't be coming from the router...

bls
Posts: 641
Joined: Mon Oct 22, 2018 11:25 pm
Location: Seattle, WA
Contact: Twitter

Re: Pi taking many IPs from Router DCHP pool

Thu Mar 12, 2020 7:02 pm

If you're using Network Manager to control your network, that would explain the varying MAC addresses. See the last post on this thread viewtopic.php?f=28&t=237623&sid=ad54bad ... 5682969e48. I haven't tried that personally, but looks like it should work.
Pi tools:
RPi SD Card Image Manager: https://github.com/gitbls/sdm
Lightweight Virtual VNC Config: https://github.com/gitbls/RPiVNCHowTo
Easy VPN installer/manager: https://github.com/gitbls/pistrong
DNS/DHCP manager:https://github.com/gitbls/ndm

Return to “Networking and servers”