You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,6 +35,9 @@ _NOTE: Site-to-site configurations should use allocated IP range `10.70.183.0/24
35
35
5. A volunteer will merge your pull request, you can then [set up your device](https://wiki.nycmesh.net/books/5-networking/page/wireguard-vpn-setup-guide) and start using it.
36
36
37
37
## Add a remote hub config
38
+
IMPORTANT COSTING NOTES:
39
+
- If this is a fully remote node/hub (no OTA mesh connectivity), please use a cost of 100 or more to not cause bridging issues, especially if configuring your node/hub for multiple SNs
40
+
- If this is a VPN backup for an OTA-connected hub, please consult in the #architecture channel or applicable hub channel before setting costs and merging.
38
41
39
42
1. Generate a public private keypair. `wg genkey | tee nn000_privatekey | wg pubkey > nn000_publickey`
40
43
2. Add a new entry to [ansible/wireguard_sn3.yaml](./ansible/wireguard_sn3.yaml) for SN3, or [ansible/wireguard_sn10.yaml](./ansible/wireguard_sn10.yaml) for SN10
0 commit comments