The #DHCP server, running on the #OpenWRT router, assigned an internal IP to a client. However this IP was already used by a central NAS device. This situation is called an IP address conflict.

The #DHCP server, running on the #OpenWRT router, assigned an internal IP to a client. However this IP was already used by a central NAS device. This situation is called an IP address conflict.

In our latest #tutorial we show where to find the current DHCP leases, how to create a static and remove an existing lease on @openwrt .

https://www.geekersdigest.com/how-to-manually-remove-a-dhcp-lease-on-openwrt-router/

0 points · 5 comments · view on lemmy.world

5 Comments

vk6flab@lemmy.radio · 7 pts · 104d (4 replies)

Better yet, only run one DHCP server per network.

gratux@lemmy.blahaj.zone · 7 pts · 104d (3 replies)

and make sure all static IPs are known to that DHCP server.

vk6flab@lemmy.radio · 1 pts · 104d (2 replies)

Indeed!

acesabe@infosec.exchange · 1 pts · 104d (1 reply)

@vk6flab
Personally I only assign static IP addresses that are not in the DHCP pool range which should prevent any IP address assignment conflicts... Reserved addresses seem like a hack to enable static addresses within the dynamic pool range...but that's just my opinion
@gratux

vk6flab@lemmy.radio · 2 pts · 104d

Given that everything on my network gets their details via DHCP, I allocate the static ones within the range, generally speaking the pretty (memorable) numbers, but allocated by the DHCP server, so from the perspective of everything on the network, it's just another DHCP address, just that it never changes.