ssh works (kinda), winbox doesn't

RouterOS General
1

I’ve got a really weird problem. 3 ROS units, 2 PC based (R1, R2), the other is a 532, which sits in the middle.

From a workstation behind R1, I can ssh into R2, but then weirdness begins:

  • I can move round all over the place (/ip route, /system resource, etc)
  • I can NOT, however, print anything… I get no output and have to kill the session

From the same workstation, Winbox can log into R2, but it never gets past “retrieving preferences”

Ok, so let’s move closer… I log into R1, then ssh to R2. Same behavior… I can move around, but can’t issue any actual commands. Both print and export just hang.

Now, let’s move even closer… from the router in the middle, I ssh into R2, and viola! Everything is working as expected.

ping, traceroute, ssh, etc… show that all routing is in place and properly working in both directions, why can’t I do anything via ssh, and why won’t winbox work?

Any help, pointers, tips, etc… would be greatly appreciated!

2

Packet sizes? MTU blackhole?

Regards

Andrew

3

I still don’t know what was wrong, but I removed an EOIP tunnel between the two end points, and added necessary static routes at the mid-point. Traffic started flowing with a vengeance. I guess EOIP isn’t the way to go… I’ll test with an IPIP tunnel later, and see what that does.

Looking at the ROS documentation, I found a reference to possible performance issues with EOIP due to packet fragmentation, but why would this suddenly become a problem after 15 months?

I’m going to post a (relatively) detailed network diagram later to see if I can get some guru-level input on the best way to approach a complete network reconfiguration to solve this and a couple other problems.