

Good point about network availability and endpoints.
Good point about network availability and endpoints.
Since I have no patience, I’ll lay out some items for consideration.
1st, I wouldn’t rely on an ISP router to serve as my end point for a VPN. They likely have access to manage that device and it likely isn’t getting any updates. You are better off implementing it with your own equipment that you keep updated.
If you have a capable security device serving as your router to the external internet and you want full access to your internal network, then you might consider using a VPN that terminates at your router.
I myself am a fan of setting up a jump host and initiating a VPN connection directly to that host when using an agent based solution. Then you can monitor the host for activities, more easily keep your edge device patched, and then use the capabilities of your jump host to interact with the rest of your network. This would require either an agent to periodically poll a platform for connection requests or another form of ingress into your network.
Expand on your use case. Why/what do want to access on your local network when you are not there?
Omg, I agree. I hate seeing the same article posted to 10 different instances all lined up in a row.
More than 5 posts would raise the likelihood of people blocking that instance because of spam. Less is more.
It sounds like you are looking for a server that is ripe for bot abuse. What time frame did the admin say not more than 5 posts. I would tend to think they mean 5 posts a day which sounds completely reasonable to be for an upper limit on posts per day into a single sub.
But it is only 6. Crunchy vs smooth doesn’t taste any different.
The feelings stage can be simplified into two scenarios.
When I’m unsure I ask my partner if they need to vent, feel supported, and/or solve the problem.
I don’t think that is a fair argument in this day and age of software development, especially for an operating system. With that level of complexity, I would contend that it is next to impossible to identify potential failure scenarios. I also think this suffers from a rose colored glasses view on history. Perhaps software in the past was as vulnerable, it just never got patched because there wasn’t an easy method to apply updates. Now that there is, it is much better to have a responsive development team to react and fix obscure problems that are difficult or impossible to predict.
This article has no useful information.
Why not link directly to the article then instead of a Reddit post that links to an article?
A Reddit post is not an article.
I said modern programming languages. I do not consider C a modern language. The point still stands about abstraction in modern languages. You don’t need to understand memory allocation to code in modern languages, but the understanding will greatly benefit you.
I still contend that knowledge of the cpu pipeline is important or else your code will wind up with a bunch of code that is constantly resulting in CPU interrupts. I guess you could say you can code in assembly without knowledge of the cpu architecture, but you won’t be making any code that runs better the output code from other languages.
Assembly requires a knowledge of the cpu architecture pipeline and memory storage addressing. Those concepts are generally abstracted away in modern languages
I’m guessing CF stands for cluster fuck.
What happens when the only way to seat a family together is to break up another family. What if you need to separate a couple who is engaged and traveling together?
I would prefer it to be opt in, instead of opt out. Maybe the centralized opt out won’t be as toothless as the do not call list.
A jump host is just a system that serves as an exit point into the restricted network. You can do this with Ubuntu desktop but you need to figure out how you are going to jump into your host. Others have mentioned tail scale and head scale as options for doing this. Tailscale would be an example of an agent based adhoc vpn solution; this would place a dependency on an external provider to host a connection broker service and use an agent that periodically checks into the broker service for connection requests. Headscale would be the self hosted option and you would need to forward a port into your network and you should guard it with a reverse proxy.