Nothing helps to improve the spikes in bufferbloat except QoS with decreasing speed. Will try Tatsuyta46 suggestions latter
P.S. After so many changes in configuration my router lost WAN first and stuck then and i was not able to reset and recover it and will try to recover from TFTP flash. Never happens to me before but looks like nvr failure _________________ Netgear R7800
So what's the current stability of DD-WRT for R7800 comparing to stock? I can see the new test versions like 3.18 (http://www.desipro.de/ddwrt/K3-AC-IPQ806X/Test-3.18/).
The reason I'm asking is that I need the most stable and reliable setup for use as my whole home is going to be home automated powered on 2.4GHz wireless.
I like the DD-WRT features but not sure if I can rely on it as much as on stock (currently the Voxel's firmware installed).
So what's the current stability of DD-WRT for R7800 comparing to stock? I can see the new test versions like 3.18 (http://www.desipro.de/ddwrt/K3-AC-IPQ806X/Test-3.18/).
The reason I'm asking is that I need the most stable and reliable setup for use as my whole home is going to be home automated powered on 2.4GHz wireless.
I like the DD-WRT features but not sure if I can rely on it as much as on stock (currently the Voxel's firmware installed).
Apologies if this isn't the correct place to ask, but as I'm running r37495M with the 3.18 kernel at the moment it seemed better to ask in this thread than the general forum. I've been trying to get ipset working, but haven't managed to get a build environment working to compile xt_set.ko and ipset, I don't think my Linux skills are up to the task. Plus AFAIK the included dnsmasq doesn't support ipset, so not sure if I can just replace it with the dnsmasq-full from Entware without losing anything.
I tried installing ipset from Kong's repository as I'd read that it included the xt_set.ko module, but it looks like it's compiled for the 4.4 kernel.
Just wondered if anyone has had any success doing this on the R7800 using Kong's builds? Might try a BS build later to see if it's included but Kong's builds have been good to me so far.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Tue Nov 06, 2018 23:45 Post subject:
well k4.19 is the new LTS kernel.. are we going to try it and magically hope whatevers fucked so far is fixed in it? _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
I have a new problem with ISP DHCP after cable modem upgrade from arris sb6183 to sb8200 docsys 3.1.
When i resetting the power on cable modem and r7800 ( kong 36175) at the same time i am not receiving Gateway IP and internet IP from ISP just 0.0.0.0.
If i am connecting computer directly to modem then i have IP and Internet right away on computer and i can connect the router to modem back and everything is working. What a mess!!!
The old arris sb6183 works fine for years. I did install the Voxel on r7800 and it works fine with sb8200 after simultaneous reset.
What do you think? Any ideas?
I tested two different dd-wrt routers(r7800 and wrt1900ac) with Kong and BS builds with 3 different cable modems from Arris, Netgear and Moto and still have the same result with no IP after router and modem simultaneous reset.
As long i switched back to stock Netgear firmware my router was able to successfully pick up WAN IP after router and modem simultaneous reset.
I know from my previous experience that submitting ticket will not help.
Dear Kong, can you check this annoying issue? _________________ Netgear R7800
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Fri Nov 09, 2018 1:52 Post subject:
tatsuya46 wrote:
well k4.19 is the new LTS kernel.. are we going to try it and magically hope whatevers fucked so far is fixed in it?
seems k3.18 finally went EOL nearly a year after original date.. been almost a month now with no updates on kernel.org so what does that mean for us and ipq qos? will it be manually maintained till/if k4.x is fixed for ipq or are we going to get k4 forced upon us or..? _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
well k4.19 is the new LTS kernel.. are we going to try it and magically hope whatevers fucked so far is fixed in it?
seems k3.18 finally went EOL nearly a year after original date.. been almost a month now with no updates on kernel.org so what does that mean for us and ipq qos? will it be manually maintained till/if k4.x is fixed for ipq or are we going to get k4 forced upon us or..?
I tested two different dd-wrt routers(r7800 and wrt1900ac) with Kong and BS builds with 3 different cable modems from Arris, Netgear and Moto and still have the same result with no IP after router and modem simultaneous reset.
As long i switched back to stock Netgear firmware my router was able to successfully pick up WAN IP after router and modem simultaneous reset.
I know from my previous experience that submitting ticket will not help.
Dear Kong, can you check this annoying issue?
I have a similar problem with R7000 and R7800 using various different versions of Kong for the past several years. If I reboot from Web UI or telnet/ssh CLI, afterwards the router cannot get a WAN IP. Similarly, when I update the firmware, the forced reboot at the end will cause the same problem. If I reset to factory defaults, then I can get a WAN IP again - but I have to redo all my configurations.
On the other hand, if I do a hard reboot (push the physical power button on the router or pull the power plug), then I have absolutely no problem getting a WAN IP after powering up again.
So for me, there's something funny with a soft reboot.
Joined: 17 Jan 2018 Posts: 64 Location: Georgia, USA
Posted: Mon Nov 12, 2018 21:22 Post subject:
totalfly wrote:
I have a similar problem with R7000 and R7800 using various different versions of Kong for the past several years. If I reboot from Web UI or telnet/ssh CLI, afterwards the router cannot get a WAN IP. Similarly, when I update the firmware, the forced reboot at the end will cause the same problem. If I reset to factory defaults, then I can get a WAN IP again - but I have to redo all my configurations.
On the other hand, if I do a hard reboot (push the physical power button on the router or pull the power plug), then I have absolutely no problem getting a WAN IP after powering up again.
So for me, there's something funny with a soft reboot.
I have had the same issue with all the builds I have used (Kong) for the past several months. If I reboot from the web GUI I lose my network time settings. The NTP does not connect and I get error messages in syslog. This causes my VPN client to fail with the loss of internet to those devices routing through the VPN.
If I power cycle the router the NTP connects and all is good to go.
My other option is to go to the "Setup/Basic Setup" tab and hit "Apply Settings". The NTP will then connect and all is good.
I would like to schedule a weekly reboot under the "Administration / Keep Alive" tab but it causes the router to lose its' NTP.
Soft reboot is definitely flakey for me. _________________ R7800 r53339 std (08/01/23)
Private network on bridge br0 = eth1 (vlan 1) + wlan0 + wlan1.
Guest network on bridge br1 = eth1.4 (vlan 4) + VAPs (wlan0.1 + wlan1.1) for IOT devices
(Roku's, Amazon Echos, smart switches, etc.) and guest.
Noob still finding my way.
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 vlan 1 set ports "1 2 6"
swconfig dev switch0 vlan 4 set ports "3 4 6t"
swconfig dev switch0 set apply
vconfig add eth1 4
brctl addif br1 eth1.4
ifconfig eth1.4 up
