Adam Trickett 
Spent most of the day writing #bash scripts to automate #Wireguard and #NetworkNamespaces. I don't do #bash all that often so have had books open to make sure it's robust code. Some of the books are over 25 years old - their authors must have retired by now!
My use of #Wireguard and #Linyx #NetworkNamespaces has worked better than Wireguard alone. Feeling very pleased. the next step is to make it work on a more complicated set-up.
Been playing with #Wireguard and #NetworkNamespaces. Interesting stuff...
MarekSystemd and Linux Network Namespaces together are terrible, although each is very nice individually. I have seperated clearnet access and dn42 access via netns in a lab setup. For each program I wanted to use in both namespaces, I had to copy-paste and customize the Systemd unit. This is terrible. Too bad Systemd doesn't support this natively, but only with tricks.
What kind of reason is "I don't like the concept"?
https://github.com/systemd/systemd/issues/2741
Personally, I find netns very handy because you can easily isolate networks (for example, dn42 and the Clearnet). This is also what Kioubit does in dn42, for example. To reject a proposal with this reasoning I think is wrong.
