Convexa B1300 drops connection after 3.203 firmware upgrade

Hi,

I’m using 2 Convexa B1300 in MESH environment with some 20 clients connected on both network bands (2,4GHz and 5Ghz). Before 3.203 firmware upgrade, setup was working flawlessly without any disruption for months. After the upgrade router drops connection randomly 2 or 3 times a day for no apparent reason and picks up again. Any suggestions or simillar problems?

here is system log

Thu Aug 19 15:46:41 2021 daemon.info hostapd: ath0: STA 84:f3:eb:78:f1:57 IEEE 802.11: authenticated
Thu Aug 19 15:46:41 2021 daemon.info hostapd: ath0: STA 84:f3:eb:78:f1:57 IEEE 802.11: associated (aid 2)
Thu Aug 19 15:46:41 2021 daemon.info hostapd: ath0: STA 84:f3:eb:78:f1:57 WPA: sending 1/4 msg of 4-Way Handshake
Thu Aug 19 15:46:41 2021 daemon.info hostapd: ath0: STA 84:f3:eb:78:f1:57 WPA: received EAPOL-Key frame (2/4 Pairwise)
Thu Aug 19 15:46:41 2021 daemon.info hostapd: ath0: STA 84:f3:eb:78:f1:57 WPA: sending 3/4 msg of 4-Way Handshake
Thu Aug 19 15:46:41 2021 daemon.emerg procd: Command failed: Not found
Thu Aug 19 15:46:41 2021 daemon.info hostapd: ath0: STA 84:f3:eb:78:f1:57 WPA: received EAPOL-Key frame (4/4 Pairwise)
Thu Aug 19 15:46:41 2021 daemon.info hostapd: ath0: STA 84:f3:eb:78:f1:57 RADIUS: starting accounting session F25B11DB4BA76A0F
Thu Aug 19 15:46:41 2021 daemon.info hostapd: ath0: STA 84:f3:eb:78:f1:57 WPA: pairwise key handshake completed (RSN)
Thu Aug 19 15:46:41 2021 kern.err kernel: [ 116.955531] wlan: [90:I:ANY] FWLOG: [30166]
Thu Aug 19 15:46:41 2021 kern.err kernel: [ 116.955585] wlan: [90:I:ANY] RATE: ChainMask 1, peer_mac f1:57, phymode 5, ni_flags 0x00201006, vht_mcs_set 0x0000, ht_mcs_set 0x00ff, legacy_rate_set 0x0fff
Thu Aug 19 15:46:41 2021 kern.err kernel: [ 116.955585]
Thu Aug 19 15:46:41 2021 kern.err kernel: [ 116.959045] wlan: [90:E:ANY] [soc0] FWLOG: [30203] WAL_DBGID_SECURITY_UCAST_KEY_SET ( 0xf157, 0x0)
Thu Aug 19 15:46:41 2021 kern.err kernel: [ 116.959045]
Thu Aug 19 15:46:41 2021 kern.err kernel: [ 116.974557] wlan: [90:E:ANY] [soc0] FWLOG: [30203] WAL_DBGID_SECURITY_ENCR_EN ( )
Thu Aug 19 15:46:41 2021 kern.err kernel: [ 116.974557]
Thu Aug 19 15:46:41 2021 kern.err kernel: [ 116.984932] wlan: [90:E:ANY] [soc0] FWLOG: [30203] WAL_DBGID_SECURITY_ALLOW_DATA ( 0x4413cc)
Thu Aug 19 15:46:41 2021 kern.err kernel: [ 116.984932]
Thu Aug 19 15:46:41 2021 kern.err kernel: [ 116.995317] wlan: [90:E:ANY] [soc0] FWLOG: [30203] WAL_DBGID_SECURITY_ENCR_EN ( )
Thu Aug 19 15:46:41 2021 kern.err kernel: [ 116.995317]
Thu Aug 19 15:46:41 2021 kern.err kernel: [ 117.003829] wlan: [90:E:ANY] [soc0] FWLOG: [30203] WAL_DBGID_SECURITY_ALLOW_DATA ( 0x4413cc)
Thu Aug 19 15:46:41 2021 kern.err kernel: [ 117.003829]
Thu Aug 19 15:46:41 2021 kern.err kernel: [ 117.012987] wlan: [90:I:ANY] FWLOG: [30288]
Thu Aug 19 15:46:41 2021 kern.err kernel: [ 117.023890] wlan: [90:I:ANY] RATE: ChainMask 1, peer_mac f1:57, phymode 5, ni_flags 0x00201006, vht_mcs_set 0x0000, ht_mcs_set 0x00ff, legacy_rate_set 0x0fff
Thu Aug 19 15:46:41 2021 kern.err kernel: [ 117.023890]
Thu Aug 19 15:46:41 2021 daemon.err gl_mqtt_service[10138]: timestamp invalid
Thu Aug 19 15:46:41 2021 daemon.err gl_mqtt_service[10138]: utils_NLB failed!
Thu Aug 19 15:46:41 2021 daemon.info hostapd: ath1: STA ce:be:f4:82:e8:b0 IEEE 802.11: authenticated
Thu Aug 19 15:46:42 2021 daemon.info hostapd: ath1: STA ce:be:f4:82:e8:b0 IEEE 802.11: associated (aid 2)
Thu Aug 19 15:46:42 2021 daemon.info hostapd: ath1: STA ce:be:f4:82:e8:b0 WPA: sending 1/4 msg of 4-Way Handshake
Thu Aug 19 15:46:42 2021 daemon.info hostapd: ath1: STA ce:be:f4:82:e8:b0 WPA: received EAPOL-Key frame (2/4 Pairwise)
Thu Aug 19 15:46:42 2021 daemon.info hostapd: ath1: STA ce:be:f4:82:e8:b0 WPA: sending 3/4 msg of 4-Way Handshake
Thu Aug 19 15:46:42 2021 daemon.info hostapd: ath1: STA ce:be:f4:82:e8:b0 WPA: received EAPOL-Key frame (4/4 Pairwise)
Thu Aug 19 15:46:42 2021 daemon.info hostapd: ath1: STA ce:be:f4:82:e8:b0 RADIUS: starting accounting session EB4E35408875DBC0
Thu Aug 19 15:46:42 2021 daemon.info hostapd: ath1: STA ce:be:f4:82:e8:b0 WPA: pairwise key handshake completed (RSN)
Thu Aug 19 15:46:42 2021 kern.err kernel: [ 117.539918] wlan: [90:I:ANY] FWLOG: [19601]
Thu Aug 19 15:46:42 2021 kern.err kernel: [ 117.539969] wlan: [90:I:ANY] RATE: ChainMask 1, peer_mac e8:b0, phymode 10, ni_flags 0x1621b006, vht_mcs_set 0xfffe, ht_mcs_set 0x00ff, legacy_rate_set 0x0ff0
Thu Aug 19 15:46:42 2021 kern.err kernel: [ 117.539969]
Thu Aug 19 15:46:42 2021 kern.err kernel: [ 117.543373] wlan: [90:E:ANY] [soc1] FWLOG: [19609] MGMT_TXRX_MU_GID_MGMT ( 0xc0, 0x2, 0x1, 0xfffe, 0x0)
Thu Aug 19 15:46:42 2021 kern.err kernel: [ 117.543373]
Thu Aug 19 15:46:42 2021 kern.err kernel: [ 117.559296] wlan: [90:E:ANY] [soc1] FWLOG: [19609] MGMT_TXRX_MU_GID_MGMT ( 0xc4, 0x404114, 0x0, 0x0, 0x0)
Thu Aug 19 15:46:42 2021 kern.err kernel: [ 117.559296]
Thu Aug 19 15:46:42 2021 kern.err kernel: [ 117.569991] wlan: [90:E:ANY] [soc1] FWLOG: [19612] MGMT_TXRX_MU_GID_MGMT ( 0xadd, 0x2, 0x1)
Thu Aug 19 15:46:42 2021 kern.err kernel: [ 117.569991]
Thu Aug 19 15:46:42 2021 kern.err kernel: [ 117.580766] wlan: [90:E:ANY] [soc1] FWLOG: [19638] WAL_DBGID_SECURITY_UCAST_KEY_SET ( 0xe8b0, 0x0)
Thu Aug 19 15:46:42 2021 kern.err kernel: [ 117.580766]
Thu Aug 19 15:46:42 2021 kern.err kernel: [ 117.591384] wlan: [90:E:ANY] [soc1] FWLOG: [19638] WAL_DBGID_SECURITY_ENCR_EN ( )
Thu Aug 19 15:46:42 2021 kern.err kernel: [ 117.591384]
Thu Aug 19 15:46:42 2021 kern.err kernel: [ 117.600868] wlan: [90:E:ANY] [soc1] FWLOG: [19638] WAL_DBGID_SECURITY_ALLOW_DATA ( 0x4413cc)
Thu Aug 19 15:46:42 2021 kern.err kernel: [ 117.600868]
Thu Aug 19 15:46:42 2021 kern.err kernel: [ 117.613899] wlan: [90:E:ANY] [soc1] FWLOG: [19638] WAL_DBGID_SECURITY_ENCR_EN ( )
Thu Aug 19 15:46:42 2021 kern.err kernel: [ 117.613899]
Thu Aug 19 15:46:42 2021 kern.err kernel: [ 117.620663] wlan: [90:E:ANY] [soc1] FWLOG: [19638] WAL_DBGID_SECURITY_ALLOW_DATA ( 0x4413cc)
Thu Aug 19 15:46:42 2021 kern.err kernel: [ 117.620663]
Thu Aug 19 15:46:42 2021 daemon.emerg procd: cat: can’t open ‘/etc/os-release’: No such file or directory
Thu Aug 19 15:46:42 2021 user.notice wireguard: wireguard client start
Thu Aug 19 15:46:42 2021 daemon.emerg procd: cat: can’t open ‘/etc/os-release’: No such file or directory
Thu Aug 19 15:46:42 2021 daemon.info procd: - init complete -
Thu Aug 19 15:46:43 2021 daemon.info hostapd: ath11: STA 9e:83:c4:02:10:dc IEEE 802.11: authenticated
Thu Aug 19 15:46:43 2021 daemon.info hostapd: ath11: STA 9e:83:c4:02:10:dc IEEE 802.11: associated (aid 1)
Thu Aug 19 15:46:43 2021 daemon.info hostapd: ath11: STA 9e:83:c4:02:10:dc WPA: sending 1/4 msg of 4-Way Handshake
Thu Aug 19 15:46:43 2021 daemon.info hostapd: ath11: STA 9e:83:c4:02:10:dc WPA: received EAPOL-Key frame (2/4 Pairwise)
Thu Aug 19 15:46:43 2021 daemon.info hostapd: ath11: STA 9e:83:c4:02:10:dc WPA: sending 3/4 msg of 4-Way Handshake
Thu Aug 19 15:46:43 2021 daemon.info hostapd: ath11: STA 9e:83:c4:02:10:dc WPA: received EAPOL-Key frame (4/4 Pairwise)
Thu Aug 19 15:46:43 2021 daemon.info hostapd: ath11: STA 9e:83:c4:02:10:dc RADIUS: starting accounting session 99EE8FB77B9928AC
Thu Aug 19 15:46:43 2021 daemon.info hostapd: ath11: STA 9e:83:c4:02:10:dc WPA: pairwise key handshake completed (RSN)
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.538850] wlan: [90:E:ANY] [soc1] FWLOG: [21009] WAL_DBGID_TX_BA_SETUP ( 0x4413cc, 0xe8b00000, 0x0, 0x40, 0x1)
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.538850]
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.538904] wlan: [90:I:ANY] FWLOG: [21011]
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.555273] wlan: [90:I:ANY] RATE: ChainMask 1, peer_mac e8:b0, phymode 10, ni_flags 0x1621b006, vht_mcs_set 0xfffe, ht_mcs_set 0x00ff, legacy_rate_set 0x0ff0
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.555273]
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.555339] wlan: [90:I:ANY] FWLOG: [21450]
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.570332] wlan: [90:I:ANY] RATE: ChainMask 3, peer_mac 10:dc, phymode 10, ni_flags 0x0621b006, vht_mcs_set 0xfffa, ht_mcs_set 0xffff, legacy_rate_set 0x0ff0
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.570332]
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.574331] wlan: [90:E:ANY] [soc1] FWLOG: [21452] MGMT_TXRX_MU_GID_MGMT ( 0xc0, 0x1, 0x2, 0xfffe, 0x0)
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.574331]
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.590101] wlan: [90:E:ANY] [soc1] FWLOG: [21452] MGMT_TXRX_MU_GID_MGMT ( 0xc4, 0x1010448, 0x0, 0x0, 0x0)
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.590101]
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.601123] wlan: [90:E:ANY] [soc1] FWLOG: [21452] MGMT_TXRX_MU_GID_MGMT ( 0xadd, 0x1, 0x2)
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.601123]
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.611921] wlan: [90:E:ANY] [soc1] FWLOG: [21455] WAL_DBGID_SECURITY_ENCR_EN ( )
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.611921]
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.621906] wlan: [90:E:ANY] [soc1] FWLOG: [21455] WAL_DBGID_SECURITY_MCAST_KEY_SET ( 0x1)
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.621906]
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.631540] wlan: [90:E:ANY] [soc1] FWLOG: [21505] WAL_DBGID_SECURITY_UCAST_KEY_SET ( 0x10dc, 0x0)
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.631540]
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.640192] wlan: [90:E:ANY] [soc1] FWLOG: [21505] WAL_DBGID_SECURITY_ENCR_EN ( )
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.640192]
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.650734] wlan: [90:E:ANY] [soc1] FWLOG: [21505] WAL_DBGID_SECURITY_ALLOW_DATA ( 0x441254)
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.650734]
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.659645] wlan: [90:E:ANY] [soc1] FWLOG: [21505] WAL_DBGID_SECURITY_ENCR_EN ( )
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.659645]
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.669600] wlan: [90:E:ANY] [soc1] FWLOG: [21505] WAL_DBGID_SECURITY_ALLOW_DATA ( 0x441254)
Thu Aug 19 15:46:44 2021 kern.err kernel: [ 119.669600]
Thu Aug 19 15:46:45 2021 kern.err kernel: [ 120.335038] wlan: [0:I:ANY] wds_peer_event_handler: 459: wds_peer_event_handler, invalid WMI event type 3
Thu Aug 19 15:46:45 2021 daemon.info dnsmasq-dhcp[5958]: DHCPDISCOVER(br-lan) 84:f3:eb:78:f1:57
Thu Aug 19 15:46:45 2021 daemon.info dnsmasq-dhcp[5958]: DHCPOFFER(br-lan) 192.168.11.104 84:f3:eb:78:f1:57
Thu Aug 19 15:46:45 2021 kern.err kernel: [ 120.434269] wlan: [0:I:ANY] wds_peer_event_handler: 459: wds_peer_event_handler, invalid WMI event type 3

Thanks

+1 here, unexpected dropouts mesh just goes down and takes few minutes to re-establish. Could not figure out the pattern, sometimes it works for days, sometimes it’s mostly unavailable for hours.

@Mahone, have you tried downgrading the firmware? Sadly, I won’t have much time to troubleshoot it further until September.

Hi,

reverting to 3.105 on both routers, everything works fine again!

Cool, thanks a lot for confirming! Will downgrade it next week, then.

@jbourne Thanks for linking to this thread.

@Mahone Thanks for the update. Might have to do the same this weekend.

Is there any plan for a fix soon, @alzhao? Much appreciated.

Yes. Checking this problem now.

This is my initial report: Convexa B can no longer mesh after 3.203 update

In my case, I can no longer mesh the two B1300s as well.

Thank you very much.

Another user complaining about mesh issue: B1300 2 x Master Nodes MESH

Hi stavol,

I’m in the process of validating the tests, which may take some time.

1 Like

FYI: downgraded to 3.105 on Saturday, so far (5 days) mesh is rock solid.

Hi @lizh is there any update on this? Here’s another user using B1300 and S1300 having issues with mesh and 3.203 update. Thank you.

Hi. Did you downgrade on the main node only, or did you have to downgrade the sub nodes as well? Thanks.

I literally registered on the forum to report this very problem.

I bought a second Convexa-B GL-B1300 router recently to create a mesh network, and I see frequent connection drops.

This happens at least once a day for me, and it is purely random.

I am also on version 3.203 for both devices.

Checking mesh stability problems on B1300.

1 Like

Just to provide more info, the Mesh and Wifi LEDs both turn off when Wifi drops. Only the power LED is on.

But you were able to set-up the mesh?

I couldn’t even make them mesh with each other :frowning:

@stavol

I’ve got to admit that the mesh on the B/S1300 is a bit tricky and there isn’t very good Gl.iNet documenation that explains clearly how to mesh.

Here’s the best procedure (well at least the one that works for me) :

  1. Reset master node
  2. Connect master node via WAN port
  3. Setup master node to get a working internet connection
  4. Scan surrounding WiFi channels to find best channels to set both the 2.4 and 5 Ghz channels to
  5. Set the WiFi up on the master node to match appropriate channels as per 4 above
  6. Also pay attention to bandwidth (20,40,80) depending on environment
  7. Reset 1st slave node
  8. Place slave node near the master node
  9. Press the mesh button on the masternode until the second faster flash and release
  10. Press the mesh button on the slave node until the second faster flash and release
  11. Wait - this appears to take a completely random amount of time to get a proper mesh connection. Often more than the state 3-4 minutes above.
  12. You can go tto the master node @ 192.168.8.1 and watch the status of the mesh ( doing browser refreshes) , you should eventually see “Wireless” change to “Mesh” on the LHS menu and you should see node 1 appear under the mesh on the mesh page. Wait until you get solid green on both nodes.
  13. Change the mesh name and password to what you want it to be on the mesh node on the master node
  14. If you have additional nodes, reset them, bring them close to the master node and slave node
  15. Repeat steps 9-12 above until you see node 2, node 3 etc and solid mesh lights
  16. Place the nodes where you want them
  17. Find the optimal position for the nodes so that all nodes show connecting to the mesh (solid led)

Hope this helps

Thank you very much for the detailed reply.

But I just want to update that downgrading to 3.105 fixes the mesh issue.

I had to reset and downgrade the main and sub nodes, and immediately after that mesh works fine.

I don’t think I’ll upgrade again for a long time haha.

@stavol Ahh sorry, I thought you meant in general, not under 3.203 :slight_smile: