With arr services try to limit network throughput and disk throughput on them, as if either are maxed out for too long (like moving big linux iso files) it can cause weird timeouts and failures
With arr services try to limit network throughput and disk throughput on them, as if either are maxed out for too long (like moving big linux iso files) it can cause weird timeouts and failures
Another one to have a search for is IPFS.
It always throws me when I see at 1080 movie less than 5gb, then I scroll across and see it’s x265…
Both devices need the same subnet mask, otherwise only one can see the “extra addresses” but in my opnsense I think I and to add some firewall router between LAN & WG0
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)
As to why everything has stopped working who knows…
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?
Very strange, but looks prebent
Nuke’em from orbit, its the only way to make sure.
deleted by creator
Good point, what happens if you run that command ? It might also just left over from when they made the custom image and forgot to clean it all up ?
From the location of that script usr lib virt-sysprep looks to be a script put in the image by the provided to do a few things on first boot. Would have thought it was normal, but you can always ask them to double check
Should be fine, I’m writing to spinning rust, so if I was playing back a movie it could cause a few “dad the tv is buffering again” problems