Running pfsense, I was able to route my entire LAN subnet through a VPN. I have firewall and NAT rules that use an alias to filter outgoing connections to specific domains outside of the VPN gateway.
This works great. But here’s the problem. Wildcards are not supported within pfsense aliases, and therefore unless you know the specific subdomain for a service, there’s no way to reroute services that use rotating or load balancing subdomains.
Surely this is a big problem in large companies. I’m sure they utilize a paid solution to solve this problem.
Are there any solutions for self hosting that are FOSS or within pfsense?
What exactly are you trying to split out? Generally, routing is done at the IP level, not by name.
There’s a few apps I need to split out. Top priority is the signiant app which according to their documentation requires various AWS subdomains as well as their own. Specific subdomains are not specified and are implied to change regularly/on demand.
In an ideal world I would do my split tunneling on the device itself, but I don’t trust Windows and thus I run my VPN at the router level.
This isn’t a problem for most things, but I need to utilize my full bandwidth to transfer large files to clients in a timely manner, and a VPN becomes a massive bottleneck.
Pfsense lets you alias by domain name (I believe it regularly resolves down to an IP and uses that for filtering), but again, you need to supply the exact subdomain.
Just wondering if there’s an alternative solution to this issue. If it’s external to pfsense that’s not the end of the world.
Worst case scenario, I would set up a dedicated Linux box or maybe even a VM which could share access to the file transfer NAS and split tunnel the entire box around the VPN. Definitely less convenient.
Can you configure those apps to use a proxy? You could set up a tiny little VM or container that has direct access, and upload through there.