NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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 t...
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.
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?
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/
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.
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 pipethe 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?
