The phone which I used to look at and turn the cameras off is connected to the R8000 when I’m at home, or LTE when I’m out. I can manage the cameras from the surface laptop connected to the WRT1900ac as well though.
Joined: 08 May 2018 Posts: 14223 Location: Texas, USA
Posted: Sat Dec 11, 2021 17:11 Post subject:
rtbrjason wrote:
The phone which I used to look at and turn the cameras off is connected to the R8000 when I’m at home, or LTE when I’m out. I can manage the cameras from the surface laptop connected to the WRT1900ac as well though.
Turn off wifi on phone or connect phone to WRT1900AC and try again. Not sure if your phone does fast-switching-handoff of LTE/Wi-Fi, but that is also a possibility.
Per Yngve Berg wrote:
I can only see one possible culprit to cause this and that is duplicate MAC Address.
Here is what my MACs look like. I've labeled the items that don't show hostnames correctly as well as labeled which items are connected to the WRT1900ac. I don't appear to have any duplicate MACs here.
Here is the client list for the WRT1900ac. For some reason, my MacBook (connected to the r8000) shows up on this list as well as the Surface Pro which IS connected to the WRT1900ac.
Joined: 16 Nov 2015 Posts: 6440 Location: UK, London, just across the river..
Posted: Sat Dec 11, 2021 17:41 Post subject:
space/interval and special symbols are not permitted for clients names and this can cause you a troubles
i use - instead of space...
example:
Ipad-64
MAMAs-Laptop-Lenovo
CorporatePC-Dell-i9
Iphone11-256 _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Joined: 08 May 2018 Posts: 14223 Location: Texas, USA
Posted: Sat Dec 11, 2021 18:34 Post subject:
I don't think it's a hostname problem
rtbrjason wrote:
Here is what my MACs look like. I've labeled the items that don't show hostnames correctly as well as labeled which items are connected to the WRT1900ac. I don't appear to have any duplicate MACs here.
No, I just wanted to give a clear picture of the MAC addresses and what each device was, and where it was connected since the topic of duplicate MACs came up. I've just started adding some static leases to get the naming to show correctly but haven't done everything yet.
kernel-panic69 wrote:
I don't think it's a hostname problem
rtbrjason wrote:
Here is what my MACs look like. I've labeled the items that don't show hostnames correctly as well as labeled which items are connected to the WRT1900ac. I don't appear to have any duplicate MACs here.
I finally decided to try the experimental driver. That seems to have resolved the TX errors. It also made available all wireless channels for each radio.
Posted: Tue Jan 11, 2022 21:53 Post subject: R8000 TX errors
On the R8000 running the experimental driver, are you still on version 47822 OR did you change that as well? I too am running a R8000 and experience TX errors but not nearly as many as what you were listing. I have around 4K errors over the past 4 days.
Posted: Sun Jan 16, 2022 23:59 Post subject: Re: R8000 TX errors
Earlkarp wrote:
On the R8000 running the experimental driver, are you still on version 47822 OR did you change that as well? I too am running a R8000 and experience TX errors but not nearly as many as what you were listing. I have around 4K errors over the past 4 days.
I'm currently on 48075. This the 3rd version I've tried with the experimental driver and have seen no TX errors since making the switch. I do seem to get some issues with the router becoming unresponsive and requiring a reboot after a few days. I'll be updating the the newest one again this evening.
