Home of the Squeezebox™ & Transporter® network music players.
Page 6 of 6 FirstFirst ... 456
Results 51 to 55 of 55

Thread: Wi-Fi 6

  1. #51
    Junior Member
    Join Date
    Apr 2020
    Posts
    6

    Verizon G3100 router

    Anyone having experience with Verizon G3100 router?

    My 2 squeezebox radios have exactly the same issues since i upgraded to Verizon's most recent router a couple of months ago. They lose connection after a few minutes. if connected to ethernet , they work just fine.

  2. #52

    wlanpoke to the rescue!

    I'm not sure if this has been mentioned in this thread or not, but there's a solution/workaround to this issue mentioned in another thread. It's a little script called 'wlanpoke' that you install on your radio and it basically monitors the WiFi connection and automatically resets the connection whenever it goes out. I experienced WiFi connection issues for months with my four SB radios and I tried all sorts of different router settings and Vonets Ethernet bridges, but nothing I tried was successful for me. Finally I stumbled across this wlanpoke script and since installing it on my radios they have been working great again. No more lost WiFi connections!!

    It's fairly easy to install if you're comfortable using a command line. Just download the zip file and follow the installation instructions in the manual.txt file.

  3. #53
    Senior Member
    Join Date
    Nov 2007
    Posts
    118
    I have found this thread of great interest, as I may be the exception. And that may offer some hope to other Wi-Fi 6 Asus users.

    We have been running an Asus AX-enabled mesh system for over a year now with 3 wireless SB legacy clients (2 Touch & 1 Radio) - with no problems whatsoever. An RT-AX88U is the router, with two AC86Us as nodes. Wi-Fi 6 is FULLY enabled on the AX88. And the Radio in particular prefers connecting to the 88 over the closer AC86 (probably because the 88s signal is just that good).

    I just spent four hours today running a Touch in an outbuilding 70 feet away from its nearest 86 node, and it played flawlessly.

    What we have encountered on one or two occasions where a wireless client refused to communicate with LMS (red signal meter) was a DHCP conflict, which was remedied by clearing the DHCP table on the router. It also helps to assign the LMS host a static address, so the clients always know where it is.

    However, as our AX client roster is growing, next week I will be swapping out both AC86s for a pair of AX XT8 nodes. One of our node locations (reaching that outbuilding) requires a wireless backhaul that the three band XT8 can better accommodate in a series configuration. The 88 will remain the router. I will be closely watching whether the legacy wireless SBs can tolerate these newer AX nodes.

    I suspect from the issues others are describing that the issue is router based. And at least in this configuration, the AX88 has gotten along with the legacy SBs, and I do not expect that to change.

    We have a total of 10 SB clients, and over 50 network clients total, but the majority are ethernet-connected.
    Last edited by sgmlaw; 2021-04-30 at 23:35.

  4. #54
    Senior Member
    Join Date
    May 2017
    Posts
    773
    Interesting to hear how this goes. Nice to know would be what your environment is. Is the building outside a city, are there other wifi sources in the neighborhood etc.
    SqueezeBoxes: 1x Transporter (Living room) 1x SB2 (shed), 1x Radio (Kitchen), 1x Boom (Dining room), 1x piCorePlayer (jacuzzi), 1x piCorePlayer (Garden) 1x OSMC + Squeezelite (Movie room), 1x Touch (Study 2), few spare unit's (SB2, SB3, Boom, Touch)
    Server: LMS on Pi3B+ 8.1.2 on PcP 7.0.1
    Network: Draytek, Netgear Smart Switch 24p, Ubiquiti PoE, 3x Ubiquity

  5. #55
    Senior Member
    Join Date
    Nov 2007
    Posts
    118
    Quote Originally Posted by edwin2006 View Post
    Interesting to hear how this goes. Nice to know would be what your environment is. Is the building outside a city, are there other wifi sources in the neighborhood etc.
    Some environmental particulars: The main structure is four levels totaling 3,500-4,000 sq. ft., with the maximum interior run dimension being approximately 125 ft. It is not uncommon for a client to be 2-3 floors and 5-6 walls away from the server. No masonry or steel construction, which is a plus in this context (but I will add that one level is partly below-grade, with a cinderblock envelope). The extended exterior roaming zone covers about 2 acres of mixed wooded and open space, with an outbuilding @ 70 ft. from the main structure. The general outside vicinity is moderately congested, but primarily in the 2.4 band with lower-tech traffic. I can detect good signal from five surrounding outside wireless networks besides our own from the property.

    This physical environment is why the property was previously wired for gigabit ethernet when 10/100 fast ethernet and 802.11b were still the standards (the primary distribution trunks to the server have since been upgraded to be 10G-capable). The primary switching equipment is Cisco 350 level quality, and those elements have retained a 10-14 year effective service life. But we have stuck with Asus prosumer-grade routers and wireless components due to the faster obsolescence curves of those elements (and they tend to be upgraded every 3-4 years as newer wireless standards emerge).

    It was a difficult single-point wireless install in years past, and earlier AP and repeater solutions were frankly excessively complicated (including from a security perspective). And the ethernet infrastructure decision has proven a boon for many years, as there is still nothing better for fixed clients (such as SB players). Our TPs and Touches never have dropouts thanks to ethernet.

    Mobile clients were the historic problem, but there were few of them. That has obviously changed with the rise of IoT. The introduction of mesh technologies has eliminated that last obstacle, and we now get excellent signal across the entire property, especially with ethernet backhauls (yet another benefit of that earlier investment). The future is AX, but the wireless tools have dramatically improved in the last four years.

    One tip for others, to reduce primary wireless loads and routing congestion is to embrace independent automation mesh protocols, such as Zigbee and Redlink (Honeywell). Loading down your primary wireless channels with 50 smart light bulbs and ten smart thermostats and sensors is asking for router and bandwidth headaches. These separate proprietary networks remain separate, with the only link to the primary network being a manageable ethernet hub/gateway link.

    As I mentioned, in our instance, we only need to deal with a relative handful of older legacy wireless clients. And I understand that our network infrastructure exceeds the usual residential standards. But IT WORKS in our Asus AX router-driven environment, and that is the takeaway for this conversation.

    If the Asus AX nodes prove to present an obstacle, we will probably still keep them and keep working the problem. The one Touch could probably be run to ethernet. And iPeng playing on an iPad Pro is not a bad substitution for a balky Radio.
    Last edited by sgmlaw; 2021-05-01 at 08:03.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •