I’m on trip and don’t have access to my pi, wondering if this is still an issue
opened 10:49PM - 20 Aug 18 UTC
closed 10:26PM - 21 Aug 18 UTC
Solution available
ROCK64
Kernel related
External bug
RK3399
After a lot (I mean, a lot) of investigation on TCP resets, Ack errors and Dups,… I found the problem that I describe while pushing a Docker image to DockerHub here: https://github.com/moby/moby/issues/37642
The boards like RK3399 need TCP/UDP offloading disabled to avoid the retransmissions and reset errors. This was already implemented by Ayufan on Rock64 and RockPro64 Rootfs and DietPi needs this too.
The configuration file below should go to `/etc/network/if-up.d` to disable offloading on this boards.
```
#!/bin/sh
ETHTOOL=/sbin/ethtool
test -x $ETHTOOL || exit 0
[ -d "/sys/devices/platform/ff540000.eth/net/$IFACE" ] || [ -d "/sys/devices/platform/ff540000.ethernet/net/$IFACE" ] || exit 0
$ETHTOOL -K "$IFACE" rx off tx off
```
This file above I got from [Ayufan's repo](https://github.com/ayufan-rock64/linux-package/blob/master/root/etc/network/if-up.d/rock64-offload) but the device "ff540000" is for Rock64 SBC. For RK3399 boards (I checked Firefly NanoPC-T4 and FriendlyArm RK3399) the identifier is: `/sys/devices/platform/fe300000.ethernet/net/$IFACE`. I believe both should be there.
I will check if RockPro64 ID also changed later.
1 Like
jack
May 21, 2019, 4:19am
2
I am afraid it might be the issue. We don’t have ipv6 testing environment, could you test it?
I am pretty sure it is affecting rockpi4b-ubuntu-bionic-minimal-20190104_2101-gpt.img.gzethtool -K eth0 rx off tx off seems to help alot, now starting a fresh image an see how this goes, old image is totally messed up due apt errors
1 Like