Acting As a Proxy
The section "Proxying the Neighboring Protocol" in Chapter 26 described why proxies are useful and gave a few examples of their use. It also showed the criteria by which neighboring protocols decide whether a given solicitation request is taken care of by the proxy. This section goes into detail on the implementation of proxying .
We saw in the section "Conditions Required by the Proxy" in Chapter 26 that two kinds of proxying can be configured: a host either can proxy all requests received on a particular NIC (per-device proxying) or, more selectively, can proxy requests for a particular address received on a particular NIC (per-destination proxying).
The precedence shown in Figure 26-8
in Chapter 26 is enforced in protocol-specific
code. ARP's implementation is shown in Chapter
28, and you can look at the routine neigh_recv_ns for IPv6's implementation. The section "Per-Device Proxying and Per-Destination
Proxying" also goes into more detail about these two types of proxying.
Before digging into the code, let me introduce a naming convention used extensively
there. The neighboring subsystem contains pairs of functions and data structures whose
names differ only in the presence or absence of an initial p (e.g., neigh_lookup versus pneigh_lookup). The p stands for
proxy. Because addresses intercepted by proxies are handled
differently, there is a dedicated set of functions to manipulate them.
Delayed Processing of Solicitation Requests
Solicitation requests handled ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access