wiki11

Now wireguard work. Thank you so mush. Little instruction for install wireguard on version debian 11 image v.3.0.11 looks like that 1) Install image on sd card 2) increase part /dev/mmcblk1p7, if you want update kernel 3) Download from link linux header and boot 4) sudo dpkg -i linux-headers-5.10.160_5.10.160-1_arm64.deb sudo reboot now 5) if you're using sd card image: sudo dd if=boot.img of=/dev/mmcblk1p4 status=progress && sync sudo reboot for emmc: sudo dd if=boot.img of=/dev/mmcblk0p4 status=progress && sync sudo reboot 6) sudo dpkg --purge raspi-firmware sudo reboot 7) sudo apt-get update sudo apt install wireguard

Hello. I check link https://www.asuswebstorage.com/navigate/a/#/MySync/NDI0MzgzMzMwLDgzNDM3Nzg2NSw4MzQzNzc4NjU%3D , but this link leads into personal account, and it is impossible to download file

I am sure in wg0.conf is working, because this config work on my laptop on debian 11

Hello @tooz. I install linux header and install boot.img. I still have errors anymore😓. It is looks like linaro@linaro-alip:~$ sudo wg-quick up wg0 [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.6.0.9/24 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] resolvconf -a tun.wg0 -m 0 -x [#] wg set wg0 fwmark 51820 [#] ip -6 route add ::/0 dev wg0 table 51820 [#] ip -6 rule add not fwmark 51820 table 51820 RTNETLINK answers: Operation not supported [#] resolvconf -d tun.wg0 -f [#] ip link delete dev wg0

If I remove raspi-firmware and fix install sudo apt install --fix-broken Then I try start wireguard and have next error linaro@linaro-alip:~$ sudo wg-quick up wg0 [#] ip link add wg0 type wireguard Error: Unknown device type. Unable to access interface: Protocol not supported [#] ip link delete dev wg0 Cannot find device "wg0"

When I use command in yours method I see next errors linaro@linaro-alip:~$ sudo apt install wireguard Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: liba52-0.7.4 libdca0 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: linux-image-5.10.0-28-rt-arm64 linux-image-rt-arm64 wireguard-tools Suggested packages: linux-doc-5.10 debian-kernel-handbook Recommended packages: apparmor The following NEW packages will be installed: linux-image-5.10.0-28-rt-arm64 linux-image-rt-arm64 wireguard wireguard-tools 0 upgraded, 4 newly installed, 0 to remove and 64 not upgraded. Need to get 44.8 MB of archives. After this operation, 252 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://deb.debian.org/debian bullseye/main arm64 linux-image-5.10.0-28-rt-arm64 arm64 5.10.209-2 [44.7 MB] Get:2 http://deb.debian.org/debian bullseye/main arm64 linux-image-rt-arm64 arm64 5.10.209-2 [1452 B] Get:3 http://deb.debian.org/debian bullseye/main arm64 wireguard-tools arm64 1.0.20210223-1 [88.9 kB] Get:4 http://deb.debian.org/debian bullseye/main arm64 wireguard all 1.0.20210223-1 [8164 B] Fetched 44.8 MB in 5s (9296 kB/s) Selecting previously unselected package linux-image-5.10.0-28-rt-arm64. (Reading database ... 87219 files and directories currently installed.) Preparing to unpack .../linux-image-5.10.0-28-rt-arm64_5.10.209-2_arm64.deb ... Unpacking linux-image-5.10.0-28-rt-arm64 (5.10.209-2) ... Selecting previously unselected package linux-image-rt-arm64. Preparing to unpack .../linux-image-rt-arm64_5.10.209-2_arm64.deb ... Unpacking linux-image-rt-arm64 (5.10.209-2) ... Selecting previously unselected package wireguard-tools. Preparing to unpack .../wireguard-tools_1.0.20210223-1_arm64.deb ... Unpacking wireguard-tools (1.0.20210223-1) ... Selecting previously unselected package wireguard. Preparing to unpack .../wireguard_1.0.20210223-1_all.deb ... Unpacking wireguard (1.0.20210223-1) ... Setting up linux-image-5.10.0-28-rt-arm64 (5.10.209-2) ... I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.10.0-28-rt-arm64 I: /boot/initrd.img.old is now a symlink to initrd.img-5.10.0-28-rt-arm64 I: /boot/vmlinuz is now a symlink to vmlinuz-5.10.0-28-rt-arm64 I: /boot/initrd.img is now a symlink to initrd.img-5.10.0-28-rt-arm64 /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.10.0-28-rt-arm64 raspi-firmware: missing /boot/firmware, did you forget to mount it? run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return code 1 run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-5.10.0-28-rt-arm64 (--configure): installed linux-image-5.10.0-28-rt-arm64 package post-installation script subprocess returned error exit status 1 Setting up wireguard-tools (1.0.20210223-1) ... wg-quick.target is a disabled or a static unit, not starting it. dpkg: dependency problems prevent configuration of linux-image-rt-arm64: linux-image-rt-arm64 depends on linux-image-5.10.0-28-rt-arm64 (= 5.10.209-2); however: Package linux-image-5.10.0-28-rt-arm64 is not configured yet. dpkg: error processing package linux-image-rt-arm64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of wireguard: wireguard depends on wireguard-modules (>= 0.0.20191219) | wireguard-dkms (>= 0.0.20200121-2); however: Package wireguard-modules is not installed. Package linux-image-rt-arm64 which provides wireguard-modules is not configured yet. Package wireguard-dkms is not installed. dpkg: error processing package wireguard (--configure): dependency problems - leaving unconfigured Processing triggers for man-db (2.9.4-2) ... Errors were encountered while processing: linux-image-5.10.0-28-rt-arm64 linux-image-rt-arm64 wireguard I need to remove raspi-firmware to be solve that problem? I find on forum that maybe problem with it

Sorry, my mistake, I write wrong version. I use debian 11 image v.3.0.11

I use debian 11 image v.3.0.11 and i have problem with install wireguard on this version

It is look like module wireguard not include in kernel 5.10.160, аlthough kernel after 5.6 must have module wireguard include on base

Hello. Maybe you made a mistake in name of linux headers? If i install linux-headers-5.10.110 and then install wireguard, I see next errors wg-quick.target is a disabled or a static unit, not starting it. Setting up dctrl-tools (2.24-3) ... Setting up dkms (2.8.4-3) ... Setting up wireguard-dkms (1.0.20210219-1) ... Loading new wireguard-1.0.20210219 DKMS files... It is likely that 5.10.160 belongs to a chroot's host Building for 5.10.110, 5.10.160, hci_uart.ko and rtk_btusb.ko Building initial module for 5.10.110 Error! The /var/lib/dkms/wireguard/1.0.20210219/5.10.110/aarch64/dkms.conf for module wireguard includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. This indicates that it should not be built. Skipped. Module build for kernel 5.10.160 was skipped since the kernel headers for this kernel does not seem to be installed. Module build for kernel hci_uart.ko was skipped since the kernel headers for this kernel does not seem to be installed. Module build for kernel rtk_btusb.ko was skipped since the kernel headers for this kernel does not seem to be installed. After this I reinstall system on microsd and first install linux-headers-5.10.160 and then wireguard. I see next errors Loading new wireguard-1.0.20210219 DKMS files... It is likely that 5.10.160 belongs to a chroot's host Building for 5.10.160, hci_uart.ko and rtk_btusb.ko Building initial module for 5.10.160 Error! The /var/lib/dkms/wireguard/1.0.20210219/5.10.160/aarch64/dkms.conf for module wireguard includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. This indicates that it should not be built. Skipped. Module build for kernel hci_uart.ko was skipped since the kernel headers for this kernel does not seem to be installed. Module build for kernel rtk_btusb.ko was skipped since the kernel headers for this kernel does not seem to be installed.

When I used command apt install wireguard wireguard-dkms I see next warning wg-quick.target is a disabled or a static unit, not starting it. Module build for kernel 5.10.160 was skipped since the kernel headers for this kernel does not seem to be installed. Module build for kernel hci_uart.ko was skipped since the kernel headers for this kernel does not seem to be installed. Module build for kernel rtk_btusb.ko was skipped since the kernel headers for this kernel does not seem to be installed. All console log from install in file. It is before i install linux headers log.txt

Hello. Somebody have problem to install wireguard to image Tinker Board 2 Debian 11 (kernel 5.10) v3.0.6 ? I install linux headers to version 5.10.160 from here here. Then i used command dpkg -i linux-headers-5.10.160_5.10.160-1_arm64.deb reboot apt install --reinstall wireguard reboot modprobe wireguard modprobe: FATAL: Module wireguard not found in directory /lib/modules/5.10.160 After errors I try install newest kernel from repository debian and install new linux headers, but it can't solve my problem. Has anyone encountered a similar error and knows how to solve it?