User Tools
device_filtering
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| device_filtering [2023/05/24 21:22] – [ebtables (routed environment)] hogwild | device_filtering [2023/05/24 21:38] – [Block devices via script/scheduler] - Capitalize Scheduler hogwild | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Block devices via script/scheduler | + | ====== Block devices via script/Scheduler |
| The easiest way to filter WiFi devices is to use the [[basic-wfilter|Wireless Filter]] menu. However, there are times when you want to block specific devices via a script. This is particularly true when you need to manage device blocking for a lot of devices. Scripting also allows you to schedule blocking/ | The easiest way to filter WiFi devices is to use the [[basic-wfilter|Wireless Filter]] menu. However, there are times when you want to block specific devices via a script. This is particularly true when you need to manage device blocking for a lot of devices. Scripting also allows you to schedule blocking/ | ||
| Line 36: | Line 36: | ||
| \\ | \\ | ||
| - | # Unblock | + | # Unblock |
| \\ | \\ | ||
| Line 60: | Line 60: | ||
| \\ | \\ | ||
| - | Still, the hostname is resolved into an IP address by the kernel. A device with randomized MAC address will obtain a new IP when reconnecting. This will probably | + | Still, the hostname is resolved into an IP address by the kernel. A device with a randomized MAC address will obtain a new IP address |
| - | You could as a paranoia approach | + | If you were very security conscious, you could trigger a "service wireless restart" |
| + | |||
| + | For WiFi devices, perhaps | ||
device_filtering.txt · Last modified: by hogwild
Page Tools
