|
Yeah go ahead and do it. I’ve had no problems running v7+ for a year now.
|
#
?
May 13, 2023 01:18
|
|
|
|
| # ? Apr 25, 2024 17:14 |
|
|
I've run into one or two weird third-party interactions with the 7.x stuff i use at work but it's mostly just "idk i have to specify something i didn't have to before" and honestly it might also be because those ones have complicating factors unrelated to being 7.whatever
|
|
#
?
May 13, 2023 01:20
|
|
|
It's happened again, the same totally poo poo engagement with security disclosures as the last time they had a huge IPv6 bug. https://blog.mikrotik.com/security/cve-2023-32154.html
|
|
#
?
May 22, 2023 10:52
|
|
|
Mikrotik: hey at least it only takes like 26 seconds to reboot on an update! … that we hope you know you need to do asap
|
|
#
?
May 22, 2023 20:03
|
|
|
Since my experiences with Mikrotik disclosures hasn't been terrible (they seem to address vulns in reasonable time frames when they are aware of them) is there any particular reason I should doubt their claim that they weren't present at the event to receive the disclosure from ZDI?
|
|
#
?
May 22, 2023 22:52
|
|
|
alyandon posted:Since my experiences with Mikrotik disclosures hasn't been terrible (they seem to address vulns in reasonable time frames when they are aware of them) is there any particular reason I should doubt their claim that they weren't present at the event to receive the disclosure from ZDI? I know nothing of this situation. My guess is that someone was there, but not in an official capacity, and that person was notified. Whether or not that 'counts' is up to you I guess and again, that's wild speculation.
|
|
#
?
May 22, 2023 23:02
|
|
|
After debating for a bit, I finally converted half my network to use the new wifi-qcom-ac drivers so now I get two CAPsMANs running amok. Challenges faced 1) Removing the wireless package and adding wifi-qcom-ac completely borks the QuickSet functionality, I had to manually configure the access points to put them into a functional CAP mode 2) Totally having to rework the dB levels I use for the Access Lists -- the new drivers required different signal ranges than legacy CAPsMAN. 3) Subjectively it feels like roaming is worse despite setting up steering, may need to keep tweaking things. At least now I'm all set if I ever decide to start adding AX hardware, assuming I stick with Mikrotik's products.
|
|
#
?
Jan 4, 2024 23:40
|
|
|
This might seem like a stupid question, but can I easily give clients a hostname that resolves to their IP address? I have a hEX S. Is it possible in WinBox? I assumed it would be in the DHCP settings but that only displays the hostname broadcast by the device. I usually just use multicast DNS but been having some issues with it recently, seeing as I have this complicated router seems to make sense to do it on there instead Generic Monk fucked around with this message at 22:41 on Feb 20, 2024 |
|
#
?
Feb 20, 2024 22:38
|
|
|
You can set static DNS entries in the DNS server. That should do what you want.
|
|
#
?
Feb 20, 2024 22:47
|
|
|
And if it wasn't made obvious in the docs, this would require your clients to be using the Mikrotik router as a DNS resolver
|
|
#
?
Feb 20, 2024 22:55
|
|
|
I believe there are some sample scripts that will do that and set DNS off of the asserted host name for you
|
|
#
?
Mar 11, 2024 12:36
|
|
|
Getting into MikroTik WiFi. Grabbed a cAP AX and I've got it configured through CAPsMAN and broadcasting successfully, but there's a lot of settings that I haven't touched (or tried to touch and broke) and leaving most everything as an unlisted Default makes me worried that I'm not properly securing my setup. Is there a best practices or hardening guide that would be good to follow?
|
|
#
?
Apr 1, 2024 15:23
|
|
|
|
| # ? Apr 25, 2024 17:14 |
|
|
Actuarial Fables posted:Getting into MikroTik WiFi. Grabbed a cAP AX and I've got it configured through CAPsMAN and broadcasting successfully, but there's a lot of settings that I haven't touched (or tried to touch and broke) and leaving most everything as an unlisted Default makes me worried that I'm not properly securing my setup. I don't really have any experience with MikroTik wifi gear - but assuming it runs routerOS you can follow the same general guidance from here: https://help.mikrotik.com/docs/display/ROS/Securing+your+router The short answer is - if you are upgraded to the latest firmware and used the defaults that came with that you should be pretty safe. Just don't do something bone-headed like expose the management interface to the internet. alyandon fucked around with this message at 20:46 on Apr 4, 2024 |
|
#
?
Apr 4, 2024 20:43
|
|