(If you don't believe me, go ahead and test it out.
#Dell sonicwall blacklist mac address windows#
It's also useless for Windows: Windows devices will happily accept the assigned IPv6 address, and promptly use a different IP address for outgoing traffic.
#Dell sonicwall blacklist mac address android#
Oh, but what about DHCPv6 and static reservations there? Go ahead and boot up an android device and see if your android device uses the "reservation." Android completely ignores DHCPv6. Either my device will use IPv6 by default, or will fall back to trying to use IPv6 when IPv4 fails to work out.
When I go to "", my machine is resolving the name to an ipv6 address and the traffic is flowing over the ipv6 "address family." I can block IPv4 addresses until I'm blue in the face, but it won't help unless I'm going to some website that's 5 years behind the times and hasn't started IPv6 migration. That point aside, however, assigning an IP address with DHCP and using that for filtering is USELESS with modern devices on modern networks. A quick google of "purpose of DHCP" reveals a first hit from University of California, Davis that states (in part): DHCP's purpose is to enable individual computers on an IP network to extract their configurations from a server (the DHCP server) or servers, in particular, servers that have no exact information about the individual computers until they request the information. I've never seen anyone actually gain any traction in trying to get MAC address rules supported, however.Ĭonsider that the purpose of DHCP is not to create a new reservation for every single client that might connect. Some reference ipfw (which isn't supported in the pfSense UI.) I've even seen (oddly) people suggesting static ARP tables, making every potential client known, and with a DHCP reservation. They also sometimes try to help by suggesting that DHCP reservations should be made against the MAC addresses and firewall rules applied to the IP addresses. The reasonable ones suggest that pfSense isn't an L2 device, so shouldn't be messing with MAC addresses. Usually, when someone asks if this could be implemented, it seems that the responses vary between people trying to be reasonable, and those who just attack. I did a search, and it seems that MANY before me have asked about pfSense having some kind of firewall rules based on MAC addresses (in addition to those based on IP addresses.) In all those cases, it was revealed that pfSense isn't capable of such a basic feature.
0 kommentar(er)
