Convexa B1300 drops connection after 3.203 firmware upgrade

stavol · 2021-08-27T02:13:44.988Z

alzhao:

Yes. Checking this problem now.

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

lizh · 2021-08-27T08:46:29.490Z

Hi stavol,

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

jbourne · 2021-09-01T14:25:30.963Z

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

stavol · 2021-09-06T01:31:06.812Z

lizh:

Hi stavol,

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

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.

Issues with firmware V3.203 on B1300 and S1300 Technical Support for Routers

Dear community, want to describe my issues with latest firmware V3.203. I have a quite big wifi network, it is composed from S1300 Main router and 4 pcs B1300 as Mesh satellites. I have updated all devices to V3.203 today, because i couldn’t pair S1300 on V3.203 with B1300 on lower versions. Using the system for half a day i have spotted following issues: Routers randomly restarts. It happens like 1 time in 2-3 hours. I will monitor this restarts and will try to find out why they happen. M…

stavol · 2021-09-06T01:32:20.537Z

jbourne:

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

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

bullza · 2021-09-06T20:27:52.928Z

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.

alzhao · 2021-09-07T03:29:57.402Z

Checking mesh stability problems on B1300.

bullza · 2021-09-07T13:00:14.513Z

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

stavol · 2021-09-09T06:59:36.996Z

But you were able to set-up the mesh?

I couldn’t even make them mesh with each other

limbot · 2021-09-09T07:58:36.115Z

@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) :

Reset master node
Connect master node via WAN port
Setup master node to get a working internet connection
Scan surrounding WiFi channels to find best channels to set both the 2.4 and 5 Ghz channels to
Set the WiFi up on the master node to match appropriate channels as per 4 above
Also pay attention to bandwidth (20,40,80) depending on environment
Reset 1st slave node
Place slave node near the master node
Press the mesh button on the masternode until the second faster flash and release
Press the mesh button on the slave node until the second faster flash and release
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.
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.
Change the mesh name and password to what you want it to be on the mesh node on the master node
If you have additional nodes, reset them, bring them close to the master node and slave node
Repeat steps 9-12 above until you see node 2, node 3 etc and solid mesh lights
Place the nodes where you want them
Find the optimal position for the nodes so that all nodes show connecting to the mesh (solid led)

Hope this helps

stavol · 2021-09-10T02:05:10.941Z

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.

limbot · 2021-09-10T02:07:49.982Z

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

kelzamedic · 2021-10-18T21:33:22.428Z

So, also here on this thread due to loosing Mesh capabilities with the 3.203 firmware uodate.

I’m running a S1300 (master with USB/Wan internet) and a B1300 (slave), which both worked flawlessly prior to the S1300 taking the update.

I’ve reverted the S1300 back to Firmware 3.105, but following the mesh setup, ad I have successfully in the past, I loose the ability to access the S1300 GUI when the router is in mesh mode, following the rollback to the 3.105 firmware.

Possible that a plugin got lost in the mix? Any suggestions?

alzhao · 2021-10-19T06:20:40.255Z

If S1300 is the master, you should not loose the admin panel. Except for mesh, did you make other settings?

kelzamedic · 2021-10-19T11:24:49.080Z

All that was done was updating firmware on the S1300 to 3.203. Per the GUI, no settings were saved to “prevent compatibility issues.” When I pressed and held the Mesh button until the blink pattern changed, about 5 seconds, I saw the separate 5G SSID disappear and the mesh light blinked like it was attempting to set up mesh. When reconnected to the router, I was not able to return to the GUI while it was in Mesh mode. I was able to return to the GUI as soon as I shut off the Mesh mode without changing any other settings. This process was tried with multiple computers and different OS without changes. This resulted in our reverting back to firmware 3.105, but it is behaving the exact same.

So, that’s why I’m wondering if not maintaining settings and plugins may have caused the problem, hence the question regarding a lost plugin.

lizh · 2021-10-20T03:18:26.667Z

Hi kelzamedic,
Confirm the version:
S1300:3203
B1300:3.105

Then the MESH of S1300 and B1300 is not work properly,but only network of S1300 could works normally?
Is that the case?

kelzamedic · 2021-10-20T04:02:07.785Z

The S1300 was updated to v3:203, which caused it to become inaccessible in MESH mode. It was then reverted to v3:105, where it remains and when MESH mode is entered, the unit is not accessible by wired or wireless connection. I have performed a reset, have reflashed with v3:105, and the unit remains inaccessible as soon as I press the mesh button and it enters mesh mode. It appears that the unit is not providing DHCP support in mesh to any connected client, and even with a client on a static IP, it remains inaccessible.

The B1300 has not been updated.

lizh · 2021-10-20T06:50:17.154Z

Is the WAN port of the S1300 connected to an upper-layer network cable when the MESH network is established？

When the MESH network is established, the S1300 serves as the main route and requires the WAN port to be connected to the network cable. Otherwise it will be configured as a sub-routing, which is the network function will be abnormal and there will be no DHCP function.

kelzamedic · 2021-10-20T11:10:33.658Z

No, the S1300 is not connected to an upper-level network cable when the Mesh is established, and it never has been in my application. The reason for the use of the S1300 for us is the capability of USB-Wan, which is successfully running when the unit is placed in mesh mode. This has historically and repeatedly worked for us until this upgrade and downgrade.

kelzamedic · 2021-10-20T16:33:03.731Z

Success with these steps:

Factory reset master node by holding down the power button until the power light blinks rapidly and shuts off. Release the power button. (Bench tests show a more successful initial mesh if the master is operating on a clean UI.)
Connect master node via WIFI or Ethernet
Log into master node UI at 192.168.8.1. Perform the initial language selection and administrative password update.
Ensure that there is a powered ethernet device on the WAN port-this does not need to be an upstream device, it is required for the Master to identify itself as the master when entering the mesh mode.
Ensure that there are no other devices via WIFI or LAN, other than your connected PC and the step 3 WAN port connected.
Ensure that there are no ethernet or WAN connections to the slave.
Reset 1st slave node
Place slave node near the master node
Press the mesh button on the master node until the second faster flash and release
Press the mesh button on the slave node until the second faster flash and release
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.
You can go to 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.
If you have additional nodes, reset them, bring them close to the master node and slave node
Repeat steps 9-12 above until you see node 2, node 3 etc and solid mesh lights
Change the mesh name and password to what you want it to be on the mesh node on the master node
Place the nodes where you want them
Find the optimal position for the nodes so that all nodes show connecting to the mesh (solid led)

I attempted additional mesh connections after the 3.203 update on both the S1300 and the B1300, thinking that doing a master reset on both, updating both to 3.203, master resetting the B1300 and going through the procedure which was successful above, might work as if you had an existing mesh between the same units and updated the master that the slave wouldnt have the new firmware.

This was initially successful in creating a mesh with both units under the 3.203 firmwares on both units, but both became unstable and lost internet connection after time.

I also noted that the B1300 unit seems unable to take the Luci or other plugins after the 3.203 firmware update. This appeared as an insufficient memory/storage in the unit. Not sure if this is causing issues with the mesh as it is attempting to receive information from the master.

Both have been reverted to the 3.105 firmware and following the procedure above, are meshed and up and running stable.

Recommend that tech support use the above amended procedure for instructions in establishing a mesh between a S1300 (master) and a B1300 (slave) in a firmware 3.105 mesh scenario. Please update us here when the 3.203 mesh is stable.

Thanks for everyone’s input.