Site Tools


device_filtering

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
device_filtering [2025/03/03 17:55] – [Block devices via script/Scheduler] hogwilddevice_filtering [2025/03/03 18:09] (current) – [Notes] -condense hogwild
Line 45: Line 45:
  \\  \\
  
-# Flush\\  ''You don't do that for iptables '':-)'' instead, reboot the device''+# Flush\\  You don't do that for iptables. Reboot the device instead.
  
  \\  \\
Line 51: Line 51:
  \\  \\
  
-Nowadays, blocking MAC addresses can be tedious. Many devices use MAC randomization. MAC addresses can "change" freqeently.+These daysmany devices use MAC randomization which can make blocking MAC addresses tedious. MAC addresses can "change" frequently.
  
-For managing this, one alternative is to filter using hostnames.+To help manage this, one option is to filter using hostnames.
  
  \\  \\
Line 66: Line 66:
  
  \\  \\
 +
  
 ===== Notes ===== ===== Notes =====
  
-The kernel still resolves the hostname to an IP address. A device with randomized MAC address will obtain a new IP address when reconnecting. This might function well, but only until the user restarts the device or just manually disconnects WiFi.+The kernel still resolves the hostname to an IP address. A device with randomized MAC address will obtain a new IP address when reconnecting. This may function well, but only until the user restarts the device or manually disconnects WiFi.
  
 If you're security conscious, you could trigger a "service wireless restart" for each new client connecting, but that would be disruptive to the general network. If you're security conscious, you could trigger a "service wireless restart" for each new client connecting, but that would be disruptive to the general network.
device_filtering.1741024536.txt.gz · Last modified: 2025/03/03 17:55 by hogwild