An RBridge registry is a third party which helps to find the communication peer for RBridges wishing to establish a link in the case that the mutual communication parameters are unknown. An RBridge registry listens on port 439 accepting DASP registry request packets and sending DASP registry reply packets back.
Operating RBridge in registry mode requires no licensing.
Starting an RBridge registry with default public parameters
This is very easy: Just install RBridge on your system which needs to be directly reachable over IPv4 and IPv6 (with no NAT devices in between). Then, type “rbridge start” with super user permissions as follows:
$ sudo rbridge start RBridge: this is a registry, no license required RBridge: going to background ... $
Since there’s no RBridge configuration file present, RBridge starts in registry mode using “PUBLIC” as the default authentication and encryption disabled.
Starting an RBridge registry with custom authentication and encryption
If you would like to have specific authentication and encryption parameters for your registry communication, you need to create the file /etc/rbridge.conf and include the credentials as needed.
$ cat /etc/rbridge.conf registry_macsecret= "my-registry-authentication-secret" registry_key= "my-registry-encryption-key" $
Afterwards just start or restart RBridge as above.
Starting an custom RBridge listening on a different port
This example makes the RBridge listen on the user port 20000 (using the same authentication end encryption parameters as in the example before).
$ cat /etc/rbridge.conf local_port= 20000 registry_macsecret= "my-registry-authentication-secret" registry_key= "my-registry-encryption-key" $
Starting RBridge automatically on reboot
If you wish to start your RBridge registry automatically on reboot you need to edit the crontab for root with “crontab -e” as follows:
@reboot sleep 30; /sbin/rbridge start
The only thing that may vary is the location of the rbridge binary, if unsure where it actually sits just execute a “which rbridge” as root.