Marek Küthe
Marek Küthe
Tailscale is slow: `wg: Failed to write packets to TUN device: write /dev/net/tun: invalid argument`
> I also experienced this problem on Arch Linux with `linux 6.10.3.arch1-1` and Tailscale version 1.70.0. Downgrading the kernel to `6.10.2-arch1-2` resolved the issue. Downgrading the kernel to `6.6.35-2-lts` also...
Tailscale is slow: `wg: Failed to write packets to TUN device: write /dev/net/tun: invalid argument`
> * Observed in dmesg: `[ 96.578967] ens18: bad gso: type: 4, size: 1348` Mhh, I haven't seen anything like that in dmesg. > If you are able to do...
Tailscale is slow: `wg: Failed to write packets to TUN device: write /dev/net/tun: invalid argument`
``` $ go version -m ~/go/bin/tailscaled | grep wireguard-go dep github.com/tailscale/wireguard-go v0.0.0-20240806212730-80ee55ffe40c h1:pH75gpj1SYEQdGK1gZ4VHwyZY/KOpG4btbol4jxTsoE= ```
Tailscale is slow: `wg: Failed to write packets to TUN device: write /dev/net/tun: invalid argument`
> Also if you want to test the kernel side of things here are the `linux` and the `linux-lts` packages with [gregkh/linux@89add40](https://github.com/gregkh/linux/commit/89add40066f9ed9abe5f7f886fe5789ff7e0c50e) applied (which fixes the problem according to [#13041...
Tailscale is slow: `wg: Failed to write packets to TUN device: write /dev/net/tun: invalid argument`
``` $ uname -a Linux ciel 6.6.44-3.1-lts #1 SMP PREEMPT_DYNAMIC Tue, 06 Aug 2024 23:09:53 +0000 x86_64 GNU/Linux $ sudo ping -f -c1000 vpn-lu.uaru-vimba.ts.net PING vpn-lu.uaru-vimba.ts.net (100.110.144.38) 56(84) bytes of...
``` root@homeguard:~# logread | grep collectd Sun Aug 11 07:26:31 2024 daemon.err collectd[7971]: rrdtool plugin: rrd_update_r failed: /tmp/rrd/homeguard/chrony/time_offset-194.94.95.123.rrd: opening '/tmp/rrd/homeguard/chrony/time_offset-194.94.95.123.rrd': No such file or directory Sun Aug 11 07:27:01 2024...
Two other things: 1) After I set `option backup '0'`, it works again. 2) In the meantime there was another problem with collectd. I had a configuration for `collectd-mod-tcpconns` in...
The whole thing seems to work without the chrony plugin. Then there are still two errors: 1) The chrony plugin does not work completely. 2) LuCi should not log me...
The following are my chrony settings: ``` root@homeguard:~# cat /etc/config/chrony config makestep 'makestep' option threshold '1' option limit '3' config pool option hostname 'ptbtime1.ptb.de' option iburst 'yes' option nts 'yes'...
No, I didn't. I am extremely inexperienced when it comes to such bugs in the bug report. I have therefore posted it here at the URL given in the bug.