#veth — Public Fediverse posts

Ok, some more info. Decided to do some basic #benchmark. Run #iperf3 on it. I was able to get gigabit against my desktop. No routing, I have just one network card. But I tried #veth interfaces and benchmarked throughput between two namespaces and got to 7 gigabits. #cryptsetup benchmarks just #aes-cbc and claims 40MiB/s for 128b and 30MiB/s for 256b which sounds like no accelerator is used and support for other ciphers might be missing from the kernel. Still using official firmware - no time to reinstall yet.

Ok, some more info. Decided to do some basic #benchmark. Run #iperf3 on it. I was able to get gigabit against my desktop. No routing, I have just one network card. But I tried #veth interfaces and benchmarked throughput between two namespaces and got to 7 gigabits. #cryptsetup benchmarks just #aes-cbc and claims 40MiB/s for 128b and 30MiB/s for 256b which sounds like no accelerator is used and support for other ciphers might be missing from the kernel. Still using official firmware - no time to reinstall yet.

At the moment it clearly boots the #nspawn container and moves the two Ethernet interfaces into the container. It also sets up an extra #veth pair, but for some reason I can't raise the veth pair, "ip link dev lan set up" from the host OS leaves the veth "lan" in the DOWN state... Wth? I think if I could get that veth up id be able to remote log in through #yggdrasil connection.

At the moment it clearly boots the #nspawn container and moves the two Ethernet interfaces into the container. It also sets up an extra #veth pair, but for some reason I can't raise the veth pair, "ip link dev lan set up" from the host OS leaves the veth "lan" in the DOWN state... Wth? I think if I could get that veth up id be able to remote log in through #yggdrasil connection.

At the moment it clearly boots the #nspawn container and moves the two Ethernet interfaces into the container. It also sets up an extra #veth pair, but for some reason I can't raise the veth pair, "ip link dev lan set up" from the host OS leaves the veth "lan" in the DOWN state... Wth? I think if I could get that veth up id be able to remote log in through #yggdrasil connection.

At the moment it clearly boots the #nspawn container and moves the two Ethernet interfaces into the container. It also sets up an extra #veth pair, but for some reason I can't raise the veth pair, "ip link dev lan set up" from the host OS leaves the veth "lan" in the DOWN state... Wth? I think if I could get that veth up id be able to remote log in through #yggdrasil connection.

At the moment it clearly boots the #nspawn container and moves the two Ethernet interfaces into the container. It also sets up an extra #veth pair, but for some reason I can't raise the veth pair, "ip link dev lan set up" from the host OS leaves the veth "lan" in the DOWN state... Wth? I think if I could get that veth up id be able to remote log in through #yggdrasil connection.