Picked up a “new old stock” hAP AX2. Doesn’t seem to be used, but also without any warranty.
My issue is that Winbox won’t stay connected. Either 3.41 or 4_beta16. LOG says user connected/disconnected, Winbox4 will say “Decrypt failed”. Legacy mode in Winbox3 doesn’t help. Sometimes it disconnects immediately, sometimes after clicking around, almost always when typing “print” into Terminal.
Tried to downgrade from 7.16.2 to 7.15.3 (where my other hAP AX2 is, in case it was a 7.16 issue) and nothing.
WebFig works without problems but I just prefer RouterOS.
SSH sometimes disconnects with “message authentication code incorrect”
Right now I’m using at as a WiFi AP only and that is stable, no issues there, it’s just Winbox.
Another thing to try is to put a (dumb) switch between your PC and the AX2, it is one of those mysterious things that sometimes help in connection.
And if you don’t need it, taking a port out of the bridge and reserve it to Winbox management is a common practice, in your simple configuration it is not needed, but if you start fiddling with bridge settings it is easy to get locked out.
Hi, yes, over both. The AX2 is connected through my AC2, for now only acting as an access point.
I do have an update though: I managed to netinstall 7.8 and that seems to be stable. I upgraded to 7.13.5 (just the OS, not the routerboard firmware) and it also seems to be fine. I would like to find out why it happens on 7.15 and higher (what I tested in the past). My other AX2 doesn’t have any issues, currently on 7.16.2.
Let me find my dumb Mercusys switch and I will test that theory.
Okay, so 7.14.3 is also fine. But 7.15.2 is busted. I went through the verbose export (with every setting on default except IP on eth1 so I can access webfig) and I can see nothing that would cause this. Only minor settings with like SMB, OpenVPN default config and that sort of thing.
Well, for now I will have to stay at 7.14.3. Thanks!
It remains “strange”, even if it happens only on some particular versions the Ax2 is a common device and 7.15.2 is old enough that should have already been some reports.
The good news are that 7.14.3 seems like a very stable version for wi-fi issues.
I have a third AX2 coming in next week. Also used, but under warranty this time. I hope it doesn’t happen on that one. But yeah, at least a stable build works just fine now. I just wonder what the “decryption failed” means in Winbox4. I mean it’s clearly related to the encrypted Winbox traffic, but I have not seen that error code anywhere, no documentation for it etc. Winbox3 just logs out.
Another update, unfortunately not. Trying to "export verbose" crashes Winbox and SSH Corrupted MAC on input.
ssh_dispatch_run_fatal: Connection to 172.17.0.2 port 22: message authentication code incorrect
Maybe, even if it can be a PITA, you could try netinstall to "nuke" everything and re-install the RouterOS really from scratch.
It has been reported several times that some cruft may remain in storage when doing simple upgrades, confioguration restores, etc., that builds up and can create issues.
I have done complete Netinstall back in January, I doubt it would be any different now. I feel it has to be a hardware defect. Maybe something regarding SSL changed in ROS 7.15 and the CPU has enough damage for it to be crashing on that?
It doesn't sound like a CPU hardware issue, in a CPU the same operation/path/junction/opcode/whatever Is used by many different "high level" OS commands, i.e. your router would crash much more frequently, on many commands.
It seems more similar with what can happen if a page of RAM or a block of storage Is defective.
If It was Ram, It would probably also be more frequent.
But - in theory at least - with wear leveling and self check algorithms in modern chips, it should not happen on storage, unless it is completely worn down.
If It was a different device the attempt to do would be a disk wipe and check, but this Is not possible on Mikrotiks AFAIK (short of desoldering the chip, work on It externallly and then resoldering It).
The storage chip can be replaced, but , since the RouterOs license is tied to its id/serial, you would need a new license, which cost needs to be added to the cost for the chip and the actual repair work, so hardly convenient, particularly as we don't know for sure if the issue Is actually with that.
