Unable to remove neighbor entry

Started by eggflamingo, December 19, 2025, 01:40:51 PM

Previous topic - Next topic
Some time ago i made a few static arp entries in the 'Interfaces > Neighbors'. Currently one of the entries has become obsolete and i wanted to remove it, but i am unable to do so.

I select the entry, click the delete button and apply. But the entry remains.

I've flushed my arp table and i don't see any leases referring to this device. Nor do i have any reservations in my DHCP services (not in KEA, ISC nor dnsmasq). I also checked my firewall rules but there is no reference to the device there either.
Previously i used ISC DHCP but i have switched to dnsmasq since about a year ago. And i think this neighbor entry is still from the time i used ISC DHCP.

am i doing something wrong or missing something obvious?

I tested on 25.7.10 and it adds and deletes the neighbor entry from the configuration.

It likely does not remove the neighbor from the ARP table until a reboot. Static ARP in ISC DHCP may change that if you apply there but that's for historic reasons.  There are upcoming changes related to these topics in 26.1.

So in case I haven't answered your question or bug can you be more precise?


Thanks,
Franco

Not sure how precise i can be tbh.

i am running 25.7.10 currently. I have rebooted the router several times since creating this post.
I did notice something , that the entry from neighbors was back in the arp table after flushing it (which is probably correct since i couldn't remove it)

What i do is:

I go to Interfaces > Neighbors. Select the entry i want to remove (check-marked) > click delete button > click yes to confirm > get the message near Apply "after changing settings, please remember to apply them" > so i click Apply.
The entry still remains in the Neighbors list.
I then rebooted the router (For good measure). After reboot, the static entry in Neighbors is still there (as well as in the Diagnostics > Arp Table).

This situation is not the end of the world of course. i can simply ignore the reserved IP address for now. But it is odd.

If you're not using static ARP and the neighbor is found via ARP it's not going anywhere.


Cheers,
Franco