Hey Zach
It's actually "Zack".
I thought I would try to use the pf routing option `route-to` to accomplish this as it seemed like it might be a simple solution.
You might be able to, but I prefer using pf to only filter traffic when I can get away with it-obviously for things like NAT I use pf.
If I was to use a new rdomain/rtable, how would I go about routing a single IP from a /24 prefix across the wg(4) tunnel and let all the other IPs in that prefix use the default route (in the default rdomain/rtable)?
I segregate my traffic with vlan(4)s and route traffic in the VLANs the same, so I have never needed to route a specific IP differently. Is there a reason the device (e.g., Apple TV) cannot belong to a different network? If not, then it's very simple to set up. There are many sources online as well as the man pages that can be useful. If you need traffic to be routed across rdomains, then pf can be used. For example the rule: pass in quick on rdomain 0 inet6 proto icmp6 to $servers rtable 1 will route ICMPv6 traffic from rdomain 0 entering the router destined to the IPs belonging to $servers by using rtable 1. Possibly useful external links: https://philomathiclife.com/self-hosting/acquiring-multiple-non- residential-ips/ https://dataswamp.org/~solene/2021-10-09-openbsd-wireguard-exit.html
