F5F Stay Refreshed Power Users Networks Error detected in Netgear switch's loopback function.

Error detected in Netgear switch's loopback function.

Error detected in Netgear switch's loopback function.

P
PXgame_br
Junior Member
Find
49
07-09-2023, 09:53 AM
#1
Dear tech community, I am reaching out for help. I had some strange network errors at home for some time, found out ports on my switch (Netgear GS308T) just randomly "die". If I plug to another port, it works again, but the old one is dead (also if I connect something else). After some time (one or two days, sometimes longer) the next one dies to, and so on, a restart "revives" the ports. Looked up the logs and found a selfloop error, but even after researching and a reset+firmware update on the switch I can't by the love of god figure out where and how I created a selfloop and if that could be the thing that causes the ports to "die". My network is quite simple, a Fritzbox as network/mesh master, and two Fritz mesh repeaters, the switch is connected to one of the repeaters to provide network in my home office/gaming room. As far as I can tell the only connection that "kills" the ports is the one between switch and repeater (cat6 cable, about 4m, I tried different ones, no change). Any ideas? Should I deactivate STP (even if that should theoretically prevent loops, if I understand correctly)? The next idea would be buying a new switch. These are the logs from today, one of the ports wasn't working and I changed ports a few times: Spoiler <179>1 2025-04-05T14:21:44.641+01:01 192.168.1.5-1 STP-3-SELFLOOP proto_stp.c(688) %% Dropping BPDU on Port GigabitEthernet2. Received BPDU SMAC (C8:9E:43:83:B9:99) same as that of interface <182>1 2025-04-05T14:21:06.631+01:01 192.168.1.5-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet6 moving from Blocking to Forwarding <182>1 2025-04-05T14:21:03.901+01:01 192.168.1.5-1 LLDP-6-NEIGHBOR_DISCOVER proto_lldp.c(4578) %% New neighbor on port GigabitEthernet6: Chassis ID D8:5EBig Grin3:8A:24:C5, Port ID D8:5EBig Grin3:8A:24:C5 <182>1 2025-04-05T14:21:03.881+01:01 192.168.1.5-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet6 moving from Disabled to Blocking <181>1 2025-04-05T14:21:03.771+01:01 192.168.1.5-1 TRAPMGR-5-PORT_LINK_UP ksi_snmp.c(232) %% Interface GigabitEthernet6 link up <182>1 2025-04-05T14:20:59.511+01:01 192.168.1.5-1 LLDP-6-NEIGHBOR_DEL proto_lldp.c(4320) %% Neighbor deleted on port GigabitEthernet6: Chassis ID D8:5EBig Grin3:8A:24:C5, Port ID D8:5EBig Grin3:8A:24:C5 <182>1 2025-04-05T14:20:58.131+01:01 192.168.1.5-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet6 moving from Forwarding to Disabled <181>1 2025-04-05T14:20:58.941+01:01 192.168.1.5-1 TRAPMGR-5-PORT_LINK_DOWN ksi_snmp.c(230) %% Interface GigabitEthernet6 link down <182>1 2025-04-05T14:19:33.621+01:01 192.168.1.5-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet2 moving from Blocking to Forwarding <182>1 2025-04-05T14:19:31.031+01:01 192.168.1.5-1 LLDP-6-NEIGHBOR_DISCOVER proto_lldp.c(4578) %% New neighbor on port GigabitEthernet2: Chassis ID C2:39:6F:65:85:C2, Port ID C2:39:6F:65:85:C2 <182>1 2025-04-05T14:19:31.371+01:01 192.168.1.5-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet2 moving from Disabled to Blocking <181>1 2025-04-05T14:19:31.351+01:01 192.168.1.5-1 TRAPMGR-5-PORT_LINK_UP ksi_snmp.c(232) %% Interface GigabitEthernet2 link up <182>1 2025-04-05T14:18:54.511+01:01 192.168.1.5-1 LLDP-6-NEIGHBOR_DEL proto_lldp.c(4320) %% Neighbor deleted on port GigabitEthernet2: Chassis ID C2:39:6F:65:85:C2, Port ID C2:39:6F:65:85:C2 <182>1 2025-04-05T14:18:53.621+01:01 192.168.1.5-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet2 moving from Forwarding to Disabled <181>1 2025-04-05T14:18:53.591+01:01 192.168.1.5-1 TRAPMGR-5-PORT_LINK_DOWN ksi_snmp.c(230) %% Interface GigabitEthernet2 link down <179>1 2025-04-05T14:18:48.631+01:01 192.168.1.5-1 STP-3-SELFLOOP proto_stp.c(688) %% Dropping BPDU on Port GigabitEthernet2. Received BPDU SMAC (C8:9E:43:83:B9:99) same as that of interface <181>1 2025-04-05T14:17:57.991+01:01 192.168.1.5-1 AAA-5-CONNECT login.c(158) %% New http connection for user admin, source 192.168.1.30 ACCEPTED <179>1 2025-04-05T14:17:55.671+01:01 192.168.1.5-1 STP-3-SELFLOOP proto_stp.c(688) %% Dropping BPDU on Port GigabitEthernet2. Received BPDU SMAC (C8:9E:43:83:B9:99) same as that of interface <180>1 2025-04-05T14:17:47.741+01:01 192.168.1.5-1 AAA-4-USER_REJECT login.c(251) %% New http connection for user admin, source 192.168.1.30 REJECTED <181>1 2025-04-05T14:17:47.741+01:01 192.168.1.5-1 TRAPMGR-5-AUTH_FAIL login.c(245) %% Failed User Login with User ID: admin <182>1 2025-04-05T14:13:08.611+01:01 192.168.0.239-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet2 moving from Blocking to Forwarding <182>1 2025-04-05T14:13:05.011+01:01 192.168.0.239-1 LLDP-6-NEIGHBOR_DISCOVER proto_lldp.c(4578) %% New neighbor on port GigabitEthernet2: Chassis ID C2:39:6F:65:85:C2, Port ID C2:39:6F:65:85:C2 <182>1 2025-04-05T14:13:05.861+01:01 192.168.0.239-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet2 moving from Disabled to Blocking <181>1 2025-04-05T14:13:05.611+01:01 192.168.0.239-1 TRAPMGR-5-PORT_LINK_UP ksi_snmp.c(232) %% Interface GigabitEthernet2 link up <182>1 2025-04-05T14:13:05.611+01:01 192.168.0.239-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet6 moving from Blocking to Forwarding <182>1 2025-04-05T14:13:03.621+01:01 192.168.0.239-1 LLDP-6-NEIGHBOR_DISCOVER proto_lldp.c(4578) %% New neighbor on port GigabitEthernet6: Chassis ID D8:5EBig Grin3:8A:24:C5, Port ID D8:5EBig Grin3:8A:24:C5 <182>1 2025-04-05T14:13:03.611+01:01 192.168.0.239-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet6 moving from Disabled to Blocking <181>1 2025-04-05T14:13:03.391+01:01 0.0.0.0-1 TRAPMGR-5-PORT_LINK_UP rsd_l3_intf.c(130) %% Interface VLAN-MGMT link up <181>1 2025-04-05T14:13:03.381+01:01 0.0.0.0-1 TRAPMGR-5-PORT_LINK_UP ksi_snmp.c(232) %% Interface GigabitEthernet6 link up <182>1 2025-04-05T14:12:58.511+01:01 0.0.0.0-1 LLDP-6-NEIGHBOR_DEL proto_lldp.c(4320) %% Neighbor deleted on port GigabitEthernet6: Chassis ID D8:5EBig Grin3:8A:24:C5, Port ID D8:5EBig Grin3:8A:24:C5 <182>1 2025-04-05T14:12:57.611+01:01 192.168.0.239-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet6 moving from Forwarding to Disabled <181>1 2025-04-05T14:12:57.591+01:01 192.168.0.239-1 TRAPMGR-5-PORT_LINK_DOWN ksi_snmp.c(230) %% Interface GigabitEthernet6 link down <181>1 2025-04-05T14:12:57.591+01:01 192.168.0.239-1 TRAPMGR-5-PORT_LINK_DOWN rsd_l3_intf.c(118) %% Interface VLAN-MGMT link down <182>1 2025-04-05T14:09:32.011+01:01 192.168.0.239-1 LLDP-6-NEIGHBOR_DISCOVER proto_lldp.c(4578) %% New neighbor on port GigabitEthernet6: Chassis ID D8:5EBig Grin3:8A:24:C5, Port ID D8:5EBig Grin3:8A:24:C5 <182>1 2025-04-05T14:09:22.601+01:01 192.168.0.239-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet6 moving from Blocking to Forwarding <182>1 2025-04-05T14:09:20.351+01:01 0.0.0.0-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet6 moving from Disabled to Blocking <181>1 2025-04-05T14:09:20.201+01:01 0.0.0.0-1 TRAPMGR-5-PORT_LINK_UP ksi_snmp.c(232) %% Interface GigabitEthernet6 link up <181>1 2025-04-05T14:09:20.201+01:01 0.0.0.0-1 TRAPMGR-5-PORT_LINK_UP rsd_l3_intf.c(130) %% Interface VLAN-MGMT link up <182>1 2025-04-05T14:09:18.101+01:01 0.0.0.0-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet6 moving from Forwarding to Disabled <181>1 2025-04-05T14:09:17.881+01:01 192.168.1.5-1 TRAPMGR-5-PORT_LINK_DOWN rsd_l3_intf.c(118) %% Interface VLAN-MGMT link down <181>1 2025-04-05T14:09:17.871+01:01 192.168.1.5-1 TRAPMGR-5-PORT_LINK_DOWN ksi_snmp.c(230) %% Interface GigabitEthernet6 link down
Reply
Reply
P
PXgame_br
07-09-2023, 09:53 AM #1

Dear tech community, I am reaching out for help. I had some strange network errors at home for some time, found out ports on my switch (Netgear GS308T) just randomly "die". If I plug to another port, it works again, but the old one is dead (also if I connect something else). After some time (one or two days, sometimes longer) the next one dies to, and so on, a restart "revives" the ports. Looked up the logs and found a selfloop error, but even after researching and a reset+firmware update on the switch I can't by the love of god figure out where and how I created a selfloop and if that could be the thing that causes the ports to "die". My network is quite simple, a Fritzbox as network/mesh master, and two Fritz mesh repeaters, the switch is connected to one of the repeaters to provide network in my home office/gaming room. As far as I can tell the only connection that "kills" the ports is the one between switch and repeater (cat6 cable, about 4m, I tried different ones, no change). Any ideas? Should I deactivate STP (even if that should theoretically prevent loops, if I understand correctly)? The next idea would be buying a new switch. These are the logs from today, one of the ports wasn't working and I changed ports a few times: Spoiler <179>1 2025-04-05T14:21:44.641+01:01 192.168.1.5-1 STP-3-SELFLOOP proto_stp.c(688) %% Dropping BPDU on Port GigabitEthernet2. Received BPDU SMAC (C8:9E:43:83:B9:99) same as that of interface <182>1 2025-04-05T14:21:06.631+01:01 192.168.1.5-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet6 moving from Blocking to Forwarding <182>1 2025-04-05T14:21:03.901+01:01 192.168.1.5-1 LLDP-6-NEIGHBOR_DISCOVER proto_lldp.c(4578) %% New neighbor on port GigabitEthernet6: Chassis ID D8:5EBig Grin3:8A:24:C5, Port ID D8:5EBig Grin3:8A:24:C5 <182>1 2025-04-05T14:21:03.881+01:01 192.168.1.5-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet6 moving from Disabled to Blocking <181>1 2025-04-05T14:21:03.771+01:01 192.168.1.5-1 TRAPMGR-5-PORT_LINK_UP ksi_snmp.c(232) %% Interface GigabitEthernet6 link up <182>1 2025-04-05T14:20:59.511+01:01 192.168.1.5-1 LLDP-6-NEIGHBOR_DEL proto_lldp.c(4320) %% Neighbor deleted on port GigabitEthernet6: Chassis ID D8:5EBig Grin3:8A:24:C5, Port ID D8:5EBig Grin3:8A:24:C5 <182>1 2025-04-05T14:20:58.131+01:01 192.168.1.5-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet6 moving from Forwarding to Disabled <181>1 2025-04-05T14:20:58.941+01:01 192.168.1.5-1 TRAPMGR-5-PORT_LINK_DOWN ksi_snmp.c(230) %% Interface GigabitEthernet6 link down <182>1 2025-04-05T14:19:33.621+01:01 192.168.1.5-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet2 moving from Blocking to Forwarding <182>1 2025-04-05T14:19:31.031+01:01 192.168.1.5-1 LLDP-6-NEIGHBOR_DISCOVER proto_lldp.c(4578) %% New neighbor on port GigabitEthernet2: Chassis ID C2:39:6F:65:85:C2, Port ID C2:39:6F:65:85:C2 <182>1 2025-04-05T14:19:31.371+01:01 192.168.1.5-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet2 moving from Disabled to Blocking <181>1 2025-04-05T14:19:31.351+01:01 192.168.1.5-1 TRAPMGR-5-PORT_LINK_UP ksi_snmp.c(232) %% Interface GigabitEthernet2 link up <182>1 2025-04-05T14:18:54.511+01:01 192.168.1.5-1 LLDP-6-NEIGHBOR_DEL proto_lldp.c(4320) %% Neighbor deleted on port GigabitEthernet2: Chassis ID C2:39:6F:65:85:C2, Port ID C2:39:6F:65:85:C2 <182>1 2025-04-05T14:18:53.621+01:01 192.168.1.5-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet2 moving from Forwarding to Disabled <181>1 2025-04-05T14:18:53.591+01:01 192.168.1.5-1 TRAPMGR-5-PORT_LINK_DOWN ksi_snmp.c(230) %% Interface GigabitEthernet2 link down <179>1 2025-04-05T14:18:48.631+01:01 192.168.1.5-1 STP-3-SELFLOOP proto_stp.c(688) %% Dropping BPDU on Port GigabitEthernet2. Received BPDU SMAC (C8:9E:43:83:B9:99) same as that of interface <181>1 2025-04-05T14:17:57.991+01:01 192.168.1.5-1 AAA-5-CONNECT login.c(158) %% New http connection for user admin, source 192.168.1.30 ACCEPTED <179>1 2025-04-05T14:17:55.671+01:01 192.168.1.5-1 STP-3-SELFLOOP proto_stp.c(688) %% Dropping BPDU on Port GigabitEthernet2. Received BPDU SMAC (C8:9E:43:83:B9:99) same as that of interface <180>1 2025-04-05T14:17:47.741+01:01 192.168.1.5-1 AAA-4-USER_REJECT login.c(251) %% New http connection for user admin, source 192.168.1.30 REJECTED <181>1 2025-04-05T14:17:47.741+01:01 192.168.1.5-1 TRAPMGR-5-AUTH_FAIL login.c(245) %% Failed User Login with User ID: admin <182>1 2025-04-05T14:13:08.611+01:01 192.168.0.239-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet2 moving from Blocking to Forwarding <182>1 2025-04-05T14:13:05.011+01:01 192.168.0.239-1 LLDP-6-NEIGHBOR_DISCOVER proto_lldp.c(4578) %% New neighbor on port GigabitEthernet2: Chassis ID C2:39:6F:65:85:C2, Port ID C2:39:6F:65:85:C2 <182>1 2025-04-05T14:13:05.861+01:01 192.168.0.239-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet2 moving from Disabled to Blocking <181>1 2025-04-05T14:13:05.611+01:01 192.168.0.239-1 TRAPMGR-5-PORT_LINK_UP ksi_snmp.c(232) %% Interface GigabitEthernet2 link up <182>1 2025-04-05T14:13:05.611+01:01 192.168.0.239-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet6 moving from Blocking to Forwarding <182>1 2025-04-05T14:13:03.621+01:01 192.168.0.239-1 LLDP-6-NEIGHBOR_DISCOVER proto_lldp.c(4578) %% New neighbor on port GigabitEthernet6: Chassis ID D8:5EBig Grin3:8A:24:C5, Port ID D8:5EBig Grin3:8A:24:C5 <182>1 2025-04-05T14:13:03.611+01:01 192.168.0.239-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet6 moving from Disabled to Blocking <181>1 2025-04-05T14:13:03.391+01:01 0.0.0.0-1 TRAPMGR-5-PORT_LINK_UP rsd_l3_intf.c(130) %% Interface VLAN-MGMT link up <181>1 2025-04-05T14:13:03.381+01:01 0.0.0.0-1 TRAPMGR-5-PORT_LINK_UP ksi_snmp.c(232) %% Interface GigabitEthernet6 link up <182>1 2025-04-05T14:12:58.511+01:01 0.0.0.0-1 LLDP-6-NEIGHBOR_DEL proto_lldp.c(4320) %% Neighbor deleted on port GigabitEthernet6: Chassis ID D8:5EBig Grin3:8A:24:C5, Port ID D8:5EBig Grin3:8A:24:C5 <182>1 2025-04-05T14:12:57.611+01:01 192.168.0.239-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet6 moving from Forwarding to Disabled <181>1 2025-04-05T14:12:57.591+01:01 192.168.0.239-1 TRAPMGR-5-PORT_LINK_DOWN ksi_snmp.c(230) %% Interface GigabitEthernet6 link down <181>1 2025-04-05T14:12:57.591+01:01 192.168.0.239-1 TRAPMGR-5-PORT_LINK_DOWN rsd_l3_intf.c(118) %% Interface VLAN-MGMT link down <182>1 2025-04-05T14:09:32.011+01:01 192.168.0.239-1 LLDP-6-NEIGHBOR_DISCOVER proto_lldp.c(4578) %% New neighbor on port GigabitEthernet6: Chassis ID D8:5EBig Grin3:8A:24:C5, Port ID D8:5EBig Grin3:8A:24:C5 <182>1 2025-04-05T14:09:22.601+01:01 192.168.0.239-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet6 moving from Blocking to Forwarding <182>1 2025-04-05T14:09:20.351+01:01 0.0.0.0-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet6 moving from Disabled to Blocking <181>1 2025-04-05T14:09:20.201+01:01 0.0.0.0-1 TRAPMGR-5-PORT_LINK_UP ksi_snmp.c(232) %% Interface GigabitEthernet6 link up <181>1 2025-04-05T14:09:20.201+01:01 0.0.0.0-1 TRAPMGR-5-PORT_LINK_UP rsd_l3_intf.c(130) %% Interface VLAN-MGMT link up <182>1 2025-04-05T14:09:18.101+01:01 0.0.0.0-1 STP-6-PORT_STATE proto_stp.c(820) %% Port GigabitEthernet6 moving from Forwarding to Disabled <181>1 2025-04-05T14:09:17.881+01:01 192.168.1.5-1 TRAPMGR-5-PORT_LINK_DOWN rsd_l3_intf.c(118) %% Interface VLAN-MGMT link down <181>1 2025-04-05T14:09:17.871+01:01 192.168.1.5-1 TRAPMGR-5-PORT_LINK_DOWN ksi_snmp.c(230) %% Interface GigabitEthernet6 link down

Reply
Reply
D
Darkriot
Junior Member
Find
14
07-10-2023, 01:33 PM
#2
Visualize the layout. Confirm the switch isn’t linked to both the repeater and master. A loop exists—STP stops the network from failing by blocking ports instead of overloading them.
Reply
Reply
D
Darkriot
07-10-2023, 01:33 PM #2

Visualize the layout. Confirm the switch isn’t linked to both the repeater and master. A loop exists—STP stops the network from failing by blocking ports instead of overloading them.

Reply
Reply
P
Pandaninja54
Junior Member
Find
42
07-10-2023, 08:30 PM
#3
I'm pretty certain there isn't another cable there; it must pass through at least one wall. EDIT: There are also additional Wi-Fi devices such as phones, my wife's laptop, TVs, tablets, and more.
Reply
Reply
P
Pandaninja54
07-10-2023, 08:30 PM #3

I'm pretty certain there isn't another cable there; it must pass through at least one wall. EDIT: There are also additional Wi-Fi devices such as phones, my wife's laptop, TVs, tablets, and more.

Reply
Reply
B
Boba999
Member
Find
130
07-12-2023, 06:06 PM
#4
Hello, your message refers to logs from Fritz or Netgear equipment. It looks like the device is switching between GigabitEthernet6 and GigabitEthernet2 ports. Could you clarify where these ports are connected in your diagram? Also, the mention of "VLAN-MGMT" suggests VLAN management is involved—do you currently use VLANs in your network configuration? What role does the second repeater play? Is it just extending wireless range or does it support additional connections?
Reply
Reply
B
Boba999
07-12-2023, 06:06 PM #4

Hello, your message refers to logs from Fritz or Netgear equipment. It looks like the device is switching between GigabitEthernet6 and GigabitEthernet2 ports. Could you clarify where these ports are connected in your diagram? Also, the mention of "VLAN-MGMT" suggests VLAN management is involved—do you currently use VLANs in your network configuration? What role does the second repeater play? Is it just extending wireless range or does it support additional connections?

Reply
Reply
S
stampy1nose
Member
Find
52
07-13-2023, 12:09 PM
#5
The log comes from the Netgear switch. The Fritzbox router shows no issues. The unexpected behavior likely stemmed from changing ports on the switch. Some errors appear immediately when connecting a device to a "dead" port. Currently, Ethernet 2 connects to the repeater, Ethernet 6 is my main PC, Ethernet 7 runs the 3D Printer (off), and Ethernet 5/4/3 are inactive. I probably left everything on the switch after the reset/update—just basic settings like name, time, and password. The IP is managed via DHCP from the main router, with a static IP reservation. The second repeater serves kitchen coverage only via Wi-Fi. EDIT: On checking the switch’s port configuration page, "administrator mode" lists 3/4/5 as disabled, no way to turn them on.
Reply
Reply
S
stampy1nose
07-13-2023, 12:09 PM #5

The log comes from the Netgear switch. The Fritzbox router shows no issues. The unexpected behavior likely stemmed from changing ports on the switch. Some errors appear immediately when connecting a device to a "dead" port. Currently, Ethernet 2 connects to the repeater, Ethernet 6 is my main PC, Ethernet 7 runs the 3D Printer (off), and Ethernet 5/4/3 are inactive. I probably left everything on the switch after the reset/update—just basic settings like name, time, and password. The IP is managed via DHCP from the main router, with a static IP reservation. The second repeater serves kitchen coverage only via Wi-Fi. EDIT: On checking the switch’s port configuration page, "administrator mode" lists 3/4/5 as disabled, no way to turn them on.

Reply
Reply
N
Nivek360
Member
Find
68
07-13-2023, 03:29 PM
#6
It might be that the repeater at the bottom is connecting to the fritzbox via the top link. One idea is STP packets traveling through the wireless repeaters and coming back to the network switch. I haven’t used a Fritz repeater before, so I’m not certain. Another possibility is the NAS isn’t properly linked to the Netgear but instead to the Fritz repeater, causing occasional data transfers.
Reply
Reply
N
Nivek360
07-13-2023, 03:29 PM #6

It might be that the repeater at the bottom is connecting to the fritzbox via the top link. One idea is STP packets traveling through the wireless repeaters and coming back to the network switch. I haven’t used a Fritz repeater before, so I’m not certain. Another possibility is the NAS isn’t properly linked to the Netgear but instead to the Fritz repeater, causing occasional data transfers.

Reply
Reply
R
Rounyx
Posting Freak
Find
838
07-13-2023, 05:17 PM
#7
Yes, that's feasible. However, it raises concerns about potential issues. Initially, I believed mesh Wi-Fi would handle everything independently without requiring user attention. Regarding the NAS, the Fritz Repeater offers two Ethernet ports, both marked in the manual for standard connections. The Synology NAS only supplies a few file shares for data storage, lacking advanced features such as a Plex server.
Reply
Reply
R
Rounyx
07-13-2023, 05:17 PM #7

Yes, that's feasible. However, it raises concerns about potential issues. Initially, I believed mesh Wi-Fi would handle everything independently without requiring user attention. Regarding the NAS, the Fritz Repeater offers two Ethernet ports, both marked in the manual for standard connections. The Synology NAS only supplies a few file shares for data storage, lacking advanced features such as a Plex server.

Reply
Reply
B
Beatdown1423
Member
Find
56
07-15-2023, 05:05 AM
#8
The mesh Wi-Fi performs its intended function, linking all components automatically without manual input. Spanning Tree Protocol functions similarly to protocols like FTP or Samba—it detects potential loops and avoids broadcast storms, protecting regular connections from being overwhelmed. If you're confident your network is loop-free, you can turn off STP for simplicity. However, it's not advised without understanding the underlying issue. You could disable it temporarily to test its impact; a failure might result in an internet outage requiring a full restart of devices. Another discussion online mentioned using Energy Efficient Ethernet, though its relevance isn't clear for your situation.
Reply
Reply
B
Beatdown1423
07-15-2023, 05:05 AM #8

The mesh Wi-Fi performs its intended function, linking all components automatically without manual input. Spanning Tree Protocol functions similarly to protocols like FTP or Samba—it detects potential loops and avoids broadcast storms, protecting regular connections from being overwhelmed. If you're confident your network is loop-free, you can turn off STP for simplicity. However, it's not advised without understanding the underlying issue. You could disable it temporarily to test its impact; a failure might result in an internet outage requiring a full restart of devices. Another discussion online mentioned using Energy Efficient Ethernet, though its relevance isn't clear for your situation.

Reply
Reply
M
mouchnino
Junior Member
Find
3
07-15-2023, 09:17 AM
#9
Apologies for the delayed reply. I've been out for two weeks and wasn't able to test it. Thanks for finding this info; I'll follow up if it was useful.
Reply
Reply
M
mouchnino
07-15-2023, 09:17 AM #9

Apologies for the delayed reply. I've been out for two weeks and wasn't able to test it. Thanks for finding this info; I'll follow up if it was useful.

Reply
Reply
I
iRaine
Posting Freak
Find
800
07-16-2023, 10:40 PM
#10
I experimented with various configurations, yet the issue persists. Occasionally it happens once a week or twice daily. It seems drilling holes might be necessary.
Reply
Reply
I
iRaine
07-16-2023, 10:40 PM #10

I experimented with various configurations, yet the issue persists. Occasionally it happens once a week or twice daily. It seems drilling holes might be necessary.

Reply
Reply