[SOLVED] Block mac address

Started by fox983, October 11, 2015, 02:18:51 PM

Previous topic - Next topic
October 11, 2015, 02:18:51 PM Last Edit: October 13, 2015, 07:22:08 AM by franco
Hi, is there a way to block navigation on wan to a specific mac address? I don't find anything, eg. in firewall rule I can only set an IP address...

AFAIK a MAC address isn't known outside the internal network. Meaning, it's not visible on the internet?
I could be wrong though.
Hobbyist at home, sysadmin at work. Sometimes the first is mixed with the second.

Packet filters normally don't allow filtering below the IP layer[1]. If you still want to do it, you will maybe have luck by modifying the ARP table manually.

[1] https://www.freebsd.org/doc/en/articles/filtering-bridges/article.html

Inside LAN mac address is known and I think it could be possible block or allow navigation through firewall. So through GUI isn't possible to block navigation? Many domestic router have this function. It could be nice also allocate more or less bandwidth, but this is another story  ;D

I was thinking you could use the captive portal MAC filtering and just have no accounts active on the login page?

Captive Portal seems working BUT I think it could be improved: if a user has internet access (without authentication) and I block his mac address, the only way is reboot the firewall, if not  PC continues to navigate. Trying to reboot Pc or Captive Portal with no success... If I reboot firewall, navigation on PC is denied.
Is it possible block navigation without rebooting?
Thank you

And if that person changes the MAC address?
Hobbyist at home, sysadmin at work. Sometimes the first is mixed with the second.

Change IP is easier than change mac address, rather best known...
Obviously changing mac address or IP is the way to bypass the block.

In Captive Portal - Allowed IP addresses is there a way to insert a range of IP instead of a single IP?

Not yet, but I will record this as a feature request for the all new captive portal:

https://github.com/opnsense/core/issues/430