I still failed to duplicate the bug between Echo Plus / Alexa and hAP ax² (7.9.1, i can not install 7.9.2 or I reset the timers…)…
(the only peripheral that stays at home for days, I have to go out to work…)
Everyone who writes about the bug had ever posted their configuration (no screenshots) just a useless list of chatter, maybe just for “me too”…
And when I ask, had anyone ever opened a ticket or sent the supout.rif with the ticket…
yes, we all have nothing to do but just only write here meee toooo. It can be combination of setting and client HW so you will never face it with one device…think a bit
MT support themselves have answered to quite a bit of problem reports to move to 7.10 chain.
Then why would anyone bother anymore to provide supout for 7.9 ??
7.9 is already history.
7.8 was pretty stable for me.
7.9 was a disaster. Disconnects, password not valid anymore even when you enter it correctly, PMKSA errors, …
7.10rc1 is ok again.
No, I wanted to know what problem you had, since this topic is about 7.9, and not 7.10rc,
but maybe you didn’t notice.
You don’t understand either the difference, or even what I wrote about previously.
So it’s more relevant that I write to us here, using 7.9.x, instead of you using 7.10rc.
And by the way it’s not an uptime comparison between devices, but how long a device stays connected to wifi before getting stuck.
So now I’m asking, If your not have 7.9x, why comment on it?
And what difference would there be in this "text comma"?
Where is the non-canary-alpha-beta-rc of the 7.10?
I am complaining about how people complain about things without even deigning to show the config, open a ticket or submit the supout.rif file,
then if we want to cover it all up with "there's 7.10rc anyway", fine,
know that there are people who act too much as a guinea pig with versions not called "canary-alpha-beta-rc" but which practically are...
Lets see how many drop in on this thread and say 7.10RC1 is still no good, that will give us a better idea. On Reddit I’m seeing people say 7.10beta5 still no good.
… and I would ask them too, “did you open the ticket and provide the supout.rif?”, “Where is the export of your configuration instead of just chatting?”
If it all worked as expected, I wouldn’t feel the need to be here and chat OR express my thoughts but apparently people are to eager to bash others for having a mind of their own it would seem. Look I’ve tried all the versions since owning Mikrotik AX products for the first time this year. And for me they work great for the most part. Clearly there are problems with PMKSA errors and some have reported crashing at thhe same time. So for me using every version those problems would be more profound. If I had a problem where I felt that it was a Special problem then yes I would send a supout.rif file to Microtik but the problem is well known No? For me that problem with those errors have subsided in version 7.10RC1 Is that because logs have been dulled etc.. I don’t know!.
But I am trying. I can get away with doing that because I have nothing to loose. If you wish to prolong… carry on.
Protagonism craze? You are the first to ask why one comments…
If you feel the target of my comments, then you are one of those who do not cooperate in fixing bugs, when they exist.
There is no interesting config to post. Just basic interfaces in bridge to act as an access point, as well as standard NAT routing.
WiFi works, until an hour later, then get all the key-exchange timeouts like in the reddit screenshot. Sat there for an hour messing around turning off WPA3-PSK, PMKID, etc. Nothing would let the clients reconnect. until a reboot.
then 1hr later same again.
been on 7.8 since my post this morning and they have stayed connected.
There are dozens of examples throughout the forum, even on other occasions, where posting the configuration made the difference.
There are dozens of examples throughout the forum, even on other occasions, where the user who doesn’t care to collaborate, especially after certain replies,
is ignored.