In my previous update, I used a symbolic link to set up the name for new namespace, like so:

My previous post originally used bind mounts (mount --bind /proc/self/ns/net /var/run/netns/vpn) instead of symbolic links (ln -sf /proc/self/ns/net /var/run/netns/vpn) to name the private namespace. The mount method created two complications:

A few weeks ago, I had occasion to find out how Docker overlay networks could be created manually, which led me to learn more about network namespaces in Linux. I already knew the concepts behind various namespaces (user, PID, mount, etc.), but this was the first time in a long time that I had occasion to set one up myself. In the process, I came up on one solution to a problem that I’d been having recently: applying a VPN only to some applications.

Over a year ago, I got a Raspberry Pi 3B. Yahoo! JAPAN has this nice system called TechUP for buying stuff (gadgets, books, subscriptions, etc.) to improve your technical skills. A Pi is perfect — it’s well within the budget, and you have lots of people using it for various projects, so there’s a lot of material online that you can learn from. And the models are always increasing in power — just look at the recently released Pi 4: a max of 4 GB of RAM (potentially more), USB 3, and Gigabit Ethernet that doesn’t share buses with the USB ports. Today, though, I’ll be talking about the Pi 3B and my experiments with it.

So, it’s been half a year since I got the Alienware Aurora R7, and I have had my fair share of bugs and annoyances. Today, I’ll talk about a few of those.