Add manual local network configuration following the problems with ifupdown
This commit is contained in:
parent
97d1845f81
commit
9e3aad87c8
@ -7,7 +7,7 @@ General:
|
||||
- Every service that needs data storage needs a volume to back it
|
||||
|
||||
ifupdown-ng:
|
||||
- Public networks should be configured manually since RAs aren't usually configured
|
||||
- Public networks should be configured manually since RAs aren't usually configured, private ones also shouldn't rely on the rather unstable DHCP
|
||||
``` HETZNER EXAMPLE
|
||||
auto eth0
|
||||
iface eth0 inet static
|
||||
@ -21,12 +21,14 @@ ifupdown-ng:
|
||||
netmask 64
|
||||
gateway fe80::1
|
||||
```
|
||||
- Private networks need this workaround for routing to work properly
|
||||
```
|
||||
auto eth1
|
||||
iface eth1 inet dhcp
|
||||
up ip route add 10.0.0.0/16 via 10.0.0.1 dev eth1
|
||||
post-up ip route del default via 10.0.0.1 dev eth1
|
||||
iface eth1 inet static
|
||||
address 10.0.X.X
|
||||
netmask 255.255.255.255
|
||||
mtu 1450
|
||||
pointopoint 10.0.0.1
|
||||
post-up ip route add 10.0.0.0/16 via 10.0.0.1 dev eth1
|
||||
```
|
||||
Yggdrasil:
|
||||
- Yggdrasil needs manual configuration for peers and whitelisting
|
||||
|
Loading…
Reference in New Issue
Block a user