Independent Routing Table Entries in One Process

In most situations, each routing daemon process embodies a single routing table entry. Nonetheless, in rare situations one routing daemon process can embody several routing table entries. Each entry defines a separate and independent software router, but without the cost associated with process switching.

This section explores two situations in which multiple routing table entries are appropriate: