Joined: 21 Jan 2017 Posts: 1782 Location: Illinois Moderator
Posted: Fri Jul 20, 2018 21:22 Post subject:
@Kong- You need to revert the compat wireless on the R9000 build like you did for the R7800 and EA8500. Build 35945 won't allow iOS/bonjour to work after the timeout of ~5min. Not sure if you made the change in the following build on 5-26-18. But I'm not going to try it based on the feedback from Labo and others where wifi drops out.
Switching back to BS 35034 until someone else throws out a "better" build to use.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Fri Jul 20, 2018 21:53 Post subject:
msoengineer wrote:
@Kong- You need to revert the compat wireless on the R9000 build like you did for the R7800 and EA8500. Build 35945 won't allow iOS/bonjour to work after the timeout of ~5min. Not sure if you made the change in the following build on 5-26-18. But I'm not going to try it based on the feedback from Labo and others where wifi drops out.
Switching back to BS 35034 until someone else throws out a "better" build to use.
So I cut and pasted "multicast_to_unicast=1" w/o quotes into both radio's custom cfg box and still no dice...
I tried reverting the R9000 all the way back to BS 34886 and still no dice...
So I cut and pasted "multicast_to_unicast=1" w/o quotes into both radio's custom cfg box and still no dice...
I tried reverting the R9000 all the way back to BS 34886 and still no dice...
Any other thoughts?
I replaced the wife's cranky Ipad with a detachable HP Chromebook. _________________ Segment 1 XR700 10Gb LAN, 1Gb WAN ISP BS
Wired AP 1 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 2 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 3 Unifi Wifi 6 LR US 1Gb LAN
Syslog Services Asustor 7110T NAS 10GB
NetGear XS716T 10GB Switch
download1.dd-wrt.com/dd-wrtv2/downloads/betas/ (Brain Slayer)
YAMon https://usage-monitoring.com/index.php
Joined: 21 Jan 2017 Posts: 1782 Location: Illinois Moderator
Posted: Sat Jul 21, 2018 1:02 Post subject:
tatsuya46 wrote:
sub r35927 and still having it, then r9000 is having a separate issue
OK, I knew something didn't pass the sniff test so I went back and did a factory reset when I re-flashed 36330.
I then put in the "multicast_to_unicast=1" (with no quotes) in the wireless security custom config window and Viola....I now have working bonjour again. This means my Kodi and HP printer work again!
So, now I'll keep you guys posted on how 36330 runs.... it's been up for 2hrs so far and seems to be just fine. That said, I do reboot my router every night to make sure things don't linger.
Thank You Tatsuya!
@Kong-guess the workaround will have to do until a permanent fix is in place. No need to revert the compat wireless for now...
Just curious has anyone been experiencing full hangs after about a week or so of uptime?
I have been running v3.0-r35452 std (03/20/1 until a few weeks ago when the X10 became completely unresponsive. I did a hard reboot and it worked fine for another week so and hung again. I upgraded to v3.0-r37961 std (12/12/1 and it seemed to be working fine until it hung again. I took a look though the logs but it seems like the UI only shows from the current startup.
Is there way I can enable log capture from the previous reboot to help troubleshoot this issue?
Is there a recommended software build that I should be using instead? Thanks.
I just switched to Voxel... the UI is pure aids (since it's default netgears), but the reliability and the problem free connections with all my mobile devices and wifi network adapters is very nice for a change.
My one big complaint is there's not much adjustability with the firewall/nat filtering and when you select channel 100(DFS), it will automatically switch channels when radar is detected and it always defaults to channel 36 which is really crap compared to the usual channels 149, 153, 157, 161. DD-WRT just stays on channel 100 until I manually change it. But it's still worth it at the moment because I am not constantly trying to fix something.
Hopefully a good build will come about and I will definitely switch back, but after the no update via web GUI issue became widespread, and the multi cast to unicast "fix" thing, IMO DD-WRT for the R9000 just went downhill.
Joined: 21 Jan 2017 Posts: 1782 Location: Illinois Moderator
Posted: Thu Dec 27, 2018 14:55 Post subject:
yodog wrote:
Going to try the new Kong build 12/26. Funny, Brainslayer also released a version on the same date.
Which netgear-to-ddwrt firmware file to choose if upgrading from the netgear firmware? hmmm...
Always use a Kong build on Netgear routers which he builds on/for for first time flash. Use the .IMG filename for stock to dd-wrt. Anything already running a dd-wrt firmware you flash a .BIN filename.
Going to try the new Kong build 12/26. Funny, Brainslayer also released a version on the same date.
Which netgear-to-ddwrt firmware file to choose if upgrading from the netgear firmware? hmmm...
Always use a Kong build on Netgear routers which he builds on/for. For first time flash use the .IMG filename for anything already running a dd-wrt firmware you flash a .BIN filename.
Ok the route of Kong it is then! Voxels firmware is giving me weird problems with my Philips Hue motion sensors. I hope this Kong version is fast and stable!
Posted: Sun Jan 06, 2019 5:09 Post subject: Frame Compression on Netgear X10 (R9000) on Kong build
Hello, there I have a question about frame compression on my Netgear X10 AKA R9000. I've looked through the WIki and generally around the internet but I can't find anything on Frame Compression. My options for frame compression are Disabled, LZO, LZ4, LZMA. Out of those options what would be the best setting for general streaming and gaming? Out of the options is one compression algorithm better than the rest? The CPU on the router is powerful so I don't think the increased CPU work would be a problem.
Thanks in Advance
PS: If someone could update the QCA wireless settings wiki with this information that would be helpful.
Joined: 21 Jan 2017 Posts: 1782 Location: Illinois Moderator
Posted: Sun Jan 06, 2019 5:59 Post subject: Re: Frame Compression on Netgear X10 (R9000) on Kong build
Johnnyde94 wrote:
Hello, there I have a question about frame compression on my Netgear X10 AKA R9000. I've looked through the WIki and generally around the internet but I can't find anything on Frame Compression. My options for frame compression are Disabled, LZO, LZ4, LZMA. Out of those options what would be the best setting for general streaming and gaming? Out of the options is one compression algorithm better than the rest? The CPU on the router is powerful so I don't think the increased CPU work would be a problem.
Thanks in Advance
PS: If someone could update the QCA wireless settings wiki with this information that would be helpful.
to get the lowest possible latency:
Setup>Networking>Port Setup section and change all of the
TX Queue Length to 2 from 1000. This will help reduce a bunch of latency.
For more ambiguous info about frame compression see the link below and look at slide 54... TL/DL Seems like LZMA is the way to go, but if it's not working, why bother enabling it. Both the Router and device must support it....likely not going to happen. This seems like a future 802.11xx implementation to help with congested wifi spectrum, and LTE/cellular too...
Joined: 21 Jan 2017 Posts: 1782 Location: Illinois Moderator
Posted: Tue Jun 04, 2019 18:33 Post subject: Messing around with Cores and IRQ's
I've been wanting to play around with moving around some IRQ's to different CPU cores for testing latency/throughput purposes.
Here are my findings so far...
There is no ETH0 interface. It appears BS has split up the ETH0 interface to "load balance" across all 4 cores of the CPU. The R9000 has 2 switches inside and the WAN is VLAN'd to the remaining ports...based on BS's comments back around page 5 and 8 of this particular thread. You'll see the funky labeling for the TX and RX ports...