User Tools
device_filtering
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| device_filtering [2024/10/31 20:43] – [Block devices via script/Scheduler] add full bridged mode names hogwild | device_filtering [2025/03/03 18:09] (current) – [Notes] -condense hogwild | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| \\ | \\ | ||
| - | * For a bridged environment (when using Media bridge | + | * For a bridged environment (Media |
| - | * For a routed environment (single router), you'll use // | + | |
| \\ | \\ | ||
| - | Given a MAC address you wish to control, | + | * For a routed environment (single router), you must use // |
| + | |||
| + | \\ | ||
| + | |||
| + | Given a MAC address you wish to control, | ||
| Line 42: | Line 45: | ||
| \\ | \\ | ||
| - | # Flush\\ | + | # Flush\\ |
| \\ | \\ | ||
| Line 48: | Line 51: | ||
| \\ | \\ | ||
| - | Nowadays, blocking MAC addresses | + | These days, many devices use MAC randomization which can make blocking MAC addresses tedious. MAC addresses can " |
| - | For managing | + | To help manage |
| \\ | \\ | ||
| Line 63: | 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 " | If you're security conscious, you could trigger a " | ||
device_filtering.1730407415.txt.gz · Last modified: by hogwild
Page Tools
