search

cmulk / wireguard-docker

Wireguard setup in Docker meant for a simple personal VPN
345 stars 92 forks source link

image on synology "RTNETLINK answers: Not supported" #30

Open cscholz opened 2 years ago

cscholz commented 2 years ago

I've deployed the alpine image as described and get the following log errors. I've tried it with a shared host docker network and also with a non host shared network. Do you have a hint for me?

2021-12-21 18:52:13,stdout,Tue Dec 21 18:52:13 UTC 2021: Starting Wireguard /etc/wireguard/wg0.conf
2021-12-21 18:52:13,stdout,Warning: `/etc/wireguard/wg0.conf' is world accessible
2021-12-21 18:52:13,stdout,[#] ip link add wg0 type wireguard
2021-12-21 18:52:13,stdout,RTNETLINK answers: Not supported
2021-12-21 18:52:13,stdout,Unable to access interface: Protocol not supported
2021-12-21 18:52:13,stdout,[#] ip link delete dev wg0
2021-12-21 18:52:13,stdout,Cannot find device "wg0"
2021-12-21 18:52:13,stdout,Adding iptables NAT rule
2021-12-21 18:52:13,stdout,ip6tables v1.8.6 (legacy): can't initialize ip6tables table `nat': Table does not exist (do you need to insmod?)
2021-12-21 18:52:13,stdout,Perhaps ip6tables or your kernel needs to be upgraded.
2021-12-21 18:52:31,stdout,Tue Dec 21 18:52:31 UTC 2021: Shutting down Wireguard
2021-12-21 18:52:31,stdout,Warning: `/etc/wireguard/wg0.conf' is world accessible
2021-12-21 18:52:31,stdout,wg-quick: `wg0' is not a WireGuard interface
2021-12-21 18:52:31,stdout,ip6tables v1.8.6 (legacy): can't initialize ip6tables table `nat': Table does not exist (do you need to insmod?)
2021-12-21 18:52:31,stdout,Perhaps ip6tables or your kernel needs to be upgraded.
cmulk commented 2 years ago

I have a couple of possible things: I'm guessing the device is some other architecture (maybe arm?) and the images here have only been built for amd64. They should build fine for other architectures (minus the kernel installation piece) since it is only bash scripts, but you would need to build an image specifically for that platform.

I think the first RNETLINK answers: Not supported may mean that the device's kernel doesn't have wireguard included or a wireguard module. You would have to do more research on that to see if synology has an available kernel or kernel module for wireguard