When Solicitation Requests Are Transmitted and Processed
In this section, we will see when a solicitation request is processed, based on the configuration of the receiving host and the physical topology of the network. Figure 26-9 covers the factors that lead a host to send out a solicitation request, and Figure 26-10 shows the most-common factors that determine whether a request is processed by the Linux host that receives it. To show the potential complexity of the recipient's decision, Figure 26-10 assumes that the recipient implements both proxying and bridging[*]; removing either of these features would simplify the flowchart. Figure 26-10 also assumes device-based proxying; destination-based proxying is similar, but leaves out a step. Note that Figure 26-10 shows both the case of a proxy server and the case of a common host that does not implement any proxying: "proxy enabled" denotes a proxy server, and "proxy disabled" denotes a common host.

Figure 26-9. Transmitting solicitation requests
This is a protocol-independent analysis; particulars about ARP are shown in Chapter 28.

Figure 26-10. Processing ingress solicitation requests
When bridging is enabled, solicitation requests are not processed by the receiving host, but are instead forwarded (bridged) to the right interfaces according ...
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