

At my remote site it has little value. At my home I have IPv6 setup on Starlink as my secondary backup internet. I use Fiber as the primary that has a public IPv4 and IPv6.
Could just use a VPS though I guess if you want.


At my remote site it has little value. At my home I have IPv6 setup on Starlink as my secondary backup internet. I use Fiber as the primary that has a public IPv4 and IPv6.
Could just use a VPS though I guess if you want.


These are going to be the people who think it’s smart to just open up RDP and SSH to the wide web though…they shouldn’t be forwarding ports…they should use a VPN.


I’d much rather deal with setting up a few VPN gateways which is trivial at most…than securing a public web service. I deal with that crap enough at work.
There are a lot less variables to contend with with a single VPN endpoint which undergoes considerably more security auditing than N public web services. Many of which I don’t have the time to review myself and mitigate if they decide to suck at coding.
Edit: I share my services with less than 5 households though.
Edit2: I’m not sure what public ipv4 or ipv6 has to do with this. My remote sites use starlink ipv4. I haven’t setup ipv6 on those internally at all. They all tunnel via wireguard to my homesite.


Setup a VPN gateway at Grandma’s house. Works fine for me.


For the vast majority of users? Yes. They shouldn’t forward ports.
Setup a VPN gateway at Grandma’s house.
We use lots of natural borders as the delimiters of given states. The Mississippi River is a big one. You see it more out east than west IMHO.


Not a great feature when you have multiple people in the same house with different users and watch histories.


Easier to handle and dump would be my guess.


In my state you can shoot, butcher, and then dispose of all of the waste (bones, skin, etc) from a deer directly into the trash. My first thought would have been, assuming you feel bones inside, that it’s from hunting.


It’s the default in the new PiOS


Because I love my dog.
Exactly that. Run a docker container (probably privileged) that has your local volume mounted. Inside that docker container install cifs-utils and then connect to the SMB server from there via CLI.
Maybe use a docker container?
Are you using Linux at work without systemd? Seems unlikely. All our 400+ nodes run RHEL and consequently systemd. This doesn’t seem to impact our researchers’ use of CUDA in the slightest when executing code on the nodes or in any kind of container.
Yeah. This is why you don’t encourage normies to port forward…they make everyone a domain admin and open up RDP…