4.4. Protocols Below IP
It's theoretically possible to filter
on information from below the IP level -- for example, the
Ethernet hardware address. However, doing so is very rarely useful
because in most cases, all packets from the outside are coming from
the same hardware address (the address of the router that handles
your Internet connection). Furthermore, many routers have multiple
connections with different lower-level protocols. As a result, doing
filtering at lower levels would require configuring different
interfaces with different kinds of rules for the different
lower-level protocols. You couldn't write one rule to apply to
all interfaces on a router that had two Ethernet connections and two
FDDI connections because the headers of Ethernet and FDDI packets,
while similar, are not identical. In practice, IP is the lowest level
protocol at which people choose to do packet filtering.
However, if you are dealing with a network with a small, fixed number
of machines on it, filtering based on hardware addresses is a useful
technique for detecting and disabling machines that have been added
inappropriately. (It is also a useful technique for making yourself
look like an idiot when you exchange network boards, and an important
machine suddenly and mysteriously stops working -- better document
it very carefully.) Even on relatively large networks, setting alarms
based on hardware addresses will notify you when machines are changed
or added. This may not be obvious based on IP address alone, since
people who add new machines will often reuse an existing IP address.
Filtering based on hardware addresses is not a reliable security
mechanism against hostile insiders. It is trivial to reset the
apparent hardware address on most machines, so an attacker can simply
choose to use the hardware address of a legitimate machine.
| | |
4.3. Protocols Above IP | | 4.5. Application Layer Protocols |