Quick background -- I'm trying to set up a station, with the initial design goal of local access and portable operation with the option to expand to a node with some good LOS back to the LA basin from Verdugo or Wilson.
I've set up an hAP ac Lite for local access and bridging to my local network. That works great and I can connect up a second mikrotik device over the passive PoE passthrough for the "real" mesh link.
I've tried a mikrotik sector antenna, no joy, and a non-XL, non-HP dish, no joy. That was clearly just a link budget problem though, I could make it to Verdugo occasionally but without enough SNR to meet reasonable link quality requirements. All this is just to say: I'm pretty sure I've gotten the basics of the SW, networking, and various configs worked out.
I got the XL HP node and expected it to be basically drop-in and it was initially -- but then I tried changing from the default tx power (I think 19dbm) to the unit's max (28dbm), and immediately it dropped off the LAN. I've done a complete reset from scratch three times now, and ever time, the moment I edit the txpwr, it loses LAN capability, continuously resetting. I can see on the switch the link come on, move a couple packets, then drop off continuously. The same happens with a direct connection to a computer -- network resets (windows shows "cable unplugged") before it's even finished configuring over and over. I also tried it with its own dedicated power supply, a different power supply, and the PoE passthrough, all have the same behavior.
I'll definitely just try making the connection at the lower power, but I'd love to have it "fully" working at some point.
In any case, I'd be very interested to see if anyone else has seen similar behavior or if there's anything folks can suggest that I try! I have confirmed that I can connect it up to my local mesh on the 5.6G channel just fine when it's set to 28dbm, interestingly -- it's just the ethernet port that resets.
Thanks!
-Devin KN6PHZ
I've set up an hAP ac Lite for local access and bridging to my local network. That works great and I can connect up a second mikrotik device over the passive PoE passthrough for the "real" mesh link.
I've tried a mikrotik sector antenna, no joy, and a non-XL, non-HP dish, no joy. That was clearly just a link budget problem though, I could make it to Verdugo occasionally but without enough SNR to meet reasonable link quality requirements. All this is just to say: I'm pretty sure I've gotten the basics of the SW, networking, and various configs worked out.
I got the XL HP node and expected it to be basically drop-in and it was initially -- but then I tried changing from the default tx power (I think 19dbm) to the unit's max (28dbm), and immediately it dropped off the LAN. I've done a complete reset from scratch three times now, and ever time, the moment I edit the txpwr, it loses LAN capability, continuously resetting. I can see on the switch the link come on, move a couple packets, then drop off continuously. The same happens with a direct connection to a computer -- network resets (windows shows "cable unplugged") before it's even finished configuring over and over. I also tried it with its own dedicated power supply, a different power supply, and the PoE passthrough, all have the same behavior.
I'll definitely just try making the connection at the lower power, but I'd love to have it "fully" working at some point.
In any case, I'd be very interested to see if anyone else has seen similar behavior or if there's anything folks can suggest that I try! I have confirmed that I can connect it up to my local mesh on the 5.6G channel just fine when it's set to 28dbm, interestingly -- it's just the ethernet port that resets.
Thanks!
-Devin KN6PHZ
Sounds like I'll probably need to try throwing more hardware at the problem :(
Try a re-load from a factory file.
This is free of cost. ;-)
73, Chuck
Just to tell me if it's definitely an AERDN-specific problem?
I'm tempted to try replacing the flash chip, though it admittedly isn't super likely to work -- more of a learning exercise than anything.
Orv W6BI
In the end, it turned out that the factory FW reset Chuck suggested, then back to AREDN nightly, resolved the glitch. I haven't yet confirmed if the AREDN stable also works now, or if the key variable is just the newer build.