Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
There’s no exact replacements, and the actual model numbers will vary depending on the Meraki access point you’re using. Assuming you are planning to use an MR46E then…AIR-ANT2524DW-R => MA-ANT-3-B6Just as you concluded, the are dipoles with an arti...
Clients have to support OWE to make use of it. I haven’t implemented OWE yet, but I’m wondering whether what you’re seeing is Meraki presenting you with both an OWE enabled SSID (the one with a lock), and an open SSID (the one without the lock). This...
Yep, with the randomised MAC addresses that are used by virtually every OS now, this is hard to implement. You have to flip it on its head and ensure you are only permitting the devices you want to access your network, and block everything else.
Assuming these are all /24 subnets the the 192.168.20.99 device shouldn’t be ARPing for 192.168.100.253, it should be ARPing for the gateway address. I’d get the subnet mask and default gateway configuration on 192.168.20.99 checked.
Yes this should work fine. Note that the PAT that The MX performs will always use the address assigned to the WAN interface. The addresses in the additional /29 can be used to 1:1 NAT, or 1:many NAT configured through the Dashboard.
