![]() |
![]()
| ![]() |
![]()
NAME
SYNOPSIS
DESCRIPTIONThe The optional [explain] and [verbose] options can be used to obtain further help or to enable a detailed view on the operations, respectively. COMMANDS
EXIT STATUSThe EXAMPLESIn this example, we will assume that the server has an interface bound to 192.168.0.1, that accepts incoming connections on port 9999/UDP for Rosenpass and port 10000/UDP for WireGuard. To create a VPN connection, start by generating secret keys on both hosts. rp genkey server.rosenpass-secret rp genkey client.rosenpass-secret Extract the public keys: rp pubkey server.rosenpass-secret server.rosenpass-public rp pubkey client.rosenpass-secret client.rosenpass-public Copy the "-public" directories to the other peers and then start the VPN. On the server: sudo rp exchange server.rosenpass-secret dev rosenpass0 listen 192.168.0.1:9999 \ peer client.rosenpass-public allowed-ips fe80::/64 On the client: sudo rp exchange client.rosenpass-secret dev rosenpass 0 \ peer server.rosenpass-public endpoint 192.168.0.1:9999 allowed-ips fe80::/64 Assign IP addresses: sudo ip a add fe80::1/64 dev rosenpass0 # Server sudo ip a add fe80::2/64 dev rosenpass0 # Client Test the connection by pinging the server on the client machine: ping fe80::1%rosenpass0 # Client You can watch how rosenpass replaces the WireGuard PSK with the following: watch -n 0.2 'wg show all; wg show all preshared-keys' SEE ALSOAUTHORSRosenpass was created by Karolin Varner, Benjamin Lipp, Wanja Zaeske, Marei Peischl, Stephan Ajuvo, and Lisa Schmidt. This manual page was written by Emil Engler BUGSThe bugs are tracked at https://github.com/rosenpass/rosenpass/issues.
|