| Commit message (Collapse) | Author | Files | Lines | ||
|---|---|---|---|---|---|
| 2023-04-15 | hosts/carmel: don't release DHCP lease on wan interface | Franck Cuny | 1 | -0/+3 | |
| No need to release the lease if we are rebooting. | |||||
| 2023-04-05 | hosts/carmel: the wireguard interface is trusted | Franck Cuny | 1 | -1/+1 | |
| 2023-04-05 | hosts/carmel: add wireguard key | Franck Cuny | 1 | -0/+1 | |
| 2023-04-05 | hosts/carmel: drop checkReversePath | Franck Cuny | 1 | -3/+0 | |
| This is managed in the tailscale module. | |||||
| 2023-04-05 | hosts/carmel: enable tailscale | Franck Cuny | 1 | -0/+2 | |
| 2023-04-03 | hosts/carmel: reconfigure the host as a router | Franck Cuny | 1 | -20/+97 | |
| I'm not using it as a desktop, and the current router is getting old and will likely fail in the near future. It's also a debian machine configured manually, so let's reconfigure carmel as our new router. There are three NICs in the host: 2 are 10Gb and one is 1Gb. The 1Gb will be used as the upstream interface, and one of the 10Gb will be for the LAN. There are 2 VLANs to configure: one for IoT devices and one for guest. | |||||
| 2022-04-05 | refactor network configuration | Franck Cuny | 1 | -1/+19 | |
| 2022-04-05 | network: move tailscale in modules | Franck Cuny | 1 | -0/+17 | |
| Move the networking configuration for the hosts to its own file. | |||||
