User Tools
device_filtering
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| device_filtering [2023/05/24 21:21] – [ebtables] -changed subhead to ebtables (routed environment) hogwild | device_filtering [2023/05/24 21:30] – [iptables] -condense, formatting hogwild | ||
|---|---|---|---|
| Line 23: | Line 23: | ||
| # Flush (unblock all the defined references at once)\\ | # Flush (unblock all the defined references at once)\\ | ||
| - | NOTE: you might have additional ebtables in your system so be very careful about flushing the full ebtable. | + | NOTE: you might have additional ebtables in your system so **be very careful** about flushing the full ebtable. |
| 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: 2023/05/24 21:38 by hogwild
Page Tools
