It seemed to stay right between 17 and 18 M.Its it stuck @18.1MB? I use these devices at a site and the traffic seems to be stuck and does not change
It seemed to stay right between 17 and 18 M.Its it stuck @18.1MB? I use these devices at a site and the traffic seems to be stuck and does not change
I messaged them last month about it... Nothing.I guess you need to update your support ticket as well.
Because the barn has a wAP 60G AP so it can serve MULTIPLE antennas that are all less than 500 Meters away.Why not use SXT AC units?
I contacted support and they sent it to me.what version firmware ?I have the exact same problem.
I got a beta firmware that makes the glitch take longer.
today at 98 days... it hit me again.
where I can find ?
thanks
It doesn't address that token thing on hosts table.A FW version which was given in november 2024 or earlier and still not released ?
Now that's odd ...
I would have to move the caps-controller off my router. Not that big a deal but I would need to rebuild on a router and make it a controller only.You might want to give v7.18RC1 a try.
When your old router comes back... it still has the config for the caps. That's the point.I actually did move the wAP and it worked just fine with a different CAPsMAN instance even without resetting.
I didn't want to reset because eventually my old router will be put back.
Downloading the drivers to it now.Load wifi-qcom-ac drivers on it and then redo your tests.
They offered to cut down trees. I said you may need to trim.Good. So the problem won't happen in Spring of 2025, it'll happen in Spring of 2026
Why didn't you go with the cap?Soo... Good thing I ordered 3 of them... one to each room i want to cover with wifi...
This switch has been on for 7 months+Maybe take a backup and reinstall the SWoS version? Or perhaps there's a bad config somewhere? I've still had no issues and the switch has been up for 136 days.
I have to say... I really like how these guys include the antenna test result patterns.Sorry about the specs, yes, there were some mistakes, we will / have corrected them. In the PDF we always try to include more information, so I suggest always opening those files too.
How far are you trying to go?I am more worried about the low 2.4ghz coverage.
So we are sure THIS TIME?I can confirm that the issue has been fully resolved. It took some time, though..
It's a reminder the daily "blink the radios". Was still needed after switching to the new radio drivers.Is this a wireless or wifi story?
Remember... this is my job.
WAP AX coming soon
Considering the "features" and "quirks" a long with the actual radio performance...Where is the wAP AX???
The cost doesn't matter at all, if the thing doesn't work.But hardware costs explode for supporting an POE standard according to Normis stated somewhere in this forum. Yep, a decision to make: loose professional customers or raise retail price by 5$....
Yeah that never worked before. You need to enter the MAC address that ties to that Access list PSK.MAC address is not mandatory. Tried that recently. Created an entry with just passphrase and SSID and I was able to connect using that passphrase.
Except that with EPSK... you can set the password and let devices connect.access list entry with a passphrase and vlan-id is pretty much what other vendors advertise as PPSK?
That would be the OUTDOOR WiFi6 Access Point that matches up with the Indoor units I have used since 2021.Gave up on waiting a long time ago...
What is the big box?
https://www.wireguardconfig.com/qrcodeYes, do you want to skype, discord, teamviewer. nothing but the best for you!!
well they were covered in soot at one point.![]()
![]()
Now paint the antennas black or the same color as the wood.
Remind me how the wifi 6 release went.If they don't have to wrie their owns drivers now, I guess everything will be smoother ?
Gonna go with the LHG 60G for my next install over 200 Meters.Is Mikrotik recalling these clearly defective products from distributors? When will these be safe to purchase?
Shoot... the hEX does... So I was "hoping".It is not in the spec nor block diagram so I would conclude there is no beeper.
The reason its complete BS... it worked despite the documentation.I dont know whether to be humbled or amused LOL.
If you are saying I have uncanny powers to spot useless posts, then I am humbled.
If you are saying, I have a unique propensity to dish out vacuous posts, then I am amused.![]()
When is this going to be fixed?We bought 8 of these switches and had the same issue on one of them. We RMA it and the replacement did not have this problem with identical config. I'd contact support in the first instance.
Compared to the Droorstop CRS354, That drops a bank of ports every soften for 4 years at this point.That is a 24-port pizza box.What I need.. is a RouterOS version of this.
https://www.fs.com/products/108716.html
For the record... I did not recommend that.Ok thanks for the tips. I should have bought the ax3 then... :/
Looking for "Does" not interested in "should".Have you guys tried 7.13.1? Those switch changes should fix the CRS354 issues described in the topic
But it's about one the Frequencies needed for 7.
This BaseBox 6 is from 2019 or even 2018. Far from Wifi 7.
Out of NOWHERE!!!@PG, MT has been busy over the past (seems like a century) year or two, modernizing their WIFI setup in RoS and thus the transition for them to adopt WIFI7 should be relatively smooth.
Was that on the switch or the router?I've first seen this issue myself after upgrading to 7.14. Wireless clients could connect to AP but stuck on DHCP. After downgrade to 7.13.5 it was resolved.
Exactly what I mean!You mean the same link from post #2 ?
RainX Spray?Yeah normis, I can agree, that even smooth surface woun't help
BUT, that is the answer I was looking forthanks woland
I was wondering for myself to apply some kind of waterfobic coating