BE63 Constant Issues

BE63 Constant Issues

76 Reply
Re:BE63 Constant Issues
Friday

  @Solla-topee 

 

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]

0
0
#72
Re:BE63 Constant Issues
Friday

  @loadii 

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

0
0
#73
Re:BE63 Constant Issues
Saturday

  @icehawk940 

 

only wish is that simple.  have responded to the case and no one respond.

0
0
#74
Re:BE63 Constant Issues
Sunday

  @loadii 

 

It's the weekend for most of the staff I would write them again on Monday 

 

Thanks 

Need help with the Deco app, setup, Ethernet backhaul, network switch or rolling back firmware? Router or AP mode? https://community.tp-link.com/us/home/forum/topic/699816?page=1
0
0
#75
Re:BE63 Constant Issues
Sunday

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?

0
0
#76
Re:BE63 Constant Issues
22 hours ago

  @HelpFixDecoApp 

 

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?

0
0
#77