NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
fade6
Jun 18, 2020Aspirant
Changing Backhaul Channel (to Help with Wireless Speakers)
Hello all. I wanted to update an older post regarding using telnet to change the hidden channel backhaul. First, a little background:
My router/sats = RB40/RBS40
Orbi is used as a router (not AP)
Wired/ethernet connected from router to 2 RBS40 sats
Wireless connected from router to outdoor orbi (RBSY50)
Wireless sound bar with subwoofer and rear speakers that communicate to sound bar via upper band 5 GHz channels (~157)
The problem, as many on the internet have posted about - some here - is that the router backhaul is set in this range (mine was channel 157) and not configurable using the web interface. Leading to impossible to deal with interference since the router and speakers are close by (and tough to move around). So someone posted a telent configuration allowing the backhaul channel to be changed (see message 11): https://community.netgear.com/t5/Orbi/Wireless-Backhaul-Channel/m-p/1802878
However, I found that the instructions for me didn't work and required a little tweaking. For some reason, "2nd hidden channel" pulled up my fronthaul 5 Ghz (which was 48 in my case). I fooled around a little bit and found that if you instead use the commands listed below, they in fact did pull up and allow me to change the hidden channel backhaul to 108 successfully. Not sure why this was the case for me, but would be interested to hear if anyone knows why. The key thing in all this for those who are not savvy with these kinds of things, like me, is to have a wifi analyzer on your phone to make sure you see all the channels being used by you and your neighbors. That is how I knew my backhaul was on channel 157. Anyways - just trying to help those who are in my situation with the wireless speakers.
- The following are the commands that worked for me:
- To read the existing channel: config get wla_hidden_channel
- To change the channel to e.g. channel 108: config set wla_hidden_channel=108
14 Replies
- ZeusyZeusAspirantHey fade6 thank you I actually tried that from the telnet post before yours and I didn’t see any change. Really appreciate you taking the time to help the others having these frustrating issues! Any other thoughts on how I can get it to not interfere? Are you no longer having WiFi interference? Was was your issue before speaker cracking or poor WiFi connectivity. I have the connectivity issue.
- fade6Aspirant
Yeah, same system you have HW-Q90R... popping noises... drops from the rear set.
Try what I posted one last time. My orbi backhaul has been on Channel 108 nice and steady for a week now. Speakers are working perfectly. As other posted - channel 108 is one of the radar channels, so if you live in an area that uses radar, the Orbi will kick it back to where it was... so cross your fingers. I hope it works for you!
- ZeusyZeusAspirantBtw message 11 in that previous post shows your resolution. Wasn’t that the exact same thing?
- fade6Aspirant
Same approach, but different config wording. When you do the "config get" command, what number does it tell you back? In my case "2nd hidden channel" was telling me 48. That is NOT the one you want to change. In my case "hidden channel" was 157. THAT is the one you want to change.
- ZeusyZeusAspirantHidden channel shows 48 so I set it to 108 like you mentioned. 2nd hidden channel was 157. I set that to 108 didn’t see any difference. 😔
We are having different issues though it seems. My issue is my WiFi connection anywhere near the soundbar is complete trash I’m use to getting 400mbps WiFi and I’ve had it as low as 40mbps lately I moved router and I’m getting 120mbps when I’m lucky but still when I unplug soundbar I get 400mbps. That’s just nuts!
- ZeusyZeusAspirantOk so the command you listed shows my front haul channel of 48 (same as yours). You’re saying change this to 108? I’ll try it.
- Retired_Member
I'm having the same issues, when I tired to put the settings in I get
/bin/ash: config: not found