Currently the resolve parameter for the getArp API call performs the opposite behavior you'd expect. When the resolve=yes parameter is supplied list_arp.pywill not resolve hostnames, while resolve=no (the default) will resolve them.
If this behavior is intentional, disregard this PR.
This does look a bit strange indeed, but may require changes in the endpoint as well. I’ll put it on the list of things to check before the 24.7 release
Currently the
resolve
parameter for the getArp API call performs the opposite behavior you'd expect. When theresolve=yes
parameter is suppliedlist_arp.py
will not resolve hostnames, whileresolve=no
(the default) will resolve them.If this behavior is intentional, disregard this PR.