Having a bit of a headache trying to get wireguard working properly through my pfsense router.
Configuration overview: VPS wireguard server set to forward all traffic from peers (it’s operating as a self-hosted VPN). I have a port on my router we’ll call OPT1 that I want to traffic all connections through wireguard to the VPN.
So far I have the VPS and pfsense connected successful through wireguard. They are making active handshakes and I can ping between them perfectly fine.
I followed the documentation, but my windows PC connected directly to OPT1 can’t access the internet. From the PC I can ping the DHCP server of OPT1 as well as the wireguard tunnel, but I can’t ping anything outside of that. I’m passing all traffic from OPT1 subnet to the wireguard interface in both OPT1 firewall rules and the wireguard interface rules.
I’m sure many of you have dealt with this configuration before. Does this issue sound familiar?
Problem solved. The firewall was attempting to pass traffic through the default gateway. You have to create a firewall rule to allow whatever traffic you want but in the advanced settings you need to select the wireguard gateway instead.
On the “server” side, you need to allow packets to get forwarded from the wg interface to the “lab” side. Positive there are guides on this. If you enable firewall logs, you’ll see that packets are being discarded until you allow them to be forwarded between interfaces/networks.
Maybe search for a “hub and spoke” guide, which essentially what you are doing.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Problem solved. The firewall was attempting to pass traffic through the default gateway. You have to create a firewall rule to allow whatever traffic you want but in the advanced settings you need to select the wireguard gateway instead.
On the “server” side, you need to allow packets to get forwarded from the wg interface to the “lab” side. Positive there are guides on this. If you enable firewall logs, you’ll see that packets are being discarded until you allow them to be forwarded between interfaces/networks.
Maybe search for a “hub and spoke” guide, which essentially what you are doing.