adyxax/www
1
0
Fork 0
Code Issues Pull requests Activity Actions

Updated old docs articles

Browse source
This commit is contained in:
Julien Dessaux 2022-04-30 23:05:01 +02:00
parent d8dfaa1796
commit fd5e65b5c3
Signed by: adyxax
GPG key ID: F92E51B86E07177E
3 changed files with 25 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

2
content/docs/freebsd/remote_install.md
View file

@ -18,7 +18,7 @@ wget https://download.freebsd.org/ftp/releases/VM-IMAGES/13.0-RELEASE/amd64/Late
```
When all is done, force a reboot of your machine and connect to the remote console. Your FreeBSD system should boot and leave you with an authentication prompt. Just type in root (it will not ask for a password) and go through this post installation checklist :
- run `freebsd-update fetch install`
- run `freebsd-update fetch install` then reboot
- set a root password with `passwd`
- add a user account with `adduser`, put it in the `wheel` group
- add a ssh authorized_keys for your new user

2
content/docs/freebsd/wireguard.md
View file

@ -42,7 +42,7 @@ AllowedIPs = 10.1.2.9/32
PersistentKeepalive = 60
```
To implement this example you will need to generate two sets of keys. The configuration for the first server will feature the first server's private key in the `[Interface]` section and the second server's public key in the `[Peer]` section, and vice versa.
To implement this example you will need to generate two sets of keys. The configuration for the first server will feature the first server's private key in the `[Interface]` section and the second server's public key in the `[Peer]` section, and vice versa for the configuration of the second server.
This example is from a machine that can be hidden behind nat therefore I configure a `PersistentKeepalive`. If your host has a public IP this line is not needed.