Explore >> Select a destination
|
You are here 
|
karla.io | ||
| | | | |
williamdurand.fr
|
|
| | | | | I am writing a minimum viable network stack from scratch for ArvernOS (a UNIX-like toy kernel). This two-part story describes some protocols of the TCP/IP stack as well as some implementation details in the context of ArvernOS. | |
| | | | |
iosoft.blog
|
|
| | | | | So far I have used a large number of custom functions to configure and control the WiFi networking, but before adding yet more functionality, I need to offer a simpler (and more standard) way of doing all this programming. When it comes to network programming on Linux or Windows systems, there is only one widely-used... | |
| | | | |
blog.oddbit.com
|
|
| | | | | Last week, Oskar Stenberg asked on Unix & Linux if it were possible to configure connectivity between two networks, both using the same address range, without involving network namespaces. That is, given this high level view of the network... ...can we set things up so that hosts on the "inner" network can communicate with hosts on the "outer" network using the range 192.168.3.0/24, and similarly for communication in the other direction? | |
| | | | |
willhaley.com
|
|
| | | After following DigitalOcean's guide for upgrading to Ubuntu Xenial I hit a snag. DNS was broken. I do not see this as a fault of DigitalOcean, but more likely an issue with Ubuntu. Update: 2017-06-27 As U?ur Çetin mentions in the comments below, there is a simpler fix for this. Find the IP address of your mirror and create an /etc/hosts entry for it. Then simply run apt upgrade. Done! Once resolvconf is working properly again, you should be able to comment out or remove the /etc/hosts entry you created for the mirror. | ||
