this post was submitted on 02 Nov 2023
9 points (73.7% liked)

Selfhosted

40113 readers
1490 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I have an #OpenWRT router. Let’s say I install Tailscale on it and want to create an interface that specifically routes to one of my exit nodes. Can I do that?

Everything I’ve seen about Tailscale on OpenWRT just provides direct router access to the tailnet (100.x.x.x), but I specifically want to route certain traffic to an exit node.

Can I do this? Do me proud, Fediverse! Hoping I can get good answers here without resorting to Reddit.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago

I’ve done something similar, though not with openwrt. There may be a decent way to do this on the firewall, but I ended up using the ACLs available from the Tailscale console.

I removed the default allow all rule. I made a group called admins that can access everything and then added a set of routes that everyone on the tail net could access.

I’ve only recently set this up, but initial testing seems to have this working as hoped.