Originally posted by starshipeleven
View Post
Is "Address" the IP address you want the service to listen or or the address of the tunnel, or is it the virtual adapter?
What "Endpoint" are you talking about, the network you are connecting to or the server or the tunnel? What perspective are you coming from here? Is endpoint the network your bridging to?
"AllowedIP's" is confusing too is that an allow list for the clients that connect to it? Address in the tunnel? What?
This could be cleaned up with clearer names such as "ListenAddress" (like every other piece of software.)
if I'm asking these questions as a ~30 year experienced sysadmin.. regular users are going to be totally lost. Even the Webpage is screwed up "Interworkings" What in the crap? -- how about DOCS? Is that too hard? No.. it is because they don't have real docs. (Interworkings.. jesus.. christ.. this is what happens when you let programmers run the show. They think their software is so cool and creative.. well maybe it is but nobody else cares, they just care if it solves their problem.)
Originally posted by starshipeleven
View Post
And no, In fact I did read the scrawl they wrote. Proper IT documentation stats with an introduction and has information on each and every fiction and option in the configuration and then contains working tutorials and examples. They don't need 50 pages, but 10 would be nice. If they ever want to be taken serious they need this. OpenVPN has good documentation, where is Wireguards?
I literally laughed reading it when they were talking about "So say you are in a coffee shop on their wifi - If you just run this script" ... give me a break.. what a joke. This is NOT enterprise software. At all. it's about at the same level stunnel is.. and there is nothing wrong with that.. but if you are going to make claims like, improving VPN's and making them simple and high performant and replacing all VPN software.. Wireguard team has decades in front of them before they will meet those goals.
Leave a comment: