Tcp is traditionally less than ideal for larger packets. So is this a novel development? There are at least two projects that explore tcp tunneling in Wireguard.
This makes no sense to me since Wireguard's code relies upon udp (user datagram protocol), not tcp. Note:(04-29-23) Nordlynx "functional" now after update protocol tcp(?) only. Any assistance or criticisms would be appreciated. Nord has referred us to the AUR community. This problem is not ISP related or related to a specific or idiosyncratic arch installation. I re-duplicated these errors on a newly configured archlinux box home video server today,and have two different ISPs. These issues are specifically with NordLynx openvpn technology has not been problematic (although now - it is also now rejecting a udp protocol). $ sudo journalctl -u nordvpnd > /home/"user"/Desktop/daemonlog.txt Mysteriously, "libtelio" errors in daemonlog.txt have disappeared, and today interface errors. Either 'libtelio' errors or issues with nordlynx technology not detecting a network interface are being experienced despite the presence of functional interfaces.
0 kommentar(er)
