BE63 Constant Issues
So I have a Deco BE63 and I'm having some issues. Latest firmware is on it and what's going on is a complete loss of connection. It's random it can happen at any time and I have checked everything and also had my ISP take a look to make sure it's not on there end. They came out and checked and everything is normal all speeds are normal all wiring is new they even replaced my Ethernet going from my ONT to the deco just to be on the safe side. Problem is still occurring. I also have tried running the BE63 in AP mode and while that stopped the Ethernet drop off there is also another bug where in AP mode I am only getting half my speeds on the download side. The upload is fine. But as soon as I put the BE63 back in router mode the speeds goes back to normal. I even tried hooking my old Orbi system back up and ran that for a few days. I had no random disconnections at all. I'm at wits end trying to figure this out. Someone had mentioned this was a known problem with HW version 1.6 and the newest HW version fixed the connection issues. Any truth to that?
thanks
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I have removed all my Amazon devices. The network is more stable and still problematic. This is the tcpdump. This is coming from a satellite node using wireless backhaul. It looks like a DDOS attack.
22:48:28.058601 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:28.058602 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:28.061151 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:28.167439 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:28.167439 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:28.168418 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:28.204936 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:28.209021 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:28.212863 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:28.242675 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:28.283711 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:28.304358 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:28.409433 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:28.419067 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:28.429488 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:29.444987 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:29.480011 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:29.497306 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:29.537716 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:29.546619 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:30.561277 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:30.702212 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:30.732108 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:30.757291 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:30.767988 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:30.775725 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:30.787054 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:30.817667 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:30.906173 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:31.907991 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:31.952266 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:31.971089 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:31.981944 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:32.008677 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:32.052669 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:33.086990 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:33.161907 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:33.369309 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
22:48:33.531057 8c:86:dd:08:bc:54 > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 86: 192.168.0.168.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) AAAA [|domain]
- Copy Link
- Report Inappropriate Content
Hi,
Since you have contacted our technical support team via email TKID260452070, it's recommended to reply to the email for further assistance.
Best Regards
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
My TP-Link Deco BE63 recently downloaded the latest firmware - Deco BE63(US)_V2.6_1.3.2 Build 26040912.
Since this firmware was installed, it no longer works with my Xfinity Xfi XB7 modem when the TP-Link is in router mode. It will only work if I set the TP-Link to Access Point mode. This is true regardless of whether the Xfi is set to bridge or router mode. This did not happen with the previous firmware and the failure coincides with the day the new firmware was automatically downloaded by the Deco.
To prove this, I'd like to re-install the previous level TP-Link firmware, but the notes for the current version say " Note: This firmware can not be degraded to the previous version."
Question. How do I downlevel the TP-Link - even if it's only long enough to prove the firmware change is the cause of my problems? Ideas?
- Copy Link
- Report Inappropriate Content
so far the interaction is like 1 response per day if I am lucky from the support folks. This is comical. After I have uploaded the logs, described the issue, and emphasize that it is in AP mode, they recommend to disable IPV6. How would you do that in AP mode?
- Copy Link
- Report Inappropriate Content
Hi,
Usually, updating the Deco BE63's firmware to v1.3.2 won't cause it to stop working with your modem in router mode. It's recommended to confirm the following information for troubleshooting.
1. When Deco works in AP mode, what's the IP address on your client device when connecting to the Deco network?
2. When Deco works in Router mode, please connect your phone to Deco's Wi-Fi, go to the Deco app > More > Internet Connection > IPv4 page, what's the IP address on this page? If you have an IPv4 address, please change the DNS server to 8.8.8.8 and 8.8.4.4 on the Advanced > DHCP Server page, and then check whether you have internet from the Deco.
Best Regards
- Copy Link
- Report Inappropriate Content
1. When in AP mode, the TP link Ethernet connected to the Xfinity xFi is at address 10.0.0.69 (assigned by the xFi in router mode). All other connected devices also have a 10.0.0.xx address.
2) I've already tried that. I put the TP-Link Deco BE63 in router mode and made the DNS servers 8.8.8.8 & 1.1.1.1. These settings fail, no internet.
I agree that firmware updates aren't usually a problem, but this problem started right after the Deco auto-updated the firmware. It's more than a coincidence. Also, I turned off the TP-Link and connected a cheap-o Cudy TR3000 with factory reset settings to the xFi and it worked flawlessly.
The obvious way to prove that it is (or isn't) the firmware update is to downgrade the TP-Link to the previous firmware version. So, back to my original question: how do I do this?
- Copy Link
- Report Inappropriate Content
OK to do this it's a little bit of a tedious process, in order to go back to the previous firmware, you have to follow the procedures like the Deco is bricked. It's a little bit of a process and you have to do it individually. You can't do all three at the same time so take your time and do it one at a time. I had to do this before, and it worked fine, but just air on the side of caution.
to do this use method 2 hold the reset button down, then put power to the Deco. Keep holding that reset button until the status light changes, then open up a webpage and you should see recovery mode make sure you have the firmware prior to the one that's curling installed and then just click install firmware
https://www.tp-link.com/us/support/faq/2958/
- Copy Link
- Report Inappropriate Content
now all the deco nodes are doing mDNS. TPLink what can be done?????. There is no more IoT device on the network.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 7
Views: 21517
Replies: 87
Voters 2
