glizzyguzzler

joined 2 years ago

I urge you to get crunked, get a pack of pizza rolls, make them all, and go to town at 3 AM.

You will not regret it in the moment, but you will regret it later

It’s even better with friends, hence this me-me:

I cannot express how perfect this is

I will investigate, for science

[–] glizzyguzzler@lemmy.blahaj.zone 4 points 1 year ago (2 children)

Would you tell me what you’re using to view Lemmy? It works on web browsers for me but it would be good to know how to make gifs that are viewable by everyone 100%

[–] glizzyguzzler@lemmy.blahaj.zone 1 points 2 years ago* (last edited 2 years 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 https://serverfault.com/questions/586486/how-to-do-the-port-forwarding-from-one-ip-to-another-ip-in-same-network).

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

Setting the WG [Interface] range to 10.0.66.0/16, along with the [Peer] to 10.0.66.10/16, and the Opnsense DHCP range in Interfaces->LAN to /16 made no connection to the internet or local occur.

This feels like banging rocks together hoping for fire - not for me (but maybe reading stuff for a bit will help, maybe)

[–] glizzyguzzler@lemmy.blahaj.zone 1 points 2 years ago* (last edited 2 years ago) (2 children)

Who knows indeed, I'm beginning to suspect that it was able to connect via the internet (and that stopped working) and I just never noticed so the VPN was a superfluous extra step.

But I did try in the [Peer] definition setting the allowed IPs to: 10.0.66.10/16 instead of 10.0.66.10/32, which should expand the allowed range to 10.0.69.XXX. Alas, that did not work.

Edit: Also tried assigning the [Peer] to an unused IP in the 10.0.69.XXX range directly, but that made nothing work so not the way either.

[–] glizzyguzzler@lemmy.blahaj.zone 1 points 2 years ago (4 children)

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.

view more: ‹ prev next ›