Existing Neighbor Interfaces

The first part of this page is a table of existing neighbor interfaces—that is, interface specifications for potential neighbor connections to other routers.

Figure 108: rvrd Neighbor Interfaces Page—Existing

Item

Description

existing neighbor interfaces

The upper table lists configured neighbor interfaces. Each row represents one potential neighbor.

Interface ID

The name of this neighbor interface. rvrd generates this name automatically, incorporating the router name.

Local Endpoint

This three-part string denotes the local end of the potential neighbor link. It has the form:

    router_name@host:TCP_connect_port
• router_name is the name of the local routing table entry.
• host is a fixed token, local_host, which denotes the local rvrd host computer. (Note that this token does not denote the LOCALHOST loopback network address.)
• TCP_connect_port is the TCP port where the local router accepts neighbor connection requests from remote routers.

Remote Endpoint

This three-part string denotes the remote end of the potential neighbor link. It has the form:

    router_name@host:TCP_connect_port
• router_name is the name of the remote routing table entry.
• host is the hostname or IP address of the remote rvrd host computer.
• TCP_connect_port is the TCP port where the local router attempts to connect to remote routers.

The token Any can appear in these three parts. For the semantics of this notation see Accept Any as Neighbor, and Seek Neighbor with Any Name. See also, Four Variations of the Form.

Features

This column lists optional features of this neighbor specification:

• Cost: the path cost of this neighbor link (see Load Balancing)
• Compression: this flag indicates whether this interface specifies data compression (see Data Compression)
• SSL: this flag indicates whether this interface requires a TLS connection (see SSL Connection with Compression)

See Also

Router Name