So we ran into a small issue today. We have a CCR that we’ve configured with the switch settings. One of our devices behind it stopped responding to pings and remote management but was still passing traffic. While troubleshooting I started to torch the interface and it started responding to pings.
to confirm, I stopped torch and it stopped responding. I have confirmed that in order to ping the device connected to that interface, I have to torch the interface.
Has anyone else ran into this?
Looks like connection tracking is in automatic mode. Try to switch it on.
I just tried to switch it to on and that didn’t seem to do the trick. I’m still seeing the same symptoms.
Even after the reboot? Then I don’t have any other idea…
We actually haven’t tried a reboot since this issue popped up. This only started happening after we rebooted it a few nights back after our fiber went down and the Mikrotik didn’t recover for some reason. I’m beginning to suspect the Mikrotik may be bad, we’ve updated the OS to the latest as well.
Therefore it is smart to have a lab to test the version you are going to deploy… You can downgrade back of course…
It’s such a minor problem that downgrading isn’t necessary. It’s a quirky problem thus the post, but not service impacting. Also, it’s only on this CCR, we have several deployed that are experiencing no issues with the latest OS.