NDP table not showing Hostname
-
-
@johnpoz said in NDP table not showing Hostname:
https://docs.netgate.com/pfsense/en/latest/monitoring/status/ndp.html#ndp-table
Do they show in your NDP table @johnpoz ?
They don't on mine, yet I can do a lookup from my router and the ip address resolves to a hostname.
-
I don't normally use IPv6... But I just tested a client that has a GUA entry in unbound, and yup for sure the IPv6 PTR resolves for it..
So its host name does show up in the arp table for its IPv4 address.. But no it doesn't seem to be showing up in the NDP table.
Have to look in redmine if this is a known issue.
edit: Ok something odd.. While I can do a PTR for the IPv6 from a client.. If I do the AAAA on pfsense directly it works, but if I do the PTR I get back a servfail. This could explain no hostname in the ndp table... Hmmm
But both forward and ptr work from a client asking pfsense.. That would for sure explain why ndp table not working if pfsense can not do a PTR on itself.. Odd
edit2: Ok maybe I had something weird in in access list, or bad entry.. I just redid everything and for sure pfsense can do ptr for ipv6 address of one of my hosts gua IPv6 and works.. But yeah not showing up in the ndp table.. hmmmm
edit3: Ok must be something in the gui page just not working, because if just do a ndp -a from cmd line on pfsense shows the hostname.
edit4: If I can not find anything in redmine about this, I will put one it.. Clearly its working from ndp -a on cmd line, but gui not showing it.
-
@nogbadthebad can you concur that you shows names in ndp -a on cmd line of pfsense, but not seeing them in gui.
What version of pfsense are you running? Curious if this is being seen in 22.05, maybe I will fire up my 22.05 and see. Little point in point in putting in a redmine if working in 22.05
-
@johnpoz The hostname shows via ssh with ndp -a running 22.01, it doesn't show on the gui.
-
how can I report this to Netgate as a possible bug?
Thanks for all the comments.
-
-
@nogbadthebad no I was away for long weekend.. When I get caught up, I will check and put one in if not already there. Really like to see if still and issue with 22.05 or 2.7 as well.
-
@cjbujold Now that 22.05 is out, and still seeing the issue I have put in the redmine about this
https://redmine.pfsense.org/issues/13318
edit: Wow jimp already responded and posted a fix, so I would "assume" this will be corrected in next version.. And jimp has a patch already listed, if you are so inclined to get it working now.
"I'll commit the change above shortly."
-
@cjbujold so if you apply the patch from jimp seems to have corrected the problem
Use 8c9ab20e as the commit ID in the patches section under system.
-
@jimp Working fine here too
-