Seek Neighbor with Any Name

Instead of declaring a neighbor with a specific name, a routing daemon can seek out any available member from a set of routing daemons, without regard to its name.

This configuration is especially useful for load balancing among a set of potential neighbors with identical routes.

Specify the potential neighbors with two pieces of information:

•

Remote Host, which must be either a DNS hostname that can resolve to more than one IP address, or a virtual IP address.

•

Remote Connect Port—all potential neighbors must listen for connection requests on this port).

Each potential neighbor must accept connections from the seeking routing daemon, without actively attempting to connect to it. The potential neighbors can specify this in either of two ways:

•

Accept connections from any neighbor, including the seeking routing daemon (see Accept Any as Neighbor).

•

Passively accept connections specifically from the seeking routing daemon (see Passive Neighbor).