this post was submitted on 28 Jan 2025
13 points (84.2% liked)

Selfhosted

60543 readers
338 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the link in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post. )

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

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

You need routing rules for this on the exit node. You can't use the default routes for the machine and expect a virtual device that is already being routed to know where to go.