I have a working PTP link [Dynadish] connected 5 kms apart and was working fine till Monday for past1 year.
Monday the linked dropped connectivity. On probing further I realised that the connection on one end of the network works fine when plugged into a standalone laptop.
But the same connection when plugged into the switch stops responding. There is no IP conflict.
ok. exactly after one month of changing the swtich and the link working fine… today the same problems has come back.
when connected to a single laptop on one end of the PTP link… the link works fine but when the same ethernet is plugged into a swtich there is no ethernet communication.
and this is happening just at one end of the PTP link using Dynadish pair.
If your wireless connection is working fine, and the problem is just in one side and when you connect radio to your network switch and the switch port goes down you may have a loop in your network design and if your switch is manageable like MikroTik or Cisco switches you just need to set the BPDU filter or BPDU guard.
Last year i saw one of my customer link goes down, at first i can’t connect to radio on my side an when i connect to my cisco switch 3560 series i notice that the port connected to the radio goes down, so i try to connect to the mikrotik radio and check the wireless link, after a while i understand my customer switch side configured flat i mean they configure they’re cisco 2960 catalyst switch without VLAN configuration and put another radio’s link and network to that switch, and in some reason we are two link between each other in 2 way. Finally i just set the BPDU guard on my cisco switch and the problem solved.
Then tell to the customer to changed they’re design.
This sounds like a spanning tree issue to me – probably, somebody is creating a loop in the network and spanning tree is trying to block it. I would wager that something is connected to the switch that is plugged into itself and causing packets to loop. If the switch doesn’t support spanning tree then the MikroTik would kick in spanning tree and block the entire switch from connecting.
I have seen customers accidentally plug switches into themselves with a long cable where both ends are nearby each other – they see the two ends close by and assume both should be connected to the switch, and connect them, but meanwhile it is actually the same cable, so the customer has just plugged the switch into itself and created a loop. If the switch supports spanning tree, it will block this loop itself, but many unmanaged switches do not.
Unplug everything from that switch except your laptop and the dynadish. See if it works - it should. Plug the rest of the cables back in one at a time and retest so that you can figure out which connection brings everything down, and then you will find the source of the loop. There may be a switch connected directly to your switch that is plugged into itself.