-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AP doesn't boot with active WAN #633
Comments
Thanks. Did this work okay on a previous nightly (it's probably a firewall change)? |
It worked as of 3.22.12 (the last version I flashed to my hAP Lite). It only started happening as of the first nightly build made available for the hAP AC2 ( I believe I first placed it into service on Monday, Jan 3rd). I've since reflashed with build I posted in my OP which I am currently running |
Can you describe what's plugged into you hAP AC2? Is there just the single cable plugged into the WAN port? If not, what else is connected. Do these cables plug into switches? Are any external VLANs configured? |
WAN port is plugged directly into TPLink AX1800 Router. Port 1 connected to TPLink TL-SG108E switch (configured for 2 VLANS). Port 2 connected to GrandStream GXP1620 phone |
Could I request the following while running the current nightly:
|
Only problem is it will not boot with WAN hence I can't download the support file |
I have my dev hAP AC2 on my desk (it has a serial cable connected which is helpful at times). If I boot it up with just a WAN cable connected it does boot. For me when I insert the power, the PWR light comes on, then in a moment the USR light comes on indicating the device is in the boot loader. After a while this light goes off again, then starts to flash as the AREDN software boots. Eventually it goes steady again as boot is completed. Very occasionally I've noticed inserting the power never has the USR light come and the device doesn't correct power up (no output on the serial line). This hasn't seemed correlated to what cables I have inserted. I've found unplugging for a dozen seconds the retrying helped (immediately retrying didn't). Anyway, booting up with WAN only cable at the moment and it's currently sitting not finding my -2 mesh network, but that can take 3-10 minutes sometimes on this device (another bug, but at least only on boot). |
I've waited longer than 15 minutes for it to boot with WAN and it never did. I have noticed the power LED as you mentioned - it does come on solidly as you describe but no boot. What's this serial connection you're referring to? |
Just loaded the brand new nightly build (2166-fdeda7d ) and no improvement to the WAN problem as reported in my OP |
Re-reading these notes I'm confused about one thing. At one point you mention the hAP Lite but mostly the hAP AC2. How did the Lite impact this? Also, can you try booting up the hAP AC2 without the WAN connected, then plug it in once you see the USR light flashing? It's not no help to you I realize, but have an hAP AC2 running as my tunnel server, and I know of a couple more that have been deployed. |
I replaced my hAP Lite with the AC2 (the Lite never had this problem) when I saw there was now firmware for the AC2 available. As for the WAN connection, yes. If I remove the WAN connection while the AC2 is booting and plug the WAN cable back in after I see the access point is broadcasting, all is good. |
Odd. Although I had exactly your problem but with the hAP Lite - with the WAN plugged in it would often fail to reboot, or take forever to do it. |
If you plug the WAN port into something else will it boot up - say your laptop LAN port? |
Did a little rummaging around and found this discussion: |
Can you log into the problem node and type the following:
Then reboot with the WAN connected and see if the problem is resolved. |
I've created a PR to do this automatically once you confirm it fixes the issue. |
Yes, I ran those commands and not only did it reboot fine with the WAN active, it seems to reboot much faster than previously |
Nightly 2124-6dac4c6
hAP AC2 - if booted (cold or warm) with WAN connection made, AP doesn't broadcast SSID so can't connect. If booted (cold or warm) without WAN connection, AP comes alive
supportdata-AH6LE-HAP-SHOP-202210191622.gz
The text was updated successfully, but these errors were encountered: