3 ms·
Isn’t that a DoS vulnerability?
by drdexebtjl 3mo ago
Isn’t that a DoS vulnerability?
- toast0 3mo agoIf somebody is arping for all the addresses on your broadcast domain, it will cause a denial of service, yes. It will make your dhcp server mad, too. Not much to do about that if you're not using managed switches. With managed switches, maybe you can spend an unreasonable amount of effort to try to prevent it, or you can just deal with it if it happens. Probably the 'right' way is to give each port its own broadcast domain and subnet, then it's pretty hard to mess up the other clients.
- drdexebtjl 3mo agoWhat would go wrong with the DHCP server if it simply did not check if someone’s responding to pings at that address before handing out the lease?
- thyristan 3mo agoNothing with the DHCP server. But as per the article, many clients won't accept such an address. And even if they would accept it, duplicate IP assignments are yet another exciting and hard to debug network problem.
- Walf 3mo agoEspecially when it's caused by identical MAC addresses! https://www.reddit.com/r/pics/comments/l9r17/now_we_know_why_the_network_stopped_working/ https://www.reddit.com/r/pics/comments/l9r17/now_we_know_why...
- nubinetwork 3mo agoI believe some clients (dhcpcd, networkd) also do the check on their side, so it's possible that they reject the lease and ask for a new one if it's in use.
- toast0 3mo agoOn the dhcp server, nothing really? But the address isn't usable if this host is arping for it.