3 ms·
This basically means they are using userspace Wireguard, such as the go implementation. That is as opposed to the in-kernel wireguard. The reason to mention co
by freedomben 3y ago
This basically means they are using userspace Wireguard, such as the go implementation. That is as opposed to the in-kernel wireguard.
The reason to mention conjuring a TCP IP stack out of thin air, is that most of the time the operating system is providing the tcpip stack as part of the kernel. With wireguard go, the tcpip stack is running in user space, meaning it can be created in a normal user space process such as the flyctl command line interface. This is indeed quite magical for people who have been around for many years as a usable in-process userspace tcpip stack is a relatively new and a novel thing.
- cchance 3y agoI always felt weird about this, i still cant really wrap my head around userspace tcpip stacks, it just feels... weird
- _JamesA_ 3y agoThere was a time that's all we had when using Windows [1]. It was weird. [1]: https://retrocomputing.stackexchange.com/questions/5891/how-did-microsoft-take-over-winsocks-windows-sockets https://retrocomputing.stackexchange.com/questions/5891/how-...