Home Network Community > Deco > Virgin Hub 5 and TP-link Deco mesh network not playing nice with each other
< Deco

Virgin Hub 5 and TP-link Deco mesh network not playing nice with each other

Virgin Hub 5 and TP-link Deco mesh network not playing nice with each other

Virgin Hub 5 and TP-link Deco mesh network not playing nice with each other
Virgin Hub 5 and TP-link Deco mesh network not playing nice with each other
2024-06-07 08:37:33 - last edited 2024-06-13 03:11:58
Model: Deco X55  
Hardware Version: V1
Firmware Version: 1.4.1

I just switched from Sky Fiber to Virgin Fiber last week and I'm getting intermittent momentary dropouts on both wired and wireless devices, the deco node lights turn red for a few seconds I noticed when this happens. My setup is Virgin Hub 5 in modem mode connected to a base TP Link Deco x55 via ethernet cable. The base deco node is then connected to two other nodes via ethernet cable. The deco is setup in wireless router mode, configured to clone mac address of the Virgin Hub, DHCP is on and LAN ip is 192.168.0.1

 

My previous configuration with Sky Fiber was a bit different. Base deco node was connected directly to the ONT via ethernet cable. The sky router was never even taken out of the box. The deco settings were wireless router mode, IPTV/VLAN turned on and ISP profile was anything@skydsl. This worked flawlessly for a year and never any dropouts.

 

Obviously the Virgin Hub seems to be the problem if the X55s worked fine with Sky Fiber but is there any way I can configure the Decos to try and get a more stable connection. Would switching to access point mode help perhaps?

 

There is a constant stream of errors in the logs too but nothing critical

 

Fri Jun 7 09:26:42 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:26:49 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:26:55 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:26:59 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:27:02 2024 daemon.err client_mgmt: wireless client associate or disassociate.

Fri Jun 7 09:27:02 2024 daemon.err client_mgmt: client_mac:66-A3-90-3B-61-51, client_ifname:ath1, client_action:associate

Fri Jun 7 09:27:02 2024 daemon.err client_mgmt: client(66-A3-90-3B-61-51) assocaite by if(ath1).

Fri Jun 7 09:27:03 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[ath1] in eth_ifname

Fri Jun 7 09:27:08 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:27:11 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:27:13 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:27:15 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:27:27 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:27:31 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:27:34 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:27:56 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:28:08 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:28:13 2024 daemon.err nrd[13342]: steeralgFindBestAPCallback: iterate BSS APId 2 ChanId 4 ESSId 0 targetBand(0) != measuredBss->band(1)

Fri Jun 7 09:28:13 2024 daemon.err nrd[13342]: steeralgFindBestAPCallback: iterate BSS APId 3 ChanId 4 ESSId 0 targetBand(0) != measuredBss->band(1)

Fri Jun 7 09:28:14 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:28:15 2024 daemon.err hostapd: hostapd_notif_disassoc num_sta 8

Fri Jun 7 09:28:15 2024 daemon.err client_mgmt: wireless client associate or disassociate.

Fri Jun 7 09:28:15 2024 daemon.err client_mgmt: client_mac:66-A3-90-3B-61-51, client_ifname:ath1, client_action:disassociate

Fri Jun 7 09:28:15 2024 daemon.err client_mgmt: client(66-A3-90-3B-61-51) disassociate by if(ath1).

Fri Jun 7 09:28:28 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:28:34 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:28:48 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:28:56 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:28:59 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:29:08 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:29:14 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:29:35 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:29:37 2024 daemon.err udhcpd[9398]: Sending ACK to 192.168.0.126

Fri Jun 7 09:29:37 2024 daemon.err udhcpd[9398]: clear ip 7e00a8c0

Fri Jun 7 09:29:38 2024 daemon.err udhcpd[9398]: Sending ACK to 192.168.0.124

Fri Jun 7 09:29:38 2024 daemon.err udhcpd[9398]: clear ip 7c00a8c0

Fri Jun 7 09:29:56 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:30:09 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:30:15 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:30:16 2024 daemon.err udhcpd[9398]: Sending ACK to 192.168.0.108

Fri Jun 7 09:30:16 2024 daemon.err udhcpd[9398]: clear ip 6c00a8c0

Fri Jun 7 09:30:32 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:30:35 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:30:56 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:31:03 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:31:09 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:31:14 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:31:23 2024 daemon.err uhttpd[7914]: iptables: No chain/target/match by that name.

Fri Jun 7 09:31:23 2024 daemon.err uhttpd[7914]: iptables v1.4.21: Couldn't load target `domain_login_rule':No such file or directory

Fri Jun 7 09:31:23 2024 daemon.err uhttpd[7914]:

Fri Jun 7 09:31:23 2024 daemon.err uhttpd[7914]: Try `iptables -h' or 'iptables --help' for more information.

Fri Jun 7 09:31:23 2024 daemon.err uhttpd[7914]: iptables: No chain/target/match by that name.

Fri Jun 7 09:31:23 2024 daemon.err uhttpd[7914]: iptables: No chain/target/match by that name.

Fri Jun 7 09:31:23 2024 user.emerg : tp215,22[2936]:

Fri Jun 7 09:31:24 2024 daemon.err uhttpd[7914]: Failed to execute call dispatcher target for entry '/admin/web'.

Fri Jun 7 09:31:24 2024 daemon.err uhttpd[7914]: The called action terminated with an exception:

Fri Jun 7 09:31:24 2024 daemon.err uhttpd[7914]: bad argument #1 to 'pairs' (table expected, got nil)

Fri Jun 7 09:31:24 2024 daemon.err uhttpd[7914]: stack traceback:

Fri Jun 7 09:31:24 2024 daemon.err uhttpd[7914]: [C]: in function 'assert'

Fri Jun 7 09:31:24 2024 daemon.err uhttpd[7914]: ?: in function 'dispatch'

Fri Jun 7 09:31:24 2024 daemon.err uhttpd[7914]: ?: in function <?:218>

Fri Jun 7 09:31:25 2024 daemon.err uhttpd[7914]: uci: Entry not found

Fri Jun 7 09:31:25 2024 daemon.err uhttpd[7914]: uci: Entry not found

Fri Jun 7 09:31:28 2024 daemon.err uhttpd[7914]: uci: Entry not found

Fri Jun 7 09:31:29 2024 daemon.err uhttpd[7914]: uci: Entry not found

Fri Jun 7 09:31:35 2024 daemon.err /usr/bin/apsd: apsd_check_eth_has_neigh:1433: Error: can't find ifname[eth1.591] in eth_ifname

Fri Jun 7 09:31:38 2024 daemon.err client_mgmt: client(EC-FA-BC-8A-17-ED) not found in arp table disconnect_counter=0

Fri Jun 7 09:31:38 2024 daemon.err client_mgmt: client(84-F3-EB-4B-D0-42) not found in arp table disconnect_counter=0

Fri Jun 7 09:31:39 2024 daemon.err uhttpd[7914]: uci: Entry not found

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:Virgin Hub 5 and TP-link Deco mesh network not playing nice with each other-Solution
2024-06-07 17:13:38 - last edited 2024-06-13 03:11:58

  @Alfkbort 

 

The virgin hub has a documented issue on the 2.5gbe port with the latest firmware, could be related.

 

Basically the port power saving kicks in under certain conditions and the port speed can end up ramping down to essentially nothing. I had this issue although my tplink wasn't plugged directly into the router.

 

It only happened to me after I switched my VM Hub from router to modem mode. I ran in router mode for a while without any issues, this is not ideal as I was effectively double natting my network, however it was stable. After a month if it running ok I decided to factory reset and try modem mode again and it's been fine for months now.

 

I'll try and dig out the link but there possible fixes mentioned are

 

1. Don't use the 2.5gbe port on the VM Hub 

2. Run in router mode, not ideal but worked ok for me

3. Install a managed switch between your VM Hub and your tplink and use that to essentially disables the power saving setting and stops the VM Hub ramping the connection down.

 

Not sure if these are linked to what you are seeing or not but worth a look.

 

Cheers

Spence

Recommended Solution
  4  
  4  
#5
Options
7 Reply
Re:Virgin Hub 5 and TP-link Deco mesh network not playing nice with each other
2024-06-07 11:41:54

  @Alfkbort 

 

See the following recommendation from TP-Link: https://community.tp-link.com/en/home/forum/topic/669676?replyId=1365154

  0  
  0  
#2
Options
Re:Virgin Hub 5 and TP-link Deco mesh network not playing nice with each other
2024-06-07 13:24:49

  @Alexandre. Okay sounds good thanks. I'll the manual update and report back.

  0  
  0  
#3
Options
Re:Virgin Hub 5 and TP-link Deco mesh network not playing nice with each other
2024-06-07 15:58:04

  @Alexandre. One question though is it okay to install Deco X55(US)_V1_1.5.1 even if I'm in the EU? It says not to on the firmware page as it's against warranty and it seems the EU firmware page doesn't have the v1.5.1 firmware available 

  0  
  0  
#4
Options
Re:Virgin Hub 5 and TP-link Deco mesh network not playing nice with each other-Solution
2024-06-07 17:13:38 - last edited 2024-06-13 03:11:58

  @Alfkbort 

 

The virgin hub has a documented issue on the 2.5gbe port with the latest firmware, could be related.

 

Basically the port power saving kicks in under certain conditions and the port speed can end up ramping down to essentially nothing. I had this issue although my tplink wasn't plugged directly into the router.

 

It only happened to me after I switched my VM Hub from router to modem mode. I ran in router mode for a while without any issues, this is not ideal as I was effectively double natting my network, however it was stable. After a month if it running ok I decided to factory reset and try modem mode again and it's been fine for months now.

 

I'll try and dig out the link but there possible fixes mentioned are

 

1. Don't use the 2.5gbe port on the VM Hub 

2. Run in router mode, not ideal but worked ok for me

3. Install a managed switch between your VM Hub and your tplink and use that to essentially disables the power saving setting and stops the VM Hub ramping the connection down.

 

Not sure if these are linked to what you are seeing or not but worth a look.

 

Cheers

Spence

Recommended Solution
  4  
  4  
#5
Options
Re:Virgin Hub 5 and TP-link Deco mesh network not playing nice with each other
2024-06-07 17:19:54

Here's the link

 

https://community.virginmedia.com/t5/Tech-Chatter/Hub-5-Firmware-Upgrade/td-p/5480079

  1  
  1  
#6
Options
Re:Virgin Hub 5 and TP-link Deco mesh network not playing nice with each other
2024-06-07 19:30:29

Alfkbort wrote

  @Alexandre. One question though is it okay to install Deco X55(US)_V1_1.5.1 even if I'm in the EU? It says not to on the firmware page as it's against warranty and it seems the EU firmware page doesn't have the v1.5.1 firmware available 

  @Alfkbort 

 

The file that you will download from the link I provided is archive, ZIP file. Inside, there are three files and among them firmware file with .bin extension:

 

X55v1_en_1.5.1 Build 20240417 Rel. 52783_US_EU_JP_CA_up.bin

 

Judging from the file naming, which I am very familiar with, this is universal firmware for Deco X55 hardware V1 sold in the US, Europe, Japan (Asia?) and Canada. It should be safe to install it on European X55 hardware V1.

 

Make sure Deco you have is hardware V1, see: How to find the hardware version on a TP-Link device

  4  
  4  
#7
Options
Re:Virgin Hub 5 and TP-link Deco mesh network not playing nice with each other
2024-06-07 21:16:27

  @SpenceW That's sounds very like it could be the problem, mainly because most of the disconnects happen first thing in the morning. Like listening to streaming radio on an echo dot and it keeps disconnecting.

 

I've updated now to 1.5.1 firmware so will see if that has any effect tomorrow morning before trying one of your suggestions 

  1  
  1  
#8
Options

Information

Helpful: 0

Views: 751

Replies: 7

Related Articles
New Virgin Hub 5 set up
1421 0
Virgin Hub 5 Internet Connection
1353 0
 Virgin Hub 5 and Deco M4
212 0
virgin media hub 3 with tp link ax5400
1369 0
Tp link m4 with virgin media hub 3.0
8296 0
 New Virgin hub 5
542 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.