VPN to home network to access PS4 doesn't work via PS Remote Play app

Submitted ⁨⁨1⁩ ⁨year⁩ ago⁩ by ⁨glizzyguzzler@lemmy.blahaj.zone⁩ to ⁨selfhosted@lemmy.world⁩

I have my home network behind a wireguard VPN connection. The wireguard “server” is run on a debian computer and the home network is handled by an opnsense computer.

My home network is on the subnet 10.0.69.XXX, while the VPN connection gets the subnet 10.0.66.XXX.

Weirdly, this setup worked fine until yesterday for the PS Remote Play app (hard requirement, iOS device). Nothing changed as far as I can tell - but yesterday the PS4 stopped being found by the PS Remote Play app (when I’m home on the 10.0.69.XXX subnet, the PS Remote Play app works fine).

I suspect from what I can google ( snbforums.com/…/ps4-remote-play-over-vpn.60629/ , github.com/williampiat3/ImprovingPSRemotePlay#lon… ) that to make it seem to the PS Remote Play app that all is well abs. 100% I need to get my device on 10.0.66.10 to do a broadcast search on the 10.0.69.XXX subnet (or have a 10.0.69.XXX address).

I feel (hope) there is a way to do this, but I am no iptables wizard. Does anyone know how to accomplish this? The solutions linked don’t make sense to me in a practical way to apply them.

source

Comments

Sort:hotnew top

Cooljimy84@lemmy.world ⁨1⁩ ⁨year⁩ ago
My friendly 2 pence, my mobile provider me a 10.x.x.x IP with CNAT (carrier grade NAT) when I’m on mobile data.

Could you not set your subnet mask on the wireguard and home to 255.255.0.0 then you can see the whole 10.0.x.x block in a broadcast?

source
- glizzyguzzler@lemmy.blahaj.zone ⁨1⁩ ⁨year⁩ ago
  Where would I set the subnet mask?
  
  I do not understand how to apply most networking concepts effectively - I only run Opnsense to get a router that has actual software updates, not because I now how to use it (no experience with networking otherwise).
  
  In WireGuard I specify the 10.0.66.XX subnet directly without DHCP. In Opnsense, I’m not sure where to look and searching for it didn’t help illuminate anything obvious.
  
  source
  - nrezcm@lemmy.world ⁨1⁩ ⁨year⁩ ago
    Check your firewall logs (Status -> System Logs -> Firewall for pfSense, can’t remember for opnsense). I’d suspect you might see blocks from 10.0.66.x to your Playstation.
    
    source
    -> View More Comments
  - Cooljimy84@lemmy.world ⁨1⁩ ⁨year⁩ ago
    So the subnet mask is got from the device handing out dhcp. Not 100% sure but on my android the subnet mash for wireguard is as /24 set on the device and also matching in the wireguard settings in opnsense. Opnsense is very very powerful, I would watch a few videos on YouTube about subneting, wireguard routing & dhcp. Its gonna be quite the learning curve (or could be)
    
    source
    -> View More Comments
Decronym@lemmy.decronym.xyz ⁨1⁩ ⁨year⁩ ago
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

Fewer Letters More Letters

IP Internet Protocol

NAT Network Address Translation

VPN Virtual Private Network

[Thread #159 for this sub, first seen 23rd Sep 2023, 19:25] [FAQ] [Full list] [Contact] [Source code]

source
glizzyguzzler@lemmy.blahaj.zone ⁨1⁩ ⁨year⁩ ago
I did a wireshark packet capture and found the wake-up packet is on UDP 987. I can only capture broadcasts, not specific stuff it looks like. Source: 10.0.69.69(iOS device IP) Destination: 10.0.69.255 Protocol: UDP Length: 105 Info 57477(or 62764, 62335, 60311 as source ports) -> 987 Len=63 Note the IP of the PS4 is 10.0.69.150

I’m not sure what to do with this, though. Nothing I tried worked (e.g., jamming 987 into the IP tables iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A PREROUTING -p udp --dport 987 -j DNAT --to-destination 10.0.69.150:987; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE; iptables -t nat -A POSTROUTING -p udp -d 10.0.69.150 --dport 987 -j SNAT --to-source 10.0.66.10:987 based on serverfault.com/…/how-to-do-the-port-forwarding-f…).

Additionally setting the Wireguard mask to 10.0.66.1/16 makes the WG connection not route successfully, and setting the mask in OpnsenseRouter->Interfaces->[LAN]->(under Static IPv4 configuration section) to 16 did nothing. Oh well, this seems beyond me

source

Fewer Letters	More Letters
IP	Internet Protocol
NAT	Network Address Translation
VPN	Virtual Private Network