While the uboot UI has some problems, it the router really flashes the firmware, it is fine.
About mesh, I see there is “cable” displayed in the 2nd node. When you pare a leaf node with main node, do not connect cable to the leaf node. After mesh you can connect a cable for backhaul.
If the above does not fix your problem. Pls let me know.
If mesh pairing ending in master solid but slave flash, you can push mesh button again at both side. No need to do reset. If that doesn’t work, you can try push mesh button more than 10 seconds to very fast flash to quit mesh mode and do pairing again.
Master node won’t be flash always unless the wan cable is not plug in, that case it’s also as a slave.
Thanks for that, but I’ve tried everything I can think of
press till very fast flash so both forget mesh/mesh setup on both units
firmware reset both units
uboot and reload software on both.
Swap physical units as master slave
Given what you just said about master node flashing I might try a different network cable and/or upstream router. Think I might have originally had the AR750s attached when it did work and these last few times I’ve been using MT300N-V2 (attaching mesh to a WISP router) .
Hi limbot,
The mesh pairing is implemented by WPS, I checked your log. It says you don’t push the slave’s mesh/WPS button to trigger WPS communication, like
PBC Status: Timed-out
Last WPS result: None
If pairing fail, push both master and slave’s mesh button for 5 second.
You can use hostapd_cli -i ath11 -p /var/run/hostapd-wifi1 wps_get_status
to confirm again.
You should be able to run the Mango from the b1300. I’m running a Ar750 off my b1300 without any issue. In fact I also have a USB camera connected to the ar750.
Thanks mate. Have removed the SMB USB key from the B1300, redirected power from the B1300 to the Mango and then the USB Key to the Mango. All seems to be working fine