A switching loop or bridging loop is a dangerous situation in switched computer networks (or in conjunction with multiple bridges), which in most situations leads to a complete network shutdown due to overload. In a switching loop, two network sockets on the same switch are directly connected to each other or there are two or more active connections between two switches. A switching loop completely overloads the network in several ways by constantly duplicating packets.
I’ve seen this myself once with a neighbor. He simply plugged a cable that was lying around into the switch so that it wasn’t lying around.
So you would have to check whether one of the cables leads back to the switch or the Internet box. Instead of depending on a device or if it is unnecessary.
There would only be a loop if 1 cable from the 2nd switch went back into the internet box…
But at least we now know that there are other network devices at play.
Disconnect all devices from the Internet box and then only connect a single PC via LAN and see whether the connection remains permanent.
And then step by step, individual device by individual device, always observing whether the LAN stays or “dies” after a few minutes.
….keep on rockin' 🤘🏼🤘🏼🤘🏼
[https://www.digitec.ch/de/s1/product/zyxel-gs-105b-v3-5-ports-netzwerk-switch-5665074?supplier=406802] (https://www.digitec.ch/de/s1/product/zyxel-gs-105b-v3-5-ports-netzwerk-switch-5665074?supplier=406802)
Zyxel. If I come across as extremely stupid, I’m sorry. I really have no idea
Sounds suspiciously like a network loop to me too. This can also occur if a bridge is unintentionally installed between the LAN and WLAN. When I look through your list of network devices, the Philips Hue Bridge catches my eye - maybe start troubleshooting there.
If it isn’t, activate the Spanning Tree Protocol (STP) on the Internet box in expert mode under Network.
Have you tried turning it off and on again?
Sevii wrote:
So, I have a cable that goes into a switch, which in turn goes into another switch (through a cable from the switch) (yes, I know, loss and stupid, but it’s enough) and that in turn could be the error?
You mean something like that?
No, that shouldn’t be the problem. Because I have been using this for several years.
On Switch 1 there is a TV, an XBox, a Nintendo Switch, the UHD 4K player, an Apple TV and a gateway for smart home control. A cable goes from Switch 1 to Switch 2 in the next room.
In addition to the PC, a TV with Netflix is connected to Switch 2. From Switch 2 goes to Switch 3 with a cable
A PC and an Apple TV are connected to Switch 3
If I were to go back from Switch 1, 2 or 3 with a cable to another switch or to the IB 4, then that would be a loop.
An example of a loop (the loop is created by the red cable):
Very good, then it really seems to have been a loop.
However, by activating STP you only circumvented the problem, but didn’t actually fix it. Your entire network traffic may now even run through the Hue Bridge. For stable operation, it is therefore important that you either disconnect the LAN-Anschluss on the Hue Bridge or deactivate its WLAN connection. To test whether the loop is really out, deactivate STP again. Whether you leave STP on permanently is a matter of taste. What is certain is that a home network must run stably even without STP.
PS: What exactly do you mean by “everything turned red”? All your Philips bulbs turned red, or what?
Have you tried turning it off and on again?
Hi @Sevii
Cool that you found the error. What do you mean by tree protocol?
P.s. If you haven’t had the new Internet box for 14 days, try returning it. Swisscom always says something about a 14-day return policy. Unless the IB3 was newer and you had a different one before, then I would keep the 3.