Posted: Tue Sep 17, 2019 14:43 Post subject: Wifi connectivity issues on Netgear R8000
I have had quite a lot of trouble getting my WiFi devices, especially my phone, connected to my Netgear R8000 running DD-WRT v3.0-r40559 std (08/06/19). It will say it is connected but be completely unable to reach any IP address, including the router itself. This only happens on WiFi and not on wired connections. Looking at my kernel logs, I am seeing quite a lot of logs that look like this:
Code:
Sep 17 07:37:30 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:31 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:31 latuda kern.warn kernel: CONSOLE: 001097.558 wl0: wlc_bmac_processpmq: skip entry with mc/bc address 7d:d9:5c:b7:ec:0d
Sep 17 07:37:32 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:34 latuda kern.warn kernel: CONSOLE: 001100.031 wl0: wlc_bmac_processpmq: skip entry with mc/bc address 7d:d9:5c:b7:ec:0d
Sep 17 07:37:35 latuda kern.warn kernel: net_ratelimit: 5 callbacks suppressed
Sep 17 07:37:35 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:35 latuda kern.warn kernel: CONSOLE: 001101.350 wl0: wlc_bmac_processpmq: skip entry with mc/bc address 7d:d9:5c:b7:ec:0d
Sep 17 07:37:36 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:37 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:37 latuda kern.warn kernel: CONSOLE: 001103.253 wl0: wlc_bmac_processpmq: skip entry with mc/bc address 7d:d9:5c:b7:ec:0d
Sep 17 07:37:38 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:38 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:38 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:38 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:38 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:38 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:39 latuda kern.warn kernel: CONSOLE: 001104.855 wl0: wlc_bmac_processpmq: skip entry with mc/bc address 7d:d9:5c:b7:ec:0d
Sep 17 07:37:40 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:41 latuda kern.warn kernel: CONSOLE: 001106.904 wl0: wlc_bmac_processpmq: skip entry with mc/bc address 7d:d9:5c:b7:ec:0d
Sep 17 07:37:41 latuda kern.warn kernel: net_ratelimit: 8 callbacks suppressed
Sep 17 07:37:41 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:42 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:43 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:44 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:45 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:46 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:47 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:48 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:49 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:49 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:49 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:49 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:49 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:49 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:52 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:52 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:37:52 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
7d:d9:5c:b7:ec:0d is the MAC address of my phone, so this could well be related. I'm not sure what is causing all of the "received packet on eth2 with own address as source address" messages, possibly something off with the routing setup, but I don't know what. I don't have a lot of complex VLAN setup and it continues to show up even when I disconnect just about everything else, including my phone and the other switches in my network. A Google search for the "skip entry" part of the logs shows that this has also been an issue with the stock firmware on some Netgear devices that was only quite recently fixed (https://community.netgear.com/t5/Business-Wireless/Occasional-wireless-traffic-hang/m-p/1695759). Is it possible the same issue exists in DD WRT, and could we incorporate their fix?
Edit: also possibly relevant, I am seeing a lot of flow ring and rate limit-related logs:
Code:
Sep 17 07:50:07 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:50:08 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:50:09 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:50:10 latuda kern.warn kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Sep 17 07:50:10 latuda kern.warn kernel: dhd_prot_flow_ring_delete: Send Flow Delete Req RING ID 119 for peer 00:51:ed:f6:b2:c4 prio 0 ifindex 0
Sep 17 07:50:10 latuda kern.warn kernel: dhd_prot_flow_ring_delete: Send Flow Delete Req RING ID 126 for peer 00:51:ed:f6:b2:c4 prio 1 ifindex 0
Sep 17 07:50:10 latuda kern.warn kernel: dhd_prot_flow_ring_delete: Send Flow Delete Req RING ID 131 for peer 00:51:ed:f6:b2:c4 prio 3 ifindex 0
Sep 17 07:50:10 latuda kern.warn kernel: dhd_flow_rings_delete_for_peer: ifindex 0
Sep 17 07:50:10 latuda kern.warn kernel: dhd_prot_flow_ring_delete: Send Flow Delete Req RING ID 127 for peer b8:27:eb:57:15:6f prio 3 ifindex 0
Sep 17 07:50:10 latuda kern.warn kernel: dhd_prot_flow_ring_delete: Send Flow Delete Req RING ID 130 for peer b8:27:eb:57:15:6f prio 0 ifindex 0
Sep 17 07:50:10 latuda kern.warn kernel: dhd_prot_flow_ring_delete_response_process: Flow Delete Response status = 0
Sep 17 07:50:10 latuda kern.warn kernel: dhd_prot_flow_ring_delete_response_process: Flow Delete Response status = 0
Sep 17 07:50:10 latuda kern.warn kernel: dhd_prot_flow_ring_delete_response_process: Flow Delete Response status = 0
Sep 17 07:50:10 latuda kern.warn kernel: dhd_prot_flow_ring_delete_response_process: Flow Delete Response status = 0
Sep 17 07:50:10 latuda kern.warn kernel: dhd_prot_flow_ring_delete_response_process: Flow Delete Response status = 0
Sep 17 07:50:10 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:50:10 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:50:10 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:50:11 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:50:11 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:50:11 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:50:12 latuda kern.warn kernel: net_ratelimit: 1 callbacks suppressed
Sep 17 07:50:12 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:50:12 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:50:12 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:50:13 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:50:13 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:50:13 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:50:13 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:50:14 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:50:14 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:50:15 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Sep 17 07:50:18 latuda kern.warn kernel: net_ratelimit: 11 callbacks suppressed
Sep 17 07:50:18 latuda kern.warn kernel: br0: received packet on eth2 with own address as source address
Joined: 08 May 2018 Posts: 14224 Location: Texas, USA
Posted: Tue Sep 17, 2019 17:25 Post subject:
The received packet own address messages are NAT loopback, if I'm not mistaken. I have the other error messages as well, but everything seems to connect to my R7000P just fine on the 5GHz band. Android or iPhone?
The received packet own address messages are NAT loopback, if I'm not mistaken. I have the other error messages as well, but everything seems to connect to my R7000P just fine on the 5GHz band. Android or iPhone?
My phone is Android. Just upgraded to Android 10, but this problem was happening before. I have both of the 5GHz and the 2.4GHz on the same SSID, so it should be able to hop between them, I'm not sure if this is just a problem on one frequency or the other. I don't know why I would be getting NAT loopback. I do have a couple of ports open to outside, but I don't think any of them are getting that much traffic.
