Open topic with navigation

TIBCO Rendezvous® 8.8.0

# Add New Neighbor Interface

The remainder of this page lets you complete a form to specify a new neighbor interface.

Figure 110: rvrd Neighbor Interface Configuration Form

## Four Variations of the Form

Four buttons rearrange the form into four variations, each with a different meaning. In each variation, `rvrd` automatically fills in some fields, and leaves others empty for you to fill.

Four Neighbor Interface Configuration Forms

Item | Description
Accept Any | Use this variation of the form to specify a neighbor interface in which this routing daemon accepts neighbor connections from any other routing daemon. A distinguishing characteristic of accept any neighbors is a remote endpoint string in which the router name, the host and the port are all Any. Restrictions:
| • | It is not possible to configure more than one accept any neighbor interface.
| • | Accept any interfaces cannot use TLS neighbor connections.
| • | Border routers cannot configure an accept any neighbor interface.
For more information, see Accept Any as Neighbor.
Passive | Use this variation of the form to specify a neighbor interface in which the local router does not actively attempt to connect to the remote neighbor. Instead, it passively waits for the remote neighbor to request a connection. A distinguishing characteristic of passive neighbors is a remote endpoint string in which the router name is specified, but the host and port are Any. For more information, see Passive Neighbor.
Active | Use this variation of the form to specify a neighbor interface in which the local router actively attempts to connect to the remote neighbor. A distinguishing characteristic of active neighbors is a remote endpoint string in which the router name, the host and the port are all specified. For an example, see Active Neighbor.
Seek Any | Use this variation of the form to specify a neighbor interface in which this routing daemon attempts to connect to any remote routing daemon that matches the specification. A distinguishing characteristic of seek any neighbors is a remote endpoint string in which the router name is Any, but the host and the port are specified. In addition, the local endpoint port is Any. Restrictions:
| • | It is illegal to configure two or more seek any neighbor interfaces with the same host.
| • | Seek any interfaces cannot use TLS neighbor connections.
| • | Border routers cannot configure a seek any neighbor interface.
For more information, see Seek Neighbor with Any Name.

## Items in the Neighbor Interface Configuration Form

This table describes the items in rvrd Neighbor Interface Configuration Form.

Item | Description
Local Endpoint | This three-part specification denotes the local end of the potential neighbor link:
| • | Router Name is the name of the local routing table entry. `rvrd` always automatically fills in this name.
| • | Host is a hostname or IP address corresponding to a network interface in the local `rvrd` host computer. For convenience, `rvrd` automatically fills in this field with the fixed token, `local_host`, which denotes the default network interface of the local `rvrd` host computer. (Note that this token does not denote the `LOCALHOST` loopback network address.) You may override this default value by typing an alternate hostname or IP address.
| • | Port is the local TCP port where the local router accepts neighbor connection requests from remote routers. For more information, see Local Connect Port.
Remote Endpoint | This three-part specification denotes the remote end of the potential neighbor link:
| • | Router Name is the name of the remote routing table entry.
| • | Host is the hostname or IP address of the remote `rvrd` host computer.
| • | Port is the remote TCP port where the local router attempts to connect to remote routers.
For more information, see Remote Connection Information.
Normal Connection | With this option, the two neighbors neither compress data nor use TLS protocols for communication on the link between them.
Data Compression without SSL | With this option, the two neighbors compress data on the link between them. To enable compression, you must select this option on both neighbors. For more information, see Data Compression.
SSL Connection with Compression | With this option, the two neighbors communicate using both compression and TLS protocols. To enable TLS, you must select this option on both neighbors—otherwise they cannot establish a connection. This option appears only in the Passive and Active variations of the configuration form. Connection statistics are not available when neighbors connect using TLS. See also Router Connection Statistics. In older releases of the routing daemon, TLS and compression are mutually exclusive features. For backward compatibility with older neighbors, this feature degrades gracefully to TLS without compression.
Certificate of Expected Peer | In TLS protocols, the local router expects the remote router to present this certificate as evidence of its identity. Paste the text of the public certificate (in PEM encoding) in this field. This field appears only in the Passive and Active variations of the configuration form.
Cost | The path cost of this neighbor link (see Load Balancing).

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO Rendezvous®

Copyright © 1997-2025. Cloud Software Group, Inc. All Rights Reserved.