Yes,
But to it seems that the phy's is using US settings?
I'm currently using the following build:
OpenWrt 19.07-SNAPSHOT r10784-e33a123140
I'm running into a strange problem with my router, for some reason this only happens when I'm accessing xfinity website after logging in to view the bandwidth counter.
root@OpenWrt:~# logread -f
Fri Dec 27 18:40:25 2019 kern.err kernel: [ 193.555580] ipq806x-gmac-dwmac 37400000.ethernet eth1: len 1706 larger than size (1536)
Fri Dec 27 18:40:26 2019 kern.err kernel: [ 193.795624] ipq806x-gmac-dwmac 37400000.ethernet eth1: len 1706 larger than size (1536)
Fri Dec 27 18:40:26 2019 kern.err kernel: [ 194.095959] ipq806x-gmac-dwmac 37400000.ethernet eth1: len 1706 larger than size (1536)
Fri Dec 27 18:40:27 2019 kern.err kernel: [ 194.696021] ipq806x-gmac-dwmac 37400000.ethernet eth1: len 1706 larger than size (1536)
Fri Dec 27 18:40:38 2019 kern.alert kernel: [ 205.816274] Unable to handle kernel paging request at virtual address adceaffc
Fri Dec 27 18:40:38 2019 kern.alert kernel: [ 205.816363] pgd = c0204000
Fri Dec 27 18:40:38 2019 kern.alert kernel: [ 205.822435] [adceaffc] *pgd=00000000
Fri Dec 27 18:40:38 2019 kern.emerg kernel: [ 205.825132] Internal error: Oops: 5 [#1] SMP ARM
I assume this is probably because I have Jumbo Packet enabled on my computer that I'm accessing it from, but I haven't seen this behavior from any other website or program, so it's a little strange to me.
Anyone have any tips? Should I update to latest and try again?
Just installed the latest kernel 4.19 build and have to say it seems pretty solid. I am currently running my r7800 strictly as an AP. Are there any configuration/services that I would want to leverage since I don't need all the router related services/functionality? (e.g. should I be disabling things like the firewall etc since I'm handling that upstream in my network?)
And if there is a better forum for finding this information - feel free to point me to it!
thanks,
For Jumbo frames to be truly efficient you need to enable it on every device you're using, otherwise you might just aswell turn it off.
1 Like
Good discussion in the r7800 exploration and r7800 performance threads about optimizing performance. Hnyman already has a clean limited number of programs. My two r7800 APs running hnyman 4.19 have all the services in the service drop down turned off and ipv4 DHCP turned off (hardwired to the router via cat 6A cable). Turning off unused low resource programs (firewall) is going to have negligible effect on performance.
See here for CPU tweaks: Netgear R7800 exploration (IPQ8065, QCA9984) - #1929 by ACwifidude
master-r11827-f8424b1b26-20191228-ct
The recent ubus version upgrade two days ago caused a bug for system log, which bug has now been fixed. However, the change also caused some services not to start, e.g. collectd (= LuCI statistics) and nlbwmon. ldir figured out that those fail where the procd init file has a "nice" parameter definition:
I have implemented that workaround in my own build.
Hopefully the underlying bug (in ubus or procd) gets fixed, but until then the workaround is to have the nice definition before the command definition in the procd init file of a service.
EDIT:
seems to be fixed in master. (it was a libubox blobmsg handling error)
master-r11829-e3e939d8e6-20191228-ct
2 Likes
Jumbo frames is enabled because I have a switch between my computer and my homelab, but I don't really need it anywhere else.
This isn't really a problem of efficiency... it's actually crashing the router, so I'm wondering if this is expected to happen or if it's a bug.
Edit: If I understand correctly, it should retry until the frames fit within the 1536, but in this scenario it somehow pushes 1.7KB
Spotted the latest build on the site hnyman, great work as always, thanks very much.
The problem with jumbo frames is a known bug with the ipq806x target, for which I understand a fix is now in master. See this post for a possible workaround.
1 Like
If i want to try the latest master build and if i'm now on vanilla, do i still have to TFTP flash the standard 18.06.5 image before flashing the latest build?
No idea what you mean by "vanilla".
I think that if you are running the Netgear OEM firmware, you might need to use the TFTP to flash the new OpenWrt factory image. (But some people said recently that they flashed OpenWrt directly from Netgear firmware, so I am not sure)
But there is no reason to flash anything 18.06.x
Just flash either the 19.07 build or the master build.
2 Likes
Thank you! I have now installed the current master build. A problem i have now though is that the router's wifi networks are visible but not connectable. 
The settings are the same now as in the vanilla firmware. Any idea what this could be?
No idea. And still no idea what you mean by "vanilla firmware".
There are no wifi-specific special changes in my build.
Did you sysupgrade or tftp? Did you keep your prior config file or did you reset your settings?
Wifi by default is turned off when you first get started. I’d configure the router with a hardwired computer. If it were me with a major upgrade I would reset the settings to the factory default (system drop down / backup firmware option). After it restarted I’d put everything in fresh. Enable the services and wifi settings you desire and you should be good to go.
I originally flashed your build directly over stock firmware about a year ago. Worked perfectly fine
If anyone would run into significantly larger image problem here is the solution:
@hnayman does it make sense to disable CONFIG_DEBUG in your build as well?
Running latest hnyman 19.07 build I'm getting occasional chatter across the network. The link between router & modem is flooded, slowing internet access. Eventually connection breaks with loss of DNS.
Router log is completely filled with:
daemon.notice netifd: wan6 (1879): Command failed: Request timed out
Appreciate this may not be specific to hnyman's build, I'm just looking for any help/hints what the cause is? Thanks.
I don't really have such packages in my build that would not use the normal binary stripping. And so the setting does not cause much size impact. (Samba disabling that stripping functionality and causing binary size growth sounds strange.)
Like jow explained to you in the samba thread, the normal stripping produces the small stripped binary for the firmware image, while the staging dir contains a full debug-enabled non-stripped binary for debugging with gdbserver.
If you add such problematic packages to my build config and you are not actively debugging things, feel free to disable that setting in your own builds.
1 Like
Weird one, have you messed with the IPV6 settings? wan6 is the alias for the IPV6 interface.
Its because of this bug and had no time to investigate this further: https://github.com/openwrt/packages/issues/10783