Page 1 of 1
WG3526 2.4 band not staying connected
Posted: Fri Jan 18, 2019 9:48 am
by jerrett.watson
I'm having problems with my 2.4 band on WG3526 router staying connected to devices. The 5.0 band seems to lock on fine and does not have the same problem. Are there any settings I can check to troubleshoot this problem? I have WG3526 with mc7455 with GO2017 firmware. Also is the best option for the firmware setup? I'm very new to this so sorry if my questions are elementary in nature! thanks
Re: WG3526 2.4 band not staying connected
Posted: Fri Jan 18, 2019 11:29 am
by JimHelms
I would update to the latest
GoldenOrb 2019. Make sure to UNCHECK the Keep Settings Box when you reflash the router.
And, use a LAN ethernet cable to flash with as opposed to wifi.
This build should have the latest WiFi drivers. I am unsure what the WiFi password is on the new build so you probably need to set it once the firmware has updated.
Re: WG3526 2.4 band not staying connected
Posted: Fri Jan 18, 2019 11:56 am
by jerrett.watson
Got it. Thanks
Re: WG3526 2.4 band not staying connected
Posted: Thu Jan 24, 2019 7:16 pm
by jerrett.watson
I installed the latest GO2019 firmware, but the 2.4 band is still not working correctly. It was intermittent on and off for a couple of days and eventually I lost it permanently until rebooting router. The 5.0 band has been solid with no problems. Is there any other setting or firmware I can try?
Re: WG3526 2.4 band not staying connected
Posted: Fri Jan 25, 2019 7:36 am
by saw2645
Have you checked for interference for the channel your using? I know interference can cause it to drop our and lose connection.
Re: WG3526 2.4 band not staying connected
Posted: Fri Jan 25, 2019 8:06 am
by JimHelms
One member on the GoldenOrb / ROOTer forum recently posted this:
My thought, generally, is that the best location for the cellular modem and antenna isn't the best place for the wifi router.
This is an excellent point across the board. And for those that are using B41 on Sprint, having WiFi running at 2.4GHz with B41 (2.5GHz) immediately adjacent seems like a particularly bad idea. There's a little bit of a buffer, as long as you're not improperly using WiFi channels 12, 13 and 14 (not allowed here in the US) — still, these are "first cousins" and not "kissing cousins" so are best kept apart.
There are also a few posts here on the forum about decreasing the TX power from 30dBm to 15dBm on the 2.4GHz WiFi to solve similar issues.
Re: WG3526 2.4 band not staying connected
Posted: Fri Jan 25, 2019 8:22 am
by swwifty
JimHelms wrote: ↑Fri Jan 25, 2019 8:06 am
One member on the GoldenOrb / ROOTer forum recently posted this:
There are also a few posts here on the forum about decreasing the TX power from 30dBm to 15dBm on the 2.4GHz WiFi to solve similar issues.
This.
I would never set my AP to transmit at a max power AP (especially 30dbm for 2.4ghz) cause most clients can only transmit at 15-20dbm max (sometimes less) so you create an asymmetrical connection, which causes the whole AP to slow down for everyone, if you have clients that are really far away (in distance, or from shadowing in a building).
Re: WG3526 2.4 band not staying connected
Posted: Fri Jan 25, 2019 1:52 pm
by bjames
I had the 2.4ghz wifi issues as well on the wg3526. I determined my problem was band 41 (@ 2500mhz) and 2.4 wifi (@ 2400mhz) were interfering with one another. I could also see this interference in my modem's antenna signal to noise ratio when I connected a device to the 2.4 wifi. I ended up separating the wifi and LTE antennas by using external antennas on the LTE side. Problem solved.
Re: WG3526 2.4 band not staying connected
Posted: Fri Jan 25, 2019 1:58 pm
by swwifty
bjames wrote: ↑Fri Jan 25, 2019 1:52 pm
I had the 2.4ghz wifi issues as well on the wg3526. I determined my problem was band 41 (@ 2500mhz) and 2.4 wifi (@ 2400mhz) were interfering with one another. I could also see this interference in my modem's antenna signal to noise ratio when I connected a device to the 2.4 wifi. I ended up separating the wifi and LTE antennas by using external antennas on the LTE side. Problem solved.
Very good info! Thanks for sharing.