pdjm

  • Posts

    3
  • Joined

  • Last visited

Everything posted by pdjm

  1. Yes that's right, but i think there is no normal image for rock pi S. Is that the problem?
  2. No, I don't know how, only happens on the rock pi, in a fresh image, no changes made in the system. In zeropi works just fine
  3. Hi Trying to use a rock pi S board as a wireguard server I get this problem: pedro@rockpi-s:~$ sudo wg-quick up wg0 [sudo] password for pedro: [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.9.0.1/24 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] resolvconf -a tun.wg0 -m 0 -x /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf [#] iptables -A FORWARD -i wg0 -j ACCEPT; iptables -A FORWARD -o wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE /usr/bin/wg-quick: line 295: iptables: command not found [#] resolvconf -d tun.wg0 -f /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf [#] ip link delete dev wg0 pedro@rockpi-s:~$ The config file I use: [Interface] Address = 10.9.0.1/24 ListenPort = 51820 DNS = 1.1.1.1 PrivateKey = xxxxxxxxxxxxx PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE [Peer] #Peer-1 PublicKey = xxxxxxxxxxxxxxxx AllowedIPs = 10.9.0.2/32 #PersistentkeepAlive = 60 and this is my armbianmonitor log: https://cl1p.net/uqzugurbasvlt With my other board, a zeropi board, wireguard is working ok, but not with the rock pi, is this related to download page saying it´s a minimal legacy kernel? Thanks!