Hey guys,
Our volunteers have updated all five router VMs to the
latest OPNsense firmware release. It doesn’t appear to
have broken anything, but as always, let us know via the
support desk if anything isn’t working correctly.
One of the things we really wanted to focus on but was just a bit
outside of our knowledge was being able to route entire IPv6 subnets
to our project members in the form of a site-to-site tunnel. For a
while now, our project members have been making use of our services
directly on their devices on an as needed basis, which while do
offer such, that was never the intended purpose of the project.
The idea has always been to route out a subnet to be used on the
LAN side of a homelab router. We reached that milestone after
having a few days to sit down and crawl the OPNsense and WireGuard
documentation pages.
Last night, we finally figured out how to get WireGuard setup between
two routers, on different physical servers, and route a /64 subnet
across the tunnel. This has been one of our goals for the project and
we figured it out. Along with the better understanding of the peer
based connections in WireGuard, we should be able to start offering
fully routed subnets within a few days.
Just have to finish publishing the documentation internally for our
volunteers and project members to make use of.
Our team has opted to bring back legacy OpenVPN support
for devices which do not support WireGuard properly.
With the latest updates to OPNsense, managing OVPN has become
a fair bit easier and we are able to offer NAT’d IPv4 and
IPv6 support with these connection profiles.
Network speeds over OVPN are much, much slower than our
WireGuard speeds. Just something to keep in mind if you
decide you need legacy connectivity.
If you need OVPN support for your homelab or older device,
reach out to our support desk and let them know.