diff --git a/_posts/2024-10-29-hosting_at_home.md b/_posts/2024-10-29-hosting_at_home.md index 82dd120..4876dec 100644 --- a/_posts/2024-10-29-hosting_at_home.md +++ b/_posts/2024-10-29-hosting_at_home.md @@ -21,7 +21,7 @@ Before we start, a quick rundown of my setup. I have a FRITZ!Box 6660 Cable (my For my webserver in particular I made a separate and really small (/30) IPv4 subnet with a virtual IP in OPNsense, mostly so this public-facing LXC is in a different network from the VMs and LXCs that are _not_ open to the public. I’ll probably switch that over to a VLAN instead of a virtual IP soon. I feel like this is a bit overkill (and probably doesn’t add that much security anyway), but I wanted to do it anyway. However, this means that my webserver has a static IPv4 in a different network, namely `10.11.10.2/30` with `10.11.10.1/30` being the virtual IP I assigned to the OPNsense installation and it cannot talk to any other VM or LXC. -I don’t want to share the exact IPv6 prefix I get from my ISP, but let’s just pretend it’s `2001:db8:0:e280::/59` where `2001:db8:0:e280::/64` is used by the FRITZ!Box itself and where `2001:db8:0:e291::/64` has been delegated to the OPNsense’s LAN interface. I have assigned a static IPv6 to the LXC which is running my webservers, namely `2001:db8:0:e280::1000:1/128`. +I don’t want to share the exact IPv6 prefix I get from my ISP, but let’s just pretend it’s `2001:db8:0:e280::/59` where `2001:db8:0:e280::/64` is used by the FRITZ!Box itself and where `2001:db8:0:e291::/64` has been delegated to the OPNsense’s LAN interface. I have assigned a static IPv6 to the LXC which is running my webservers, namely `2001:db8:0:e291::1000:1/128`. My webserver is running Caddy and I’m using a module for Caddy called `dns.providers.cloudflare` so that Caddy can create an SSL certificate even when it’s behind Cloudflare’s proxy. diff --git a/_site/2024/10/29/hosting_at_home.html b/_site/2024/10/29/hosting_at_home.html index 96ce95d..692c771 100644 --- a/_site/2024/10/29/hosting_at_home.html +++ b/_site/2024/10/29/hosting_at_home.html @@ -39,7 +39,7 @@
For my webserver in particular I made a separate and really small (/30) IPv4 subnet with a virtual IP in OPNsense, mostly so this public-facing LXC is in a different network from the VMs and LXCs that are not open to the public. I’ll probably switch that over to a VLAN instead of a virtual IP soon. I feel like this is a bit overkill (and probably doesn’t add that much security anyway), but I wanted to do it anyway. However, this means that my webserver has a static IPv4 in a different network, namely 10.11.10.2/30
with 10.11.10.1/30
being the virtual IP I assigned to the OPNsense installation and it cannot talk to any other VM or LXC.
I don’t want to share the exact IPv6 prefix I get from my ISP, but let’s just pretend it’s 2001:db8:0:e280::/59
where 2001:db8:0:e280::/64
is used by the FRITZ!Box itself and where 2001:db8:0:e291::/64
has been delegated to the OPNsense’s LAN interface. I have assigned a static IPv6 to the LXC which is running my webservers, namely 2001:db8:0:e280::1000:1/128
.
I don’t want to share the exact IPv6 prefix I get from my ISP, but let’s just pretend it’s 2001:db8:0:e280::/59
where 2001:db8:0:e280::/64
is used by the FRITZ!Box itself and where 2001:db8:0:e291::/64
has been delegated to the OPNsense’s LAN interface. I have assigned a static IPv6 to the LXC which is running my webservers, namely 2001:db8:0:e291::1000:1/128
.
My webserver is running Caddy and I’m using a module for Caddy called dns.providers.cloudflare
so that Caddy can create an SSL certificate even when it’s behind Cloudflare’s proxy.