KaraRyougi

Same issue here. Environment is Kubuntu 18.04 and qtShadowsocks. The error log goes like this: ``` AEAD data chunk is incomplete (too small for payload) AEAD data chunk is incomplete...

@bringtree I switched to shadowsocks-libev...

I also got a similar panic error for the conntrack plugin: ``` panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x38 pc=0x137d4d3] goroutine...

It seems `addr, err := nfutil.GetOrigDst(tc, ipv6)` doesn't work.

So basically it's about ``nfutil/socketcall_linux_other.go``... I checked ``https://golang.org/src/syscall/syscall_linux_mips64x.go``. Is it unfinished?

I have a similar issue with qat1.7.l.4.7.0-00006.tar.gz when I tried to enable SR-IOV by enable-icp-sriov=host. I have the following errors: ``` Building for linux_2.6 MODPOST 1 modules ERROR: "osalCryptoInterfaceInit" [/QAT/quickassist/lookaside/access_layer/src/qat_api.ko]...

Actually, I found that the build will fail without any configure flags. @jdschuet ``` ... ERROR: "osalCryptoInterfaceInit" [/root/QAT/quickassist/lookaside/access_layer/src/qat_api.ko] undefined! ERROR: "osalCryptoInterfaceExit" [/root/QAT/quickassist/lookaside/access_layer/src/qat_api.ko] undefined! ERROR: "adf_module_unload" [/root/QAT/quickassist/lookaside/access_layer/src/qat_api.ko] undefined! ERROR: "icpSetProcessName" [/root/QAT/quickassist/lookaside/access_layer/src/qat_api.ko]...

I had the same issue. I followed AI's suggestion to add ``` [patch.crates-io] smoltcp = { git = "https://github.com/smoltcp-rs/smoltcp", branch = "main" } ``` into `Cargo.toml` and re-compiled shadowsocks-rust. I...