Plex through surfshark wireguard pfsense vpn
-
@stephenw10 IMO?, what if my machines are connected to lan pfsense is that command u put still valid for that ?
-
I didn't put a command. I would add it in the gui so you don't end up removing any other subnets you are routing.
-
@stephenw10 said in Plex through surfshark wireguard pfsense vpn:
I didn't put a command. I would add it in the gui so you don't end up removing any other subnets you are routing.
Yes you are right of course. I happen to run them on various Linux machines and execute the command sudo tailscale up with any additional settings.
In my case it's the --advertise-routes=xxx.xxx.xx.x/24,nnn.nnn.nn.n/24 which defines the subnets that I am allowing my clients to access.
If you deploy it in pfsense it's different. Simply click add and enter your ISP routers LAN IP or entire subnet after the existing subnets.
Then the subnets will be visible in the admin gui when you log into the tailscale admin console at https://login.tailscale.com
For your respective subnet router, on the right you can access and control which subnets will actually be allowed to be used.
-
@Gblenn but does a pc have to have Tailscale on the isp router/modem side for me to access it in my pfsense lan
-
No, pfSense is the client here. As long as it's WAN side subnet is routed by tailscale a remote client will be able to access it.
-
@stephenw10 how do I add the wan side in pfsense then?
-
As @Gblenn showed above. You need it to advertise that subnet to other tailscale clients that same as it's doing for the LAN.
But unless you really need this I would wait until you're on-site to revert any changes you might make accidentally.
-
@stephenw10 ok will have a go
-
@stephenw10 I have indirect connections on plex I don't know whether it's pfsense is causing it or not my setup is same as above
-
@jhmc93 What do you mean with "indirect connections"?
I tried reading through the thread to get back into the thinking here... Are you still running two separate networks with your wifi on the WAN side of pfsense?? Or have you cleaned it up so that you have everything on the correct side of pfsense?? -
@jhmc93 said in Plex through surfshark wireguard pfsense vpn:
my ISP router is also my modem, so it’s gotta be running to provide my internet. Also my pfsense only has LAN ports but no WiFi access, so I use my WiFi devices on my ISP/ Modem router and my pfsense for my proxmox clusters that run my media servers.
You are making your life hard imo.
Your system would be more maintainable if you-
Put your ISP Modem/Router in bridge mode, so it functions purely as a Modem
-
Use pfsense as your router / firewall for all your LAN
-
Use a dedicated device / Access point for your wifi
-
-
@Patch pfsense doesn’t have a WiFi device to broadcast WiFi. Pfsense is a side step as it also ran off a power line network plug for just my media servers, so I narrowed it down so when I connect to my isp WiFi my Plex shows indirect connections but if I join my VPN program through my laptop it goes back a normal connection.
-
That seems expected if the Plex server is behind pfSense and the clients are in front of it.
-
@jhmc93 said in Plex through surfshark wireguard pfsense vpn:
@Patch pfsense doesn’t have a WiFi device to broadcast WiFi.
My recommendation is you use a dedicated WiFi access point.
Doing so will give you a more capable and maintainable systemI use UniFi access points with the controller running as a VM on Proxmox but there’s several good options
-
@jhmc93 said in Plex through surfshark wireguard pfsense vpn:
@Patch pfsense doesn’t have a WiFi device to broadcast WiFi. Pfsense is a side step as it also ran off a power line network plug for just my media servers, so I narrowed it down so when I connect to my isp WiFi my Plex shows indirect connections but if I join my VPN program through my laptop it goes back a normal connection.
Yes, that ^ otherwise what is the point of having pfsense at all?
If you are looking to improve network safety/security and perhaps add more functionality, you really need to move everything over to be on the LAN side of pfsense.
Right now you are just making life difficult for yourself.The best, and also cheapest solution would be if you can connect pfsense directly to the incoming cable (ISP WAN cable in pfsense instead of ISP router). Then turn off DHCP in the ISP modem, and connect one of it's LAN ports to pfsense LAN. This turns it into an AP and you are good to go...
Otherwise check if the ISP router has bridge/passthrough mode. If not you need to place pfsense in a DMZ, which the router probably has.
