04-17-2019 11:25 AM
Hi all,
Previously, we have a controller and using MAC filter to allow only the added object MAC addresses to join the SSID.
But there is a limitation that only 256 objects are already supported.
Can I use "MAC firewall object" and have the AP firewall policy to achieve the same purpose but support more than 256 clients?
Also, what is the different between Mac filter and MAC Firewall?
Solved! Go to Solution.
04-25-2019 09:54 AM
Of course, here is the guide we have for setting up MAC authentication in Classic. HiveManager (formerly NG) is a separate platform from Classic, just for future reference.
https://thehivecommunity.aerohive.com/s/article/MAC-Authentication-Set-Up
04-25-2019 09:54 AM
Of course, here is the guide we have for setting up MAC authentication in Classic. HiveManager (formerly NG) is a separate platform from Classic, just for future reference.
https://thehivecommunity.aerohive.com/s/article/MAC-Authentication-Set-Up
04-25-2019 04:17 AM
Yes, is also ok to use Radius for the authentication.
Might I have the configuration guidance for Classic NG?
Appreciate if also an example to show how to setup MAC in a Radius, assume using Windows server 2012 R2 as Radius.
04-18-2019 04:09 PM
The maximum firewall rule limit is going to be 64 rules. The difference between a MAC filter and a MAC firewall is that the MAC filter screens authentication requests from client devices to the AP, where MAC firewall screens the traffic sent by the clients associated to the AP already.
You could set up MAC authentication to only allow devices with pre-approved MAC addresses to connect to your network, does that sound like what you're looking for? This guide reviews how to do that: https://thehivecommunity.aerohive.com/s/article/Radius-SSID-in-NG
I wouldn't recommend using the APs for extensive MAC filtering or firewall purposes; if there are large filtering needs, then a network firewall would be better at managing that.