Orbi WiFi 7 RBE973
Reply

Re: R7800 reboots when Pinebook Pro uses the Wifi in AP mode

ericzolf
Aspirant

R7800 reboots when Pinebook Pro uses the Wifi in AP mode

Hi,

I recently got a PineBook Pro (aka PBP, from pine64.org) and I have now the issue that each time the PBP uses the Wifi a bit more heavily, the R7800 chokes and reboots.

 

I am ready to admit that the PBP is doing something strange and I reported the issue also there the issue https://forum.pine64.org/showthread.php?tid=18739 but:

  1. this hints at a denial of service weakness in the R7800 which could be used for malign purposes
  2. I'd appreciate some help to debug the issue from the R7800 side, where the logs are absolutely useless, and gone after a reboot. I've discovered https://nighthawk.home/debug.htm but missing documentation on how to use it.

Thanks, Eric

Some more information: I have two R7800 both configured very similarly as AP against the same 3rd party router, latest firmware, and both showing the same behavior. Depending which Wifi is used by the PBP, the corresponding R7800 reboots.

Message 1 of 15
plemans
Guru

Re: R7800 reboots when Pinebook Pro uses the Wifi in AP mode

does it matter if its connected to the 2.4ghz or the 5ghz?

Message 2 of 15
Kitsap
Master

Re: R7800 reboots when Pinebook Pro uses the Wifi in AP mode

One option would be to consider the Voxel firmware for your R7800s.  Be sure and review the Readme file linked in the banner.

 

https://www.voxel-firmware.com/Downloads/Voxel/html/index.html

 

 

Message 3 of 15
ericzolf
Aspirant

Re: R7800 reboots when Pinebook Pro uses the Wifi in AP mode


@plemans wrote:

does it matter if its connected to the 2.4ghz or the 5ghz?


No, it doesn't. My normal configuration is with "Smart Connect", so both under the same name, and the issue appeared. I split them for troubleshooting, but both cause the reboot.

Message 4 of 15
ericzolf
Aspirant

Re: R7800 reboots when Pinebook Pro uses the Wifi in AP mode

 
@Kitsap wrote:

One option would be to consider the Voxel firmware for your R7800s.  Be sure and review the Readme file linked in the banner.

 

https://www.voxel-firmware.com/Downloads/Voxel/html/index.html

I didn't know about the Voxel firmware, but I was considering OpenWrt if everything else breaks. What would be the advantages/disadvantages of both, if we arrive to this stage? From what I could find, Voxel, like the stock firmware, is also based on OpenWrt.

The nearest to a comparison I could find is https://www.snbforums.com/threads/voxel-firmware.50141/post-587447 and it's  already more than 3 years old, so possibly/probably outdated.

Message 5 of 15
Kitsap
Master

Re: R7800 reboots when Pinebook Pro uses the Wifi in AP mode


@ericzolf wrote:
 
@Kitsap wrote:

One option would be to consider the Voxel firmware for your R7800s.  Be sure and review the Readme file linked in the banner.

 

https://www.voxel-firmware.com/Downloads/Voxel/html/index.html

I didn't know about the Voxel firmware, but I was considering OpenWrt if everything else breaks. What would be the advantages/disadvantages of both, if we arrive to this stage? From what I could find, Voxel, like the stock firmware, is also based on OpenWrt.

The nearest to a comparison I could find is https://www.snbforums.com/threads/voxel-firmware.50141/post-587447 and it's  already more than 3 years old, so possibly/probably outdated.


My only experience is with Voxel, none with OpenWrt.  I ran Voxel on my R7800 for three years before I put it in backup status.  Now on my R9000 it has performed well for the last couple of years.  Both routers were obtained second hand.

 

Voxel is based on stock firmware with many of the Netgear imposed limitations removed.  This has a more substantial impact on the R7800 than on the R9000.  I obtained the R9000 because it has an optical SPF 10Gb WAN port.

 

Voxel is easy to get into or get out of.  However, he is a one man show.  If something happens to him I expect the project to disappear.  I am on board as long as it is available.

 

Most users that install Voxel firmware on their router never look back.

 

 

 

 

 

 

 

 

Message 6 of 15
FURRYe38
Guru

Re: R7800 reboots when Pinebook Pro uses the Wifi in AP mode

Voxels WEB GUI is mostly same or similar to NG stock FW. He makes some GUI changes and mostly cosmetic. 

 

Voxels mostly keeps the backend FW packages more up to date with in the FW and also as more support for some features that NG doesn't support.

 

I think other draw backs would be that features like Amor and Circle may not work at all with his FW loaded. Not sure if Nighthawk app will either. 

 

I did load his FW on my R7800 a few years back. With the additional WEB GUI diagnostic plug-in that was supported back then, was really nice. Seem to run well though I didn't test it out for a long time. Just wanted to see if I could get it loaded on and with the plug-in that was brought up. I have data at home that I still have somewhere's regarding that. 

 

Think in long term, Voxels would be the better option, if your system is not in warranty and this is what you want to keep for a while longer, give it a try. You can always come back to NG stock. 

 

 

Message 7 of 15
plemans
Guru

Re: R7800 reboots when Pinebook Pro uses the Wifi in AP mode

could always toss voxel's on one of them and see if the problem replicates using 3rd party firmware. 

Message 8 of 15
ericzolf
Aspirant

Re: R7800 reboots when Pinebook Pro uses the Wifi in AP mode

OK, let me try this (might take a while) and see if it helps, or if at least I can get more information about the issue.

Message 9 of 15
Kitsap
Master

Re: R7800 reboots when Pinebook Pro uses the Wifi in AP mode


@FURRYe38 wrote:

 

I think other draw backs would be that features like Amor and Circle may not work at all with his FW loaded. Not sure if Nighthawk app will either. 

 


The Nighthawk mobile application works fine on my R9000 with the Voxel firmware.

Message 10 of 15
ericzolf
Aspirant

Re: R7800 reboots when Pinebook Pro uses the Wifi in AP mode

Hi, so I found at last the time to burn Voxel's firmware and it didn't change anything to my problem, exactly the same behavior once my PineBook Pro starts to use the Wifi, reboot without notice of warning...

Does this new firmware have secret powers for debugging?

Message 11 of 15
Kitsap
Master

Re: R7800 reboots when Pinebook Pro uses the Wifi in AP mode


@ericzolf wrote:

Hi, so I found at last the time to burn Voxel's firmware and it didn't change anything to my problem, exactly the same behavior once my PineBook Pro starts to use the Wifi, reboot without notice of warning...

Does this new firmware have secret powers for debugging?


No special powers.  There is a debug menu for both stock and Voxel firmware.   It is here:  http://192.168.1.1/debug.htm.  If your IP address for the router is different you will have to adjust the address.  I note a debug log capture you could experiment with.  Also you could post your issue in the Netgear section over in Small Net Builders forum.  Lots of experience there with the R7800.

https://www.snbforums.com/forums/netgear-ac-wireless-wi-fi-5.53/

 

 

 

Message 12 of 15
ericzolf
Aspirant

Re: R7800 reboots when Pinebook Pro uses the Wifi in AP mode

I knew about this page but couldn't find any documentation on how to use it, and what is the format of the output, and how to use it.

Message 13 of 15
ericzolf
Aspirant

Re: R7800 reboots when Pinebook Pro uses the Wifi in AP mode

After having setup SSH, I'm now able at least to access `dmesg` and the result is:

[ 0.000000] Inst RSSI value of node-96:16:68:1f:58:96: 18
[ 0.000000] Inst RSSI value of node-96:16:68:
[ 0.000000] 58:96: 18
[ 0.000000] Inst RSSI value of node-96:16:
[ 0.000000] 58:96: 18
[ 0.000000] [wifi1] FWLOG: [1410228] RATE: ChainMask 1, peer_mac 1e:9b, phymode 5, ni_flags 0x00041006, vht_mcs_set 0x0000, ht_mcs_set 0x00ff, legacy_rate_set 0x1584d7
[ 0.000000] [wifi1] FWLOG: [1410263] WAL_DBGID_SECURITY_UCAST_KEY_SET ( 0x1e9b, 0x0 )
[ 0.000000] [wifi1] FWLOG: [1410263] WAL_DBGID_SECURITY_ENCR_EN (
[ 0.000000] )
[ 0.000000] [wifi1]
[ 0.000000] 0x4492cc )
[ 0.000000] [wifi1] FWLOG: [1410430] WAL_DBGID_TX_BA_SETUP (
[ 0.000000] 0x4492cc, 0x1e9b0006
[ 0.000000] , 0x2, 0x20, 0x1 )
[ 0.000000] [wifi1] FWLOG: [1410431]
[ 0.000000] RATE: ChainMask 1, peer_mac 1e:9b, phymode 5, ni_flags 0x00041006, vht_mcs_set 0x0000, ht_mcs_set 0x00ff, legacy_rate_set 0x1585cf
[ 0.000000] [wifi1] FWLOG: [1410511] WAL_DBGID_TX_BA_SETUP (
[ 0.000000] 0x4492cc, 0x1e9b0000
[ 0.000000] , 0x0, 0x20, 0x1 )
[ 0.000000] Inst RSSI value of node-84:cf:bf:8f:45:50: 45
[ 0.000000] Inst RSSI value of node-84:cf:bf:8f:45:50: 45
[ 0.000000] Inst RSSI value of node-84:cf:bf:8f:45:50: 45
[ 0.000000] Inst RSSI value of node-84:cf:bf:8f:45:50: 45
[ 0.000000] Inst RSSI value of node-96:16:68:1f:58:96: 18
[ 0.000000] Inst RSSI value of node-96:16:68:1f:58:96: 18
[ 0.000000] Inst RSSI value of node-84:cf:bf:8f:45:50: 42
[ 0.000000] Inst RSSI value of node-84:cf:bf:8f:45:50: 42
[ 0.000000] Inst RSSI value of node-96:16:68:1f:58:96: 18
[ 0.000000] Inst RSSI value of node-96:16:68:1f:58:96: 18
[ 0.000000] Inst RSSI value of node-84:cf:bf:8f:45:50: 41
[ 0.000000] Inst RSSI value of node-84:cf:bf:8f:45:50: 42
[ 0.000000] Inst RSSI value of node-96:16:68:1f:58:96: 18
[ 0.000000] Inst RSSI value of node-96:16:68:1f:58:96: 18
[ 0.000000] ASSERT: ecm_nss_ipv4_ip_process:884:Not IPv4 address: dead:beef:dead:beef:dead:beef:b63f:0896
client_loop: send disconnect: Broken pipe

 

 

the last IPv6 address is the one of my PineBook Pro and is the last message before break-down.

It sounds to me almost like the PBP sends an IPv6 address where it should send an IPv4 one, and the router doesn't catch it properly (possibly related to the NSS driver, which is quite specific AFAIU). Does it make sense and, more importantly, how to go further?

Message 14 of 15
ericzolf
Aspirant

Re: R7800 reboots when Pinebook Pro uses the Wifi in AP mode

Fair enough, I'm also outside of my waters already since quite a while. As a side remark, I got the confirmation that it was a kernel/driver issue, a longer message appeared after another test:

 

[ 0.000000] ------------[ cut here ]------------
[ 0.000000] Kernel BUG at bfc0c610 [verbose debug info unavailable]
[ 0.000000] Internal error: Oops - BUG: 0 [#1] SMP ARM
[ 0.000000] Modules linked in:
[ 0.000000] mtdoops(O) NetUSB(P)
[ 0.000000] ecm(O) smart_antenna(PO)
[ 0.000000] umac(O) ath_dev(PO) hst_tx99(PO)
[ 0.000000] ath_spectral(PO) ath_dfs(PO)
[ 0.000000] ort(O) ip_set_hash_mac(O) ip_set_hash_ip(O) ip_set_bitmap_port(O) ip_set_bitmap_ipmac(O) ip_set_bitmap_ip(O) ip_set(O) ip6t_rt ip6t_hbh ip6t_mh ip6t_frag ip6t_eui64 ip6t_ah ip6table_raw ip6_queue nf_conntrack_ipv6 nf_defrag_ipv6 ebt_snat ebt_dnat ebt_arpreply ebt_arp ebt_vlan ebt_stp ebt_pkttype ebt_limit ebt_among ebt_802_3 ebtable_nat nf_nat_ftp(O) nf_conntrack_ftp(O) ipt_urlBlock(O) ipt_TRIGGER(O) ipt_spiDoS(O) ipt_spiadvDoS(O) nf_nat_pptp(O) nf_conntrack_pptp(O) pptp(O) l2tp(O) ip6t_CONE(PO) xt_RAWNAT(O) ipt_dnshijack(O) nf_nat_dnirtsp(O) nf_conntrack_dnirtsp(O) nf_nat_dnih323(O) nf_conntrack_dnih323(O) ipt_CONENAT(PO) ipt_NETGEAR_REJECT(O) xt_TEE ip6t_rpfilter ipt_rpfilter nf_nat_tftp nf_conntrack_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_proto_gre(O) nf_conntrack_proto_gre(O) nf_nat_amanda nf_conntrack_amanda nf_conntrack_broadcast nf_nat_irc nf_conntrack_irc xt_HL xt_hl xt_ecn ipt_ECN xt_CLASSIFY xt_time xt_tcpmss xt_statistic xt_layer7 xt_quota xt_pkttype xt_physdev xt_owner compat_xtables(O) nf_nat_STARCRAFT(PO) ipt_NETMAP xt_recent xt_helper xt_connbytes qca_mcs(O) xt_CT ehci_hcd dwc3 sd_mod xt_LOG xt_comment msdos bonding dni_qos(O) ifb qca_nss_qdisc(O) qca_nss_crypto_tool(O) qca_nss_crypto(O) qca_nss_drv(O) pppoe l2tp_netlink l2tp_core dni_enet(PO) qca_nss_gmac(O) pppox ppp_async ppp_generic slhc vfat fat ntfs ext4 jbd2 mbcache cifs dm_crypt dm_mirror dm_region_hash dm_log dm_mod nls_iso8859_1 nls_cp437 crc_ccitt exportfs clbr(PO) shortcut_fe_drv(O) qca_ssdk(O) shortcut_fe_ipv6(O) shortcut_fe(O) md5 md4 hmac ecb des_generic arc4 [last unloaded: ecm]
[ 0.000000] CPU: 0 Tainted: P O (3.4.103 #1)
[ 0.000000] PC is at ecm_nss_ipv4_connection_sync_many_callback+0x17c/0x5f4 [ecm]
[ 0.000000] LR is at console_unlock+0x388/0x434
[ 0.000000] pc : [<bfc0c610>] lr : [<c006f0e4>] psr: 20000113
[ 0.000000] sp : c08058e8 ip : 00000000 fp : c0805abc
[ 0.000000] r10: d6df7000 r9 : 00000000 r8 : ddf16800
[ 0.000000] r7 : d819212e r6 : 00000800 r5 : d8192134 r4 : d6df7000
[ 0.000000] r3 : c08003c4 r2 : 00000001 r1 : 00555000 r0 : 00000064
[ 0.000000] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
[ 0.000000] Control: 10c5787d Table: 5b60c06a DAC: 00000015

[ 0.000000] LR: 0xc006f064:
[ 0.000000] f064 ea000001 e1a01004 ebfffcf1 e121f00a eaffff4d e5972004 e3a03000 e5873014
[ 0.000000] f084 e1520003 15873004 f57ff05f e3a03801 e1982f9f e6522f13 e1881f92 e3310000
[ 0.000000] f0a4 1afffffa f57ff04f e320f004 e59f00d4 eb00a331 e1a00008 eb10dd87 e5973020

[... etc ...]

 

Message 15 of 15
Top Contributors
Discussion stats
  • 14 replies
  • 1592 views
  • 0 kudos
  • 4 in conversation
Announcements

Orbi 770 Series