Selfhosted

41623 readers

444 users here now

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
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

Opnsense Tailscale Plugin - Firewall (lemmy.dbzer0.com)

submitted 4 days ago by [email protected] to c/selfhosted

2 comments fedilink hide all child comments

I feel like this might be a long shot but wanted to see if anyone else was running the tailscale plugin for Opnsense. I have everything set up when my opnsense acts as an exit node. The clients connect up to the exit node just fine but I wanted to redirect traffic to a different gateway instead of my ISP gateway. I tried setting up tailscale net as the source on the tailscale interface to route traffic to a specific gateway but it doesn't seem to work. It seems like tailscale ignores all of opnsense firewall rules which is a lot different than what I am use to working with the wireguard interface on opnsense.

you are viewing a single comment's thread
view the rest of the comments

[–] BobsAccountant 1 points 4 days ago

You said you added the Tailscale network, but how wide did you go? By default when you load the plugin and activate the interface, it just gives its own IP as the network (/32). If you added that, then only traffic with that specific origin will hit your route. It's crazy, but for my firewall rules (not routing) to work, I had to define the network as a 100.0.0.0/8, which is gigantic. You may have to do that with the route as you can't otherwise set the gateway on the interface as it's not hosting the DHCP server.