I cannot add a screen shot.Sooo.
I can not get to my hAp AC3 after an update. The mac address is shown but not the node name.
From my connected node with the update shows the neighborhood mac address.
Clicking on that mac address gets a page not showing the ip address.
Apparently one can not edit or insert the ip address for this sub-page pullup.
I have reset my main router. Pulled the power plug on the hAp AC3 for a hard reset.
ipconfig shows 10.30.165.97 for lan, but 192.168.254.254 for a gateway.
My only alternative is to go back to initial install but before I do; has anyone had this happen to their system as well?
Greg
I can not get to my hAp AC3 after an update. The mac address is shown but not the node name.
From my connected node with the update shows the neighborhood mac address.
Clicking on that mac address gets a page not showing the ip address.
Apparently one can not edit or insert the ip address for this sub-page pullup.
I have reset my main router. Pulled the power plug on the hAp AC3 for a hard reset.
ipconfig shows 10.30.165.97 for lan, but 192.168.254.254 for a gateway.
My only alternative is to go back to initial install but before I do; has anyone had this happen to their system as well?
Greg
You did save a backup, yes?
73, Chuck
I may have but since I can not reach the AC3 hAp I have no way to load or boot it . Looks like a re-flash unless the nightly has a bug in mac address association with node names?
I used a few other nodes to test this theory out and have noticed a long delay in recapturing node names to show up in the Neighbor listing.
What I was doing was to first update my DtD nodes before updating my hAp. But when I first updated my hAp before updating my nodes is when the Hap got "ghosted" and grayed out on the DtD node side of neighbor list and then unreahable as clicvking on the gray mac address puts up the mini page showing no ipadress. ipconfig syays otherwise but then my browser does not accept the 10.30.xxx.xxx connect. It doesnt matter what cpu I use so something is amiss that I dont understand.
Greg
I do not understand how you have access to DtD nodes, but
not have access to an indoor node. (hAP-ac3 is an indoor device)
I, too, have found that these recent releases (~2026) sometimes seem to
't a k e f o r e v e r' to link after a firmware upgrade or setting change that requires a reboot. :-(
This is especially aggravating when managing remote sites with a laptop in a car.
I see that Jim K6CCC has followed up with some questions.
Please be more specific in your statements/answers.
When using a browser to access a node, are you prefixing 'http://' to the address?
Often my browser insists on prefixing 'https://' to the browser location name. :-(
Other tools like 'ping' or 'nmap' sometimes help with debugging.
Maybe posting a cropped image would help.
Usually screenshots don't help much unless your screensize is 600x600. ;-)
73, Chuck
I do not understand how you have access to DtD nodes, but
not have access to an indoor node. (hAP-ac3 is an indoor device)
I, too, have found that these recent releases (~2026) sometimes seem to
't a k e f o r e v e r' to link after a firmware upgrade or setting change that requires a reboot. :-(
This is especially aggravating when managing remote sites with a laptop in a car.
I see that Jim K6CCC has followed up with some questions.
Please be more specific in your statements/answers.
When using a browser to access a node, are you prefixing 'http://' to the address?
Often my browser insists on prefixing 'https://' to the browser location name. :-(
Other tools like 'ping' or 'nmap' sometimes help with debugging.
Maybe posting a cropped image would help.
Usually screenshots don't help much unless your screensize is 600x600. ;-)
73, Chuck
Yes, some of those answers are related.
If the network configuration is anything except dead simple, include a network drawing.