If you did it at my office, nothing because typically only one of those jacks is cross connected (the other is a spare wire) also our switches use spanning tree. Most network loops I’ve seen have been caused by logical configuration errors.
Network loops are real.
Network loops are common.
Network loops are the leading cause of people screaming “for fucks sake!” After spending far too long looking for other solutions to why the network goes down intermittently.
If you have a good switch or router, correct. If you have cheap consumer level crap, it could potentially cause a lot of issues until you unplug it. It wholly depends what’s on the other end of those jacks, though. Who knows what “in” and “out” mean in this context.
… What does this do to a network anyway? Nothing, right?
If you did it at my office, nothing because typically only one of those jacks is cross connected (the other is a spare wire) also our switches use spanning tree. Most network loops I’ve seen have been caused by logical configuration errors.
Network loops are real. Network loops are common. Network loops are the leading cause of people screaming “for fucks sake!” After spending far too long looking for other solutions to why the network goes down intermittently.
If you have a good switch or router, correct. If you have cheap consumer level crap, it could potentially cause a lot of issues until you unplug it. It wholly depends what’s on the other end of those jacks, though. Who knows what “in” and “out” mean in this context.
If you remember to use a cross-over cable, it ruins the address resolution protocol and stops everything from working.
Modern routers have code exclusively to detect it and disable the ports.
And if you don’t have spanning tree enabled, this could be a big problem