Mikrotik 3.10 to 3.30 Bug
So I ran into a problem after installing a new Mikrotik back-haul. Reference the diagram below:
I have a building that I’m serving wireless to, and I was doing the back-haul with some old Redlines…this all worked fine. Well, the Redlines eventually tanked on me, so I swapped them for some 411s. When I got the 411s in, I threw 3.30 on them and installed them. I could pass traffic fine across them, no problems. I then hooked up the building AP and left. I then got a call saying that the wireless was useless…nice.
I went out to investigate and I was getting some interesting results. I connected to the AP just fine. I opened winbox and could ping from the AP to the internet just fine. With the ping still running, I tried to browse to any site other than google, and the pings stopped passing… I rebooted the AP and got the same results…everything was fine until I tried to pull a real page, at which point the ethernet between my AP and the back-haul radio stopped passing traffic.
After futzing with it for several minutes, I noticed that my AP was still on 3.10, so I upgraded the OS to 3.30 which is the same version my back-hauls are running. I started my ping again, and browsed to a site and…it worked perfectly. Nothing dropped and all my pages loaded. There appears to be a bug that when 3.10 tries to communicate with a 3.30ish MTK, the traffic just stops passing.
I hope you guys don’t run into these issues, but if you do, upgrade!
Now you’re starting to sound like you work for Mikrotik! “Have problem…..first upgrade since we’ve probably fixed it already.” 😉
I am officially the head of the redneck liaison office…and how are things going Rob? 😛 hehehe
I believe he gets 50 cents everytime he says Microtik…Carl’s JR.
Ha…good times……….Mikrotik Carl’s JR.
PEBKAC
I’m hating on an OS X snow kitty server at the moment. Open directory is flakin out and I only have about 1400 users in it. Can’t say I’ve ever had a *nix server that would just lock. No errors, no panics, just lights are on but no one’s home crap. I’m sure it’s an ID ten T error on my part though. 😉
Bah…one of those days, eh 😉 I’m hoping you have a backup of some sort? Is this a file server, or an authentication server?
I’ve been back and forth with enterprise support for 3 weeks…..you read that right….3 weeks! I’ve reinstalled the OS 3-4 times, sent them log files/diagnostics, disabled all services, jumped through burning rings, etc… The server itself isn’t doing that much….just directory services. It provides mobile profiles for mac users and does a lil smb share for windoze clients to their home directory. I had hopes to move all directory services over to it but with it just randomly locking up, I’ll have to rethink that for a bit. I’m leaning towards apple sauce than apple pie right now for sure! 😀
I have to say I’ve never had these kinds of issues with my windows DCs…Though I have seen some crazy stuff happen.