* RTNETLINK answers: Operation not supported
@ 2017-08-05 19:38 Sahil Gupta
2017-08-06 16:30 ` Sahil Gupta
0 siblings, 1 reply; 9+ messages in thread
From: Sahil Gupta @ 2017-08-05 19:38 UTC (permalink / raw)
To: WireGuard mailing list, Eric Light, Jason A. Donenfeld
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
Hi,
I am not able to setup Wireguard interface on Raspberry pi.
Error:
RTNETLINK answers: Operation not supported
See the stack:
"
pi@raspberrypi:~ $ cd /etc/wireguard/
pi@raspberrypi:/etc/wireguard $ l
-bash: l: command not found
pi@raspberrypi:/etc/wireguard $ ls
publickey wg0.conf
pi@raspberrypi:/etc/wireguard $ history | grep wg0
15 history | grep wg0
pi@raspberrypi:/etc/wireguard $ ip link add wg0 type wireguard
RTNETLINK answers: Operation not permitted
pi@raspberrypi:/etc/wireguard $ sudo su
root@raspberrypi:/etc/wireguard# wg-quick up wg0
Warning: `/etc/wireguard/wg0.conf' is world accessible
[#] ip link add wg0 type wireguard
RTNETLINK answers: Operation not supported
`wg0` is not a valid WireGuard interface
Usage: wg show { <interface> | all | interfaces } [public-key | private-key
| listen-port | fwmark | peers | preshared-keys | endpoints | allowed-ips |
latest-handshakes | transfer | persistent-keepalive | dump]
root@raspberrypi:/etc/wireguard# wg show
root@raspberrypi:/etc/wireguard# wg show all
root@raspberrypi:/etc/wireguard#
"
Any pointers will be appreciated.
Thanks
Sahil Gupta
[-- Attachment #2: Type: text/html, Size: 1479 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: RTNETLINK answers: Operation not supported 2017-08-05 19:38 RTNETLINK answers: Operation not supported Sahil Gupta @ 2017-08-06 16:30 ` Sahil Gupta 2017-08-06 16:33 ` Sahil Gupta 0 siblings, 1 reply; 9+ messages in thread From: Sahil Gupta @ 2017-08-06 16:30 UTC (permalink / raw) To: WireGuard mailing list, Eric Light, Jason A. Donenfeld [-- Attachment #1: Type: text/plain, Size: 16481 bytes --] I have tried to install linux headers but still showing the same error. Here's the stack to process. " pi@raspberrypi:~ $ sudo dpkg -i linux-headers-4.9.31-v7+_4.9.31-v7+-2_armhf.deb Selecting previously unselected package linux-headers-4.9.31-v7+. (Reading database ... 132946 files and directories currently installed.) Preparing to unpack linux-headers-4.9.31-v7+_4.9.31-v7+-2_armhf.deb ... Unpacking linux-headers-4.9.31-v7+ (4.9.31-v7+-2) ... dpkg: dependency problems prevent configuration of linux-headers-4.9.31-v7+: linux-headers-4.9.31-v7+ depends on bc; however: Package bc is not installed. dpkg: error processing package linux-headers-4.9.31-v7+ (--install): dependency problems - leaving unconfigured Errors were encountered while processing: linux-headers-4.9.31-v7+ pi@raspberrypi:~ $ lsmod | grep wireguard pi@raspberrypi:~ $ sudo apt-get install wireguard-dkms wireguard-tools Reading package lists... Done Building dependency tree Reading state information... Done wireguard-dkms is already the newest version (0.0.20170726-1). wireguard-tools is already the newest version (0.0.20170726-1). You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-4.9.31-v7+ : Depends: bc but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). pi@raspberrypi:~ $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: bc The following NEW packages will be installed: bc 0 upgraded, 1 newly installed, 0 to remove and 855 not upgraded. 1 not fully installed or removed. Need to get 101 kB of archives. After this operation, 212 kB of additional disk space will be used. Do you want to continue? [Y/n] Y WARNING: The following packages cannot be authenticated! bc Install these packages without verification? [y/N] y Get:1 http://deb.debian.org/debian unstable/main armhf bc armhf 1.06.95-9+b3 [101 kB] Fetched 101 kB in 0s (226 kB/s) Selecting previously unselected package bc. (Reading database ... 148260 files and directories currently installed.) Preparing to unpack .../bc_1.06.95-9+b3_armhf.deb ... Unpacking bc (1.06.95-9+b3) ... Processing triggers for install-info (5.2.0.dfsg.1-6) ... Processing triggers for man-db (2.7.5-1~bpo8+1) ... Setting up bc (1.06.95-9+b3) ... Setting up linux-headers-4.9.31-v7+ (4.9.31-v7+-2) ... make: Entering directory '/usr/src/linux-headers-4.9.31-v7+' HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/bin2c HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf *** Default configuration is based on 'bcm2709_defconfig' # # configuration written to .config # make: Leaving directory '/usr/src/linux-headers-4.9.31-v7+' make: Entering directory '/usr/src/linux-headers-4.9.31-v7+' scripts/kconfig/conf --silentoldconfig Kconfig CHK include/config/kernel.release UPD include/config/kernel.release WRAP arch/arm/include/generated/asm/bitsperlong.h WRAP arch/arm/include/generated/asm/clkdev.h WRAP arch/arm/include/generated/asm/cputime.h WRAP arch/arm/include/generated/asm/current.h WRAP arch/arm/include/generated/asm/early_ioremap.h WRAP arch/arm/include/generated/asm/emergency-restart.h WRAP arch/arm/include/generated/asm/errno.h WRAP arch/arm/include/generated/asm/exec.h WRAP arch/arm/include/generated/asm/ioctl.h WRAP arch/arm/include/generated/asm/ipcbuf.h WRAP arch/arm/include/generated/asm/irq_regs.h WRAP arch/arm/include/generated/asm/kdebug.h WRAP arch/arm/include/generated/asm/local.h WRAP arch/arm/include/generated/asm/local64.h WRAP arch/arm/include/generated/asm/mm-arch-hooks.h WRAP arch/arm/include/generated/asm/msgbuf.h WRAP arch/arm/include/generated/asm/msi.h WRAP arch/arm/include/generated/asm/param.h WRAP arch/arm/include/generated/asm/parport.h WRAP arch/arm/include/generated/asm/poll.h WRAP arch/arm/include/generated/asm/preempt.h WRAP arch/arm/include/generated/asm/resource.h WRAP arch/arm/include/generated/asm/rwsem.h WRAP arch/arm/include/generated/asm/seccomp.h WRAP arch/arm/include/generated/asm/segment.h WRAP arch/arm/include/generated/asm/sembuf.h WRAP arch/arm/include/generated/asm/serial.h WRAP arch/arm/include/generated/asm/shmbuf.h WRAP arch/arm/include/generated/asm/siginfo.h WRAP arch/arm/include/generated/asm/simd.h WRAP arch/arm/include/generated/asm/sizes.h WRAP arch/arm/include/generated/asm/socket.h WRAP arch/arm/include/generated/asm/sockios.h WRAP arch/arm/include/generated/asm/termbits.h WRAP arch/arm/include/generated/asm/termios.h WRAP arch/arm/include/generated/asm/timex.h WRAP arch/arm/include/generated/asm/trace_clock.h WRAP arch/arm/include/generated/asm/unaligned.h CHK include/generated/uapi/linux/version.h UPD include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h UPD include/generated/utsrelease.h GEN include/generated/mach-types.h CC kernel/bounds.s CHK include/generated/bounds.h UPD include/generated/bounds.h CHK include/generated/timeconst.h UPD include/generated/timeconst.h CC arch/arm/kernel/asm-offsets.s CHK include/generated/asm-offsets.h UPD include/generated/asm-offsets.h CALL scripts/checksyscalls.sh grep: scripts/../arch/x86/entry/syscalls/syscall_32.tbl: No such file or directory HOSTCC scripts/dtc/dtc.o HOSTCC scripts/dtc/flattree.o HOSTCC scripts/dtc/fstree.o HOSTCC scripts/dtc/data.o HOSTCC scripts/dtc/livetree.o HOSTCC scripts/dtc/treesource.o HOSTCC scripts/dtc/srcpos.o HOSTCC scripts/dtc/checks.o HOSTCC scripts/dtc/util.o HOSTCC scripts/dtc/dtc-lexer.lex.o HOSTCC scripts/dtc/dtc-parser.tab.o HOSTLD scripts/dtc/dtc HOSTCC scripts/genksyms/genksyms.o HOSTCC scripts/genksyms/parse.tab.o SHIPPED scripts/genksyms/lex.lex.c HOSTCC scripts/genksyms/lex.lex.o HOSTLD scripts/genksyms/genksyms CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig MKELF scripts/mod/elfconfig.h HOSTCC scripts/mod/modpost.o CC scripts/mod/devicetable-offsets.s GEN scripts/mod/devicetable-offsets.h HOSTCC scripts/mod/file2alias.o HOSTCC scripts/mod/sumversion.o HOSTLD scripts/mod/modpost HOSTCC scripts/kallsyms HOSTCC scripts/pnmtologo HOSTCC scripts/conmakehash HOSTCC scripts/recordmcount HOSTCC scripts/sortextable make: Leaving directory '/usr/src/linux-headers-4.9.31-v7+' -------- Uninstall Beginning -------- Module: wireguard Version: 0.0.20170726-1 Kernel: 4.9.35+ (armv7l) ------------------------------------- Status: Before uninstall, this module version was ACTIVE on this kernel. wireguard.ko: - Uninstallation - Deleting from: /lib/modules/4.9.35+/kernel/net/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod... DKMS: uninstall completed. -------- Uninstall Beginning -------- Module: wireguard Version: 0.0.20170726-1 Kernel: 4.9.35-v7+ (armv7l) ------------------------------------- Status: Before uninstall, this module version was ACTIVE on this kernel. wireguard.ko: - Uninstallation - Deleting from: /lib/modules/4.9.35-v7+/kernel/net/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod... DKMS: uninstall completed. ------------------------------ Deleting module version: 0.0.20170726-1 completely from the DKMS tree. ------------------------------ Done. Loading new wireguard-0.0.20170726-1 DKMS files... It is likely that 4.9.35-v7+ belongs to a chroot's host Building for 3.6-trunk-rpi, 4.9.31-v7+, 4.9.35+ and 4.9.35-v7+ Building initial module for 3.6-trunk-rpi Error! The dkms.conf for this module includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. This indicates that it should not be built. Skipped. Building initial module for 4.9.31-v7+ Done. wireguard: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.9.31-v7+/kernel/net/ depmod... DKMS: install completed. Building initial module for 4.9.35+ Done. wireguard: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.9.35+/kernel/net/ depmod... DKMS: install completed. Building initial module for 4.9.35-v7+ Done. wireguard: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.9.35-v7+/kernel/net/ depmod... DKMS: install completed. -------- Uninstall Beginning -------- Module: wireguard Version: 0.0.20170726-1 Kernel: 4.9.31-v7+ (armv7l) ------------------------------------- Status: Before uninstall, this module version was ACTIVE on this kernel. wireguard.ko: - Uninstallation - Deleting from: /lib/modules/4.9.31-v7+/kernel/net/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod... DKMS: uninstall completed. -------- Uninstall Beginning -------- Module: wireguard Version: 0.0.20170726-1 Kernel: 4.9.35+ (armv7l) ------------------------------------- Status: Before uninstall, this module version was ACTIVE on this kernel. wireguard.ko: - Uninstallation - Deleting from: /lib/modules/4.9.35+/kernel/net/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod... DKMS: uninstall completed. -------- Uninstall Beginning -------- Module: wireguard Version: 0.0.20170726-1 Kernel: 4.9.35-v7+ (armv7l) ------------------------------------- Status: Before uninstall, this module version was ACTIVE on this kernel. wireguard.ko: - Uninstallation - Deleting from: /lib/modules/4.9.35-v7+/kernel/net/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod... DKMS: uninstall completed. ------------------------------ Deleting module version: 0.0.20170726-1 completely from the DKMS tree. ------------------------------ Done. Loading new wireguard-0.0.20170726-1 DKMS files... It is likely that 4.9.35-v7+ belongs to a chroot's host Building for 3.6-trunk-rpi, 4.9.31-v7+, 4.9.35+ and 4.9.35-v7+ Building initial module for 3.6-trunk-rpi Error! The dkms.conf for this module includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. This indicates that it should not be built. Skipped. Building initial module for 4.9.31-v7+ Done. wireguard: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.9.31-v7+/kernel/net/ depmod... DKMS: install completed. Building initial module for 4.9.35+ Done. wireguard: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.9.35+/kernel/net/ depmod... DKMS: install completed. Building initial module for 4.9.35-v7+ Done. wireguard: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.9.35-v7+/kernel/net/ depmod... DKMS: install completed. pi@raspberrypi:~ $ lsmod | grep wireguard pi@raspberrypi:~ $ ip link add dev wg0 type wireguard RTNETLINK answers: Operation not permitted pi@raspberrypi:~ $ sudo apt-get install wireguard-dkms wireguard-tools Reading package lists... Done Building dependency tree Reading state information... Done wireguard-dkms is already the newest version (0.0.20170726-1). wireguard-tools is already the newest version (0.0.20170726-1). 0 upgraded, 0 newly installed, 0 to remove and 855 not upgraded. pi@raspberrypi:~ $ lsmod | grep wireguard pi@raspberrypi:~ $ ip link add dev wg0 type wireguard RTNETLINK answers: Operation not permitted pi@raspberrypi:~ $ sudo apt-get purge wireguard-dkms wireguard-tools Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dkms libmnl0 linux-headers-3.6-trunk-common linux-headers-3.6-trunk-rpi linux-kbuild-3.6 Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: wireguard-dkms* wireguard-tools* 0 upgraded, 0 newly installed, 2 to remove and 855 not upgraded. After this operation, 918 kB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 148279 files and directories currently installed.) Removing wireguard-dkms (0.0.20170726-1) ... -------- Uninstall Beginning -------- Module: wireguard Version: 0.0.20170726-1 Kernel: 4.9.31-v7+ (armv7l) ------------------------------------- Status: Before uninstall, this module version was ACTIVE on this kernel. wireguard.ko: - Uninstallation - Deleting from: /lib/modules/4.9.31-v7+/kernel/net/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod... DKMS: uninstall completed. -------- Uninstall Beginning -------- Module: wireguard Version: 0.0.20170726-1 Kernel: 4.9.35+ (armv7l) ------------------------------------- Status: Before uninstall, this module version was ACTIVE on this kernel. wireguard.ko: - Uninstallation - Deleting from: /lib/modules/4.9.35+/kernel/net/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod... DKMS: uninstall completed. -------- Uninstall Beginning -------- Module: wireguard Version: 0.0.20170726-1 Kernel: 4.9.35-v7+ (armv7l) ------------------------------------- Status: Before uninstall, this module version was ACTIVE on this kernel. wireguard.ko: - Uninstallation - Deleting from: /lib/modules/4.9.35-v7+/kernel/net/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod... DKMS: uninstall completed. ------------------------------ Deleting module version: 0.0.20170726-1 completely from the DKMS tree. ------------------------------ Done. Removing wireguard-tools (0.0.20170726-1) ... dpkg: warning: while removing wireguard-tools, directory '/etc/wireguard' not empty so not removed Processing triggers for man-db (2.7.5-1~bpo8+1) ... " On Sat, Aug 5, 2017 at 3:38 PM, Sahil Gupta <sg5414@g.rit.edu> wrote: > Hi, > I am not able to setup Wireguard interface on Raspberry pi. > > Error: > RTNETLINK answers: Operation not supported > > > See the stack: > " > pi@raspberrypi:~ $ cd /etc/wireguard/ > pi@raspberrypi:/etc/wireguard $ l > -bash: l: command not found > pi@raspberrypi:/etc/wireguard $ ls > publickey wg0.conf > pi@raspberrypi:/etc/wireguard $ history | grep wg0 > 15 history | grep wg0 > pi@raspberrypi:/etc/wireguard $ ip link add wg0 type wireguard > RTNETLINK answers: Operation not permitted > pi@raspberrypi:/etc/wireguard $ sudo su > root@raspberrypi:/etc/wireguard# wg-quick up wg0 > Warning: `/etc/wireguard/wg0.conf' is world accessible > [#] ip link add wg0 type wireguard > RTNETLINK answers: Operation not supported > `wg0` is not a valid WireGuard interface > Usage: wg show { <interface> | all | interfaces } [public-key | > private-key | listen-port | fwmark | peers | preshared-keys | endpoints | > allowed-ips | latest-handshakes | transfer | persistent-keepalive | dump] > root@raspberrypi:/etc/wireguard# wg show > root@raspberrypi:/etc/wireguard# wg show all > root@raspberrypi:/etc/wireguard# > > " > > Any pointers will be appreciated. > > Thanks > Sahil Gupta > [-- Attachment #2: Type: text/html, Size: 22417 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: RTNETLINK answers: Operation not supported 2017-08-06 16:30 ` Sahil Gupta @ 2017-08-06 16:33 ` Sahil Gupta 2017-08-06 16:34 ` Jason A. Donenfeld 0 siblings, 1 reply; 9+ messages in thread From: Sahil Gupta @ 2017-08-06 16:33 UTC (permalink / raw) To: WireGuard mailing list, Eric Light, Jason A. Donenfeld [-- Attachment #1: Type: text/plain, Size: 17724 bytes --] If I am correct to make wireguard work. You require three components 1. wireguard-dkms 2. wireguard-tools 3. linux headers I tried "linux-headers-4.9.31-v7+_4.9.31-v7+-2_armhf.deb" Please correct me if I am using wrong linux header for compilation. Thanks Sahil On Sun, Aug 6, 2017 at 12:30 PM, Sahil Gupta <sg5414@g.rit.edu> wrote: > I have tried to install linux headers but still showing the same error. > > Here's the stack to process. > " > pi@raspberrypi:~ $ sudo dpkg -i linux-headers-4.9.31-v7+_4.9. > 31-v7+-2_armhf.deb > Selecting previously unselected package linux-headers-4.9.31-v7+. > (Reading database ... 132946 files and directories currently installed.) > Preparing to unpack linux-headers-4.9.31-v7+_4.9.31-v7+-2_armhf.deb ... > Unpacking linux-headers-4.9.31-v7+ (4.9.31-v7+-2) ... > dpkg: dependency problems prevent configuration of > linux-headers-4.9.31-v7+: > linux-headers-4.9.31-v7+ depends on bc; however: > Package bc is not installed. > > dpkg: error processing package linux-headers-4.9.31-v7+ (--install): > dependency problems - leaving unconfigured > Errors were encountered while processing: > linux-headers-4.9.31-v7+ > pi@raspberrypi:~ $ lsmod | grep wireguard > pi@raspberrypi:~ $ sudo apt-get install wireguard-dkms wireguard-tools > Reading package lists... Done > Building dependency tree > Reading state information... Done > wireguard-dkms is already the newest version (0.0.20170726-1). > wireguard-tools is already the newest version (0.0.20170726-1). > You might want to run 'apt --fix-broken install' to correct these. > The following packages have unmet dependencies: > linux-headers-4.9.31-v7+ : Depends: bc but it is not going to be installed > E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or > specify a solution). > pi@raspberrypi:~ $ sudo apt --fix-broken install > Reading package lists... Done > Building dependency tree > Reading state information... Done > Correcting dependencies... Done > The following additional packages will be installed: > bc > The following NEW packages will be installed: > bc > 0 upgraded, 1 newly installed, 0 to remove and 855 not upgraded. > 1 not fully installed or removed. > Need to get 101 kB of archives. > After this operation, 212 kB of additional disk space will be used. > Do you want to continue? [Y/n] Y > WARNING: The following packages cannot be authenticated! > bc > Install these packages without verification? [y/N] y > Get:1 http://deb.debian.org/debian unstable/main armhf bc armhf > 1.06.95-9+b3 [101 kB] > Fetched 101 kB in 0s (226 kB/s) > Selecting previously unselected package bc. > (Reading database ... 148260 files and directories currently installed.) > Preparing to unpack .../bc_1.06.95-9+b3_armhf.deb ... > Unpacking bc (1.06.95-9+b3) ... > Processing triggers for install-info (5.2.0.dfsg.1-6) ... > Processing triggers for man-db (2.7.5-1~bpo8+1) ... > Setting up bc (1.06.95-9+b3) ... > Setting up linux-headers-4.9.31-v7+ (4.9.31-v7+-2) ... > make: Entering directory '/usr/src/linux-headers-4.9.31-v7+' > HOSTCC scripts/basic/fixdep > HOSTCC scripts/basic/bin2c > HOSTCC scripts/kconfig/conf.o > HOSTCC scripts/kconfig/zconf.tab.o > HOSTLD scripts/kconfig/conf > *** Default configuration is based on 'bcm2709_defconfig' > # > # configuration written to .config > # > make: Leaving directory '/usr/src/linux-headers-4.9.31-v7+' > make: Entering directory '/usr/src/linux-headers-4.9.31-v7+' > scripts/kconfig/conf --silentoldconfig Kconfig > CHK include/config/kernel.release > UPD include/config/kernel.release > WRAP arch/arm/include/generated/asm/bitsperlong.h > WRAP arch/arm/include/generated/asm/clkdev.h > WRAP arch/arm/include/generated/asm/cputime.h > WRAP arch/arm/include/generated/asm/current.h > WRAP arch/arm/include/generated/asm/early_ioremap.h > WRAP arch/arm/include/generated/asm/emergency-restart.h > WRAP arch/arm/include/generated/asm/errno.h > WRAP arch/arm/include/generated/asm/exec.h > WRAP arch/arm/include/generated/asm/ioctl.h > WRAP arch/arm/include/generated/asm/ipcbuf.h > WRAP arch/arm/include/generated/asm/irq_regs.h > WRAP arch/arm/include/generated/asm/kdebug.h > WRAP arch/arm/include/generated/asm/local.h > WRAP arch/arm/include/generated/asm/local64.h > WRAP arch/arm/include/generated/asm/mm-arch-hooks.h > WRAP arch/arm/include/generated/asm/msgbuf.h > WRAP arch/arm/include/generated/asm/msi.h > WRAP arch/arm/include/generated/asm/param.h > WRAP arch/arm/include/generated/asm/parport.h > WRAP arch/arm/include/generated/asm/poll.h > WRAP arch/arm/include/generated/asm/preempt.h > WRAP arch/arm/include/generated/asm/resource.h > WRAP arch/arm/include/generated/asm/rwsem.h > WRAP arch/arm/include/generated/asm/seccomp.h > WRAP arch/arm/include/generated/asm/segment.h > WRAP arch/arm/include/generated/asm/sembuf.h > WRAP arch/arm/include/generated/asm/serial.h > WRAP arch/arm/include/generated/asm/shmbuf.h > WRAP arch/arm/include/generated/asm/siginfo.h > WRAP arch/arm/include/generated/asm/simd.h > WRAP arch/arm/include/generated/asm/sizes.h > WRAP arch/arm/include/generated/asm/socket.h > WRAP arch/arm/include/generated/asm/sockios.h > WRAP arch/arm/include/generated/asm/termbits.h > WRAP arch/arm/include/generated/asm/termios.h > WRAP arch/arm/include/generated/asm/timex.h > WRAP arch/arm/include/generated/asm/trace_clock.h > WRAP arch/arm/include/generated/asm/unaligned.h > CHK include/generated/uapi/linux/version.h > UPD include/generated/uapi/linux/version.h > CHK include/generated/utsrelease.h > UPD include/generated/utsrelease.h > GEN include/generated/mach-types.h > CC kernel/bounds.s > CHK include/generated/bounds.h > UPD include/generated/bounds.h > CHK include/generated/timeconst.h > UPD include/generated/timeconst.h > CC arch/arm/kernel/asm-offsets.s > CHK include/generated/asm-offsets.h > UPD include/generated/asm-offsets.h > CALL scripts/checksyscalls.sh > grep: scripts/../arch/x86/entry/syscalls/syscall_32.tbl: No such file or > directory > HOSTCC scripts/dtc/dtc.o > HOSTCC scripts/dtc/flattree.o > HOSTCC scripts/dtc/fstree.o > HOSTCC scripts/dtc/data.o > HOSTCC scripts/dtc/livetree.o > HOSTCC scripts/dtc/treesource.o > HOSTCC scripts/dtc/srcpos.o > HOSTCC scripts/dtc/checks.o > HOSTCC scripts/dtc/util.o > HOSTCC scripts/dtc/dtc-lexer.lex.o > HOSTCC scripts/dtc/dtc-parser.tab.o > HOSTLD scripts/dtc/dtc > HOSTCC scripts/genksyms/genksyms.o > HOSTCC scripts/genksyms/parse.tab.o > SHIPPED scripts/genksyms/lex.lex.c > HOSTCC scripts/genksyms/lex.lex.o > HOSTLD scripts/genksyms/genksyms > CC scripts/mod/empty.o > HOSTCC scripts/mod/mk_elfconfig > MKELF scripts/mod/elfconfig.h > HOSTCC scripts/mod/modpost.o > CC scripts/mod/devicetable-offsets.s > GEN scripts/mod/devicetable-offsets.h > HOSTCC scripts/mod/file2alias.o > HOSTCC scripts/mod/sumversion.o > HOSTLD scripts/mod/modpost > HOSTCC scripts/kallsyms > HOSTCC scripts/pnmtologo > HOSTCC scripts/conmakehash > HOSTCC scripts/recordmcount > HOSTCC scripts/sortextable > make: Leaving directory '/usr/src/linux-headers-4.9.31-v7+' > > -------- Uninstall Beginning -------- > Module: wireguard > Version: 0.0.20170726-1 > Kernel: 4.9.35+ (armv7l) > ------------------------------------- > > Status: Before uninstall, this module version was ACTIVE on this kernel. > > wireguard.ko: > - Uninstallation > - Deleting from: /lib/modules/4.9.35+/kernel/net/ > - Original module > - No original module was found for this module on this kernel. > - Use the dkms install command to reinstall any previous module version. > > depmod... > > DKMS: uninstall completed. > > -------- Uninstall Beginning -------- > Module: wireguard > Version: 0.0.20170726-1 > Kernel: 4.9.35-v7+ (armv7l) > ------------------------------------- > > Status: Before uninstall, this module version was ACTIVE on this kernel. > > wireguard.ko: > - Uninstallation > - Deleting from: /lib/modules/4.9.35-v7+/kernel/net/ > - Original module > - No original module was found for this module on this kernel. > - Use the dkms install command to reinstall any previous module version. > > depmod... > > DKMS: uninstall completed. > > ------------------------------ > Deleting module version: 0.0.20170726-1 > completely from the DKMS tree. > ------------------------------ > Done. > Loading new wireguard-0.0.20170726-1 DKMS files... > It is likely that 4.9.35-v7+ belongs to a chroot's host > Building for 3.6-trunk-rpi, 4.9.31-v7+, 4.9.35+ and 4.9.35-v7+ > Building initial module for 3.6-trunk-rpi > Error! The dkms.conf for this module includes a BUILD_EXCLUSIVE directive > which > does not match this kernel/arch. This indicates that it should not be > built. > Skipped. > Building initial module for 4.9.31-v7+ > Done. > > wireguard: > Running module version sanity check. > - Original module > - No original module exists within this kernel > - Installation > - Installing to /lib/modules/4.9.31-v7+/kernel/net/ > > depmod... > > DKMS: install completed. > Building initial module for 4.9.35+ > Done. > > wireguard: > Running module version sanity check. > - Original module > - No original module exists within this kernel > - Installation > - Installing to /lib/modules/4.9.35+/kernel/net/ > > depmod... > > DKMS: install completed. > Building initial module for 4.9.35-v7+ > Done. > > wireguard: > Running module version sanity check. > - Original module > - No original module exists within this kernel > - Installation > - Installing to /lib/modules/4.9.35-v7+/kernel/net/ > > depmod... > > DKMS: install completed. > > -------- Uninstall Beginning -------- > Module: wireguard > Version: 0.0.20170726-1 > Kernel: 4.9.31-v7+ (armv7l) > ------------------------------------- > > Status: Before uninstall, this module version was ACTIVE on this kernel. > > wireguard.ko: > - Uninstallation > - Deleting from: /lib/modules/4.9.31-v7+/kernel/net/ > - Original module > - No original module was found for this module on this kernel. > - Use the dkms install command to reinstall any previous module version. > > depmod... > > DKMS: uninstall completed. > > -------- Uninstall Beginning -------- > Module: wireguard > Version: 0.0.20170726-1 > Kernel: 4.9.35+ (armv7l) > ------------------------------------- > > Status: Before uninstall, this module version was ACTIVE on this kernel. > > wireguard.ko: > - Uninstallation > - Deleting from: /lib/modules/4.9.35+/kernel/net/ > - Original module > - No original module was found for this module on this kernel. > - Use the dkms install command to reinstall any previous module version. > > depmod... > > DKMS: uninstall completed. > > -------- Uninstall Beginning -------- > Module: wireguard > Version: 0.0.20170726-1 > Kernel: 4.9.35-v7+ (armv7l) > ------------------------------------- > > Status: Before uninstall, this module version was ACTIVE on this kernel. > > wireguard.ko: > - Uninstallation > - Deleting from: /lib/modules/4.9.35-v7+/kernel/net/ > - Original module > - No original module was found for this module on this kernel. > - Use the dkms install command to reinstall any previous module version. > > depmod... > > DKMS: uninstall completed. > > ------------------------------ > Deleting module version: 0.0.20170726-1 > completely from the DKMS tree. > ------------------------------ > Done. > Loading new wireguard-0.0.20170726-1 DKMS files... > It is likely that 4.9.35-v7+ belongs to a chroot's host > Building for 3.6-trunk-rpi, 4.9.31-v7+, 4.9.35+ and 4.9.35-v7+ > Building initial module for 3.6-trunk-rpi > Error! The dkms.conf for this module includes a BUILD_EXCLUSIVE directive > which > does not match this kernel/arch. This indicates that it should not be > built. > Skipped. > Building initial module for 4.9.31-v7+ > Done. > > wireguard: > Running module version sanity check. > - Original module > - No original module exists within this kernel > - Installation > - Installing to /lib/modules/4.9.31-v7+/kernel/net/ > > depmod... > > DKMS: install completed. > Building initial module for 4.9.35+ > Done. > > wireguard: > Running module version sanity check. > - Original module > - No original module exists within this kernel > - Installation > - Installing to /lib/modules/4.9.35+/kernel/net/ > > depmod... > > DKMS: install completed. > Building initial module for 4.9.35-v7+ > Done. > > wireguard: > Running module version sanity check. > - Original module > - No original module exists within this kernel > - Installation > - Installing to /lib/modules/4.9.35-v7+/kernel/net/ > > depmod... > > DKMS: install completed. > pi@raspberrypi:~ $ lsmod | grep wireguard > pi@raspberrypi:~ $ ip link add dev wg0 type wireguard > RTNETLINK answers: Operation not permitted > pi@raspberrypi:~ $ sudo apt-get install wireguard-dkms wireguard-tools > Reading package lists... Done > Building dependency tree > Reading state information... Done > wireguard-dkms is already the newest version (0.0.20170726-1). > wireguard-tools is already the newest version (0.0.20170726-1). > 0 upgraded, 0 newly installed, 0 to remove and 855 not upgraded. > pi@raspberrypi:~ $ lsmod | grep wireguard > pi@raspberrypi:~ $ ip link add dev wg0 type wireguard > RTNETLINK answers: Operation not permitted > pi@raspberrypi:~ $ sudo apt-get purge wireguard-dkms wireguard-tools > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following packages were automatically installed and are no longer > required: > dkms libmnl0 linux-headers-3.6-trunk-common linux-headers-3.6-trunk-rpi > linux-kbuild-3.6 > Use 'sudo apt autoremove' to remove them. > The following packages will be REMOVED: > wireguard-dkms* wireguard-tools* > 0 upgraded, 0 newly installed, 2 to remove and 855 not upgraded. > After this operation, 918 kB disk space will be freed. > Do you want to continue? [Y/n] Y > (Reading database ... 148279 files and directories currently installed.) > Removing wireguard-dkms (0.0.20170726-1) ... > > -------- Uninstall Beginning -------- > Module: wireguard > Version: 0.0.20170726-1 > Kernel: 4.9.31-v7+ (armv7l) > ------------------------------------- > > Status: Before uninstall, this module version was ACTIVE on this kernel. > > wireguard.ko: > - Uninstallation > - Deleting from: /lib/modules/4.9.31-v7+/kernel/net/ > - Original module > - No original module was found for this module on this kernel. > - Use the dkms install command to reinstall any previous module version. > > depmod... > > DKMS: uninstall completed. > > -------- Uninstall Beginning -------- > Module: wireguard > Version: 0.0.20170726-1 > Kernel: 4.9.35+ (armv7l) > ------------------------------------- > > Status: Before uninstall, this module version was ACTIVE on this kernel. > > wireguard.ko: > - Uninstallation > - Deleting from: /lib/modules/4.9.35+/kernel/net/ > - Original module > - No original module was found for this module on this kernel. > - Use the dkms install command to reinstall any previous module version. > > depmod... > > DKMS: uninstall completed. > > -------- Uninstall Beginning -------- > Module: wireguard > Version: 0.0.20170726-1 > Kernel: 4.9.35-v7+ (armv7l) > ------------------------------------- > > Status: Before uninstall, this module version was ACTIVE on this kernel. > > wireguard.ko: > - Uninstallation > - Deleting from: /lib/modules/4.9.35-v7+/kernel/net/ > - Original module > - No original module was found for this module on this kernel. > - Use the dkms install command to reinstall any previous module version. > > depmod... > > DKMS: uninstall completed. > > ------------------------------ > Deleting module version: 0.0.20170726-1 > completely from the DKMS tree. > ------------------------------ > Done. > Removing wireguard-tools (0.0.20170726-1) ... > dpkg: warning: while removing wireguard-tools, directory '/etc/wireguard' > not empty so not removed > Processing triggers for man-db (2.7.5-1~bpo8+1) ... > > " > > On Sat, Aug 5, 2017 at 3:38 PM, Sahil Gupta <sg5414@g.rit.edu> wrote: > >> Hi, >> I am not able to setup Wireguard interface on Raspberry pi. >> >> Error: >> RTNETLINK answers: Operation not supported >> >> >> See the stack: >> " >> pi@raspberrypi:~ $ cd /etc/wireguard/ >> pi@raspberrypi:/etc/wireguard $ l >> -bash: l: command not found >> pi@raspberrypi:/etc/wireguard $ ls >> publickey wg0.conf >> pi@raspberrypi:/etc/wireguard $ history | grep wg0 >> 15 history | grep wg0 >> pi@raspberrypi:/etc/wireguard $ ip link add wg0 type wireguard >> RTNETLINK answers: Operation not permitted >> pi@raspberrypi:/etc/wireguard $ sudo su >> root@raspberrypi:/etc/wireguard# wg-quick up wg0 >> Warning: `/etc/wireguard/wg0.conf' is world accessible >> [#] ip link add wg0 type wireguard >> RTNETLINK answers: Operation not supported >> `wg0` is not a valid WireGuard interface >> Usage: wg show { <interface> | all | interfaces } [public-key | >> private-key | listen-port | fwmark | peers | preshared-keys | endpoints | >> allowed-ips | latest-handshakes | transfer | persistent-keepalive | dump] >> root@raspberrypi:/etc/wireguard# wg show >> root@raspberrypi:/etc/wireguard# wg show all >> root@raspberrypi:/etc/wireguard# >> >> " >> >> Any pointers will be appreciated. >> >> Thanks >> Sahil Gupta >> > > [-- Attachment #2: Type: text/html, Size: 23656 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: RTNETLINK answers: Operation not supported 2017-08-06 16:33 ` Sahil Gupta @ 2017-08-06 16:34 ` Jason A. Donenfeld 2017-08-06 18:31 ` Sahil Gupta 0 siblings, 1 reply; 9+ messages in thread From: Jason A. Donenfeld @ 2017-08-06 16:34 UTC (permalink / raw) To: Sahil Gupta; +Cc: WireGuard mailing list pi@raspberrypi:~ $ ip link add dev wg0 type wireguard RTNETLINK answers: Operation not permitted This needs to be run as root, using sudo. sudo ip link add dev wg0 type wireguard After this, it should work. I believe you worked out the prior issues already by installing the headers package and bc and whatnot. Please stop sending duplicate emails to the mailing list. Collect your thoughts in single coherent messages, and email the list directly rather than individual members. The barrage of the last 48 hours -- when many of us are not available since it's the weekend -- has been a bit annoying. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: RTNETLINK answers: Operation not supported 2017-08-06 16:34 ` Jason A. Donenfeld @ 2017-08-06 18:31 ` Sahil Gupta 2017-08-06 18:36 ` Jason A. Donenfeld 0 siblings, 1 reply; 9+ messages in thread From: Sahil Gupta @ 2017-08-06 18:31 UTC (permalink / raw) To: Jason A. Donenfeld; +Cc: WireGuard mailing list [-- Attachment #1: Type: text/plain, Size: 9199 bytes --] Thanks for reply. That problem is resolve. I am in new difficultly now. Scenario. We have three system say laptop L1, laptop L2 and raspberry pi (say pi). L1 and L2 are connected with wireless interface(wlan0). L1 and pi connected from ethernet interface via ethernet cable. Now, L1 wlan ip: 192.168.0.9 L1 eth0 ip: 10.42.0.1 L2 wlan ip: 192.168.0.11 pi eth0 ip: 10.42.0.2 L1 wg0 ip: 10.0.0.6 L2 wg0 ip: 10.0.0.2 pi wg0 ip: 10.0.0.3 Now problem is L1 and pi executing ping command but L1 and L2 don't. <============================================================================================> *Connectivity:* L1(eth0 : 10.42.0.1, wg0 : 10.0.0.6, wlan0 : 192.168.0.9) ⇔ L2(wlan0 : 192.168.0.11,wg0 : 10.0.0.2 ) ⇕ pi (eth0:10.42.0.2,wg0:10.0.0.3) <=============================================================================================> *Config file of L1:* [Interface] PrivateKey = 6Ew/TWF8+ofWSnk1Mxmb+8D8Kx9ZIP2SjcxBKkmXnGo= ListenPort = 12345 Address = 10.0.0.6/24 [Peer] PublicKey = r+F7hbLjN3J4qc75V734DW2H28BVh8ydkCkK1Lf8blY= Endpoint = 192.168.0.11:12345 AllowedIPs = 10.0.0.0/24 [Peer] PublicKey = hkZUDze5qDILltpjoaYe+vG1qcYqTtKg8E3nawix92k= Endpoint = 10.42.0.2:12345 AllowedIPs = 10.0.0.0/24 <=============================================================================================> *Config file of L2:* [Interface] PrivateKey = SICBGQ/vbASs5Xoo0AK1cMy9CbLpfxlCAD2Ap+TACEo= ListenPort = 12345 Address = 10.0.0.2/24 [Peer] PublicKey = duJE8ANouuvgL5IZM7oMWCdluvMlCvjZCDe8BJIVg34= Endpoint = 192.168.0.9:12345 AllowedIPs = 10.0.0.0/24 <=============================================================================================> *Config file of pi:* [Interface] PrivateKey = kNFqEj9bB8CUx7mfGdc4UR1uYtj647X5HKdx7XPbGFA= ListenPort = 12345 Address = 10.0.0.3/24 [Peer] PublicKey = duJE8ANouuvgL5IZM7oMWCdluvMlCvjZCDe8BJIVg34= Endpoint = 10.42.0.1:12345 AllowedIPs = 10.0.0.0/24 <=============================================================================================> *Terminal of L1:* sahilgupta221@sahilgupta221-Inspiron-3543:/etc/wireguard$ sudo wg-quick up wg0 Warning: `/etc/wireguard/wg0.conf' is world accessible [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip address add 10.0.0.6/24 dev wg0 [#] ip link set mtu 1420 dev wg0 [#] ip link set wg0 up sahilgupta221@sahilgupta221-Inspiron-3543:/etc/wireguard$ ping 10.0.0.2 PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. ^C --- 10.0.0.2 ping statistics --- 294 packets transmitted, 0 received, 100% packet loss, time 293003ms sahilgupta221@sahilgupta221-Inspiron-3543:/etc/wireguard$ ping 10.0.0.3 PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data. 64 bytes from 10.0.0.3: icmp_seq=1 ttl=64 time=13.1 ms 64 bytes from 10.0.0.3: icmp_seq=2 ttl=64 time=0.922 ms 64 bytes from 10.0.0.3: icmp_seq=3 ttl=64 time=0.934 ms 64 bytes from 10.0.0.3: icmp_seq=4 ttl=64 time=0.718 ms 64 bytes from 10.0.0.3: icmp_seq=5 ttl=64 time=0.949 ms 64 bytes from 10.0.0.3: icmp_seq=6 ttl=64 time=0.902 ms 64 bytes from 10.0.0.3: icmp_seq=7 ttl=64 time=0.829 ms 64 bytes from 10.0.0.3: icmp_seq=8 ttl=64 time=0.907 ms ^C --- 10.0.0.3 ping statistics --- 8 packets transmitted, 8 received, 0% packet loss, time 7004ms rtt min/avg/max/mdev = 0.718/2.410/13.120/4.048 ms sahilgupta221@sahilgupta221-Inspiron-3543:/etc/wireguard$ <=============================================================================================> *Terminal of L2*: sahilgupta221@sahilgupta221-900X3B-900X4B:/etc/wireguard$ sudo wg-quick up wg0 [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip address add 10.0.0.2/24 dev wg0 [#] ip link set mtu 1420 dev wg0 [#] ip link set wg0 up sahilgupta221@sahilgupta221-900X3B-900X4B:/etc/wireguard$ ping 10.0.0.6 PING 10.0.0.6 (10.0.0.6) 56(84) bytes of data. ^C --- 10.0.0.6 ping statistics --- 246 packets transmitted, 0 received, 100% packet loss, time 250882ms sahilgupta221@sahilgupta221-900X3B-900X4B:/etc/wireguard$ ping 10.0.0.2 PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. 64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=0.129 ms 64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=0.074 ms 64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=0.080 ms 64 bytes from 10.0.0.2: icmp_seq=4 ttl=64 time=0.077 ms 64 bytes from 10.0.0.2: icmp_seq=5 ttl=64 time=0.073 ms 64 bytes from 10.0.0.2: icmp_seq=6 ttl=64 time=0.072 ms 64 bytes from 10.0.0.2: icmp_seq=7 ttl=64 time=0.070 ms 64 bytes from 10.0.0.2: icmp_seq=8 ttl=64 time=0.075 ms 64 bytes from 10.0.0.2: icmp_seq=9 ttl=64 time=0.076 ms ^C --- 10.0.0.2 ping statistics --- 9 packets transmitted, 9 received, 0% packet loss, time 8200ms rtt min/avg/max/mdev = 0.070/0.080/0.129/0.020 ms sahilgupta221@sahilgupta221-900X3B-900X4B:/etc/wireguard$ ping 10.0.0.3 PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data. ^C --- 10.0.0.3 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1007ms sahilgupta221@sahilgupta221-900X3B-900X4B:/etc/wireguard$ sudo chmod 777 * [sudo] password for sahilgupta221: sahilgupta221@sahilgupta221-900X3B-900X4B:/etc/wireguard$ <=============================================================================================> *Terminal of pi:* pi@raspberrypi:~ $ sudo wg-quick up wg0 Warning: `/etc/wireguard/wg0.conf' is world accessible [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip address add 10.0.0.3/24 dev wg0 [#] ip link set mtu 1420 dev wg0 [#] ip link set wg0 up pi@raspberrypi:~ $ ping 10.0.0.6 PING 10.0.0.6 (10.0.0.6) 56(84) bytes of data. 64 bytes from 10.0.0.6: icmp_seq=1 ttl=64 time=5015 ms 64 bytes from 10.0.0.6: icmp_seq=2 ttl=64 time=4009 ms 64 bytes from 10.0.0.6: icmp_seq=3 ttl=64 time=2969 ms 64 bytes from 10.0.0.6: icmp_seq=4 ttl=64 time=1929 ms 64 bytes from 10.0.0.6: icmp_seq=5 ttl=64 time=890 ms 64 bytes from 10.0.0.6: icmp_seq=6 ttl=64 time=0.829 ms 64 bytes from 10.0.0.6: icmp_seq=7 ttl=64 time=4.16 ms 64 bytes from 10.0.0.6: icmp_seq=8 ttl=64 time=0.883 ms 64 bytes from 10.0.0.6: icmp_seq=9 ttl=64 time=0.849 ms 64 bytes from 10.0.0.6: icmp_seq=10 ttl=64 time=4.08 ms ^C --- 10.0.0.6 ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9245ms rtt min/avg/max/mdev = 0.829/1482.655/5015.674/1805.291 ms, pipe 5 pi@raspberrypi:~ $ ^C pi@raspberrypi:~ $ ifconfig eth0 Link encap:Ethernet HWaddr b8:27:eb:ab:0e:3b inet addr:10.42.0.2 Bcast:10.42.0.255 Mask:255.255.255.0 inet6 addr: fe80::ba27:ebff:feab:e3b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:638 errors:0 dropped:0 overruns:0 frame:0 TX packets:316 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:73672 (71.9 KiB) TX bytes:38774 (37.8 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wg0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:10.0.0.3 P-t-P:10.0.0.3 Mask:255.255.255.0 UP POINTOPOINT RUNNING NOARP MTU:1420 Metric:1 RX packets:307 errors:0 dropped:0 overruns:0 frame:0 TX packets:50 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:25812 (25.2 KiB) TX bytes:3988 (3.8 KiB) pi@raspberrypi:~ $ nano w pi@raspberrypi:~ $ ^C pi@raspberrypi:~ $ cd /etc/wireguard/ pi@raspberrypi:/etc/wireguard $ nano wg0.conf pi@raspberrypi:/etc/wireguard $ ping 10.0.0.2 PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. ^C --- 10.0.0.2 ping statistics --- 23 packets transmitted, 0 received, 100% packet loss, time 22891ms <=============================================================================================> *Summarry*: Q1: How can I connectivity between L1 and L2? Q2: Do I need to maintain two different wireguard interfaces for each LAN connection? Q3: If answer to Q2 is yes then how L2 can ping to pi? Q4: Why pi can't ping to L2? Terminal response will verifies the problem. <============================================================================================> *PS: Apologies for disturbing on weekends. Didn't realize weekend part. * *These are summer holidays here. Each day is same to me.Some of people like, you, Eric,Christian Hesse etc. are super experts on certain matters.My selfishness is that I want the quick response to accelerate work.* *So approached in this manner.* *Not sure of duplicate part. I think I only send two messages.One solution to problem and other requesting the tutorial.Next time I will maintain single thread for particular problem.Please reply whenever feel free.* 😊 Sorry and Thanks again Sahil Gupta [-- Attachment #2: Type: text/html, Size: 19963 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: RTNETLINK answers: Operation not supported 2017-08-06 18:31 ` Sahil Gupta @ 2017-08-06 18:36 ` Jason A. Donenfeld 0 siblings, 0 replies; 9+ messages in thread From: Jason A. Donenfeld @ 2017-08-06 18:36 UTC (permalink / raw) To: Sahil Gupta; +Cc: WireGuard mailing list On Sun, Aug 6, 2017 at 8:31 PM, Sahil Gupta <sg5414@rit.edu> wrote: > PS: Apologies for disturbing on weekends. Didn't realize weekend part. > These are summer holidays here. Each day is same to me. > Some of people like, you, Eric,Christian Hesse etc. are super experts on certain matters. > My selfishness is that I want the quick response to accelerate work. The problem isn't that you emailed on the weekend. Everyone emails on weekends; that's what they're for! The problem is that you sent the same issue several times to several different addresses, and kept sending the same email, before you even waited to receive a response. When I finally loaded up my box, it wasn't very nice to see the same HTML-filled email 6 different times. So, we're happy to help here, but please relax a bit and give us time. ^ permalink raw reply [flat|nested] 9+ messages in thread
* RTNETLINK answers: Operation not supported @ 2017-02-28 16:08 William Clark 2017-02-28 22:21 ` Lucian Cristian 2017-03-01 8:14 ` Jörg Thalheim 0 siblings, 2 replies; 9+ messages in thread From: William Clark @ 2017-02-28 16:08 UTC (permalink / raw) To: WireGuard [-- Attachment #1: Type: text/plain, Size: 677 bytes --] Hello, So I wanted to try WireGuard but unfortunately I can't get pas this part: ip link add dev wg0 type wireguard. When ever I run the command "ip link add dev wg0 type wireguard" I get the output: RTNETLINK answers: Operation not supported This both happens on CentOS 7 and Fedora 25 and Ubuntu 16.04. CentOS 7 Kernel: Linux hostname 3.10.0-514.6.2.el7.x86_64 #1 SMP Thu Feb 23 03:04:39 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Fedora 25 Kernel: Linux hostname 4.9.7-x86_64-X #2 SMP Thu Feb 2 15:43:55 EST 2017 x86_64 x86_64 x86_64 GNU/Linux I've tried installing Linux headers too, but no luck and I've rebooted after the upgrade too, and still no luck. Thanks a lot. [-- Attachment #2: Type: text/html, Size: 1757 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: RTNETLINK answers: Operation not supported 2017-02-28 16:08 William Clark @ 2017-02-28 22:21 ` Lucian Cristian 2017-03-01 8:14 ` Jörg Thalheim 1 sibling, 0 replies; 9+ messages in thread From: Lucian Cristian @ 2017-02-28 22:21 UTC (permalink / raw) To: wireguard [-- Attachment #1: Type: text/plain, Size: 1044 bytes --] On 28.02.2017 18:08, William Clark wrote: > Hello, > > So I wanted to try WireGuard but unfortunately I can't get pas this part: > ip link add dev wg0 type wireguard. > > When ever I run the command "ip link add dev wg0 type wireguard" > I get the output: > RTNETLINK answers: Operation not supported > > This both happens on CentOS 7 and Fedora 25 and Ubuntu 16.04. > > CentOS 7 Kernel: > Linux hostname 3.10.0-514.6.2.el7.x86_64 #1 SMP Thu Feb 23 03:04:39 > UTC 2017 x86_64 x86_64 x86_64 GNU/Linux > Fedora 25 Kernel: > Linux hostname 4.9.7-x86_64-X #2 SMP Thu Feb 2 15:43:55 EST 2017 > x86_64 x86_64 x86_64 GNU/Linux > > I've tried installing Linux headers too, but no luck and I've rebooted > after the upgrade too, and still no luck. > > Thanks a lot. > > > _______________________________________________ > WireGuard mailing list > WireGuard@lists.zx2c4.com > https://lists.zx2c4.com/mailman/listinfo/wireguard I'm using centos 7 (even centos 6) with kernel-ml or kernel-lt from elrepo, 3.10 is not supported by wireguard Regards [-- Attachment #2: Type: text/html, Size: 3360 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: RTNETLINK answers: Operation not supported 2017-02-28 16:08 William Clark 2017-02-28 22:21 ` Lucian Cristian @ 2017-03-01 8:14 ` Jörg Thalheim 1 sibling, 0 replies; 9+ messages in thread From: Jörg Thalheim @ 2017-03-01 8:14 UTC (permalink / raw) To: wireguard On 2017-02-28 17:08, William Clark wrote: > Hello, > > So I wanted to try WireGuard but unfortunately I can't get pas this part: > ip link add dev wg0 type wireguard. > > When ever I run the command "ip link add dev wg0 type wireguard" > I get the output: > RTNETLINK answers: Operation not supported > > This both happens on CentOS 7 and Fedora 25 and Ubuntu 16.04. > > CentOS 7 Kernel: > Linux hostname 3.10.0-514.6.2.el7.x86_64 #1 SMP Thu Feb 23 03:04:39 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux > Fedora 25 Kernel: > Linux hostname 4.9.7-x86_64-X #2 SMP Thu Feb 2 15:43:55 EST 2017 x86_64 x86_64 x86_64 GNU/Linux > > I've tried installing Linux headers too, but no luck and I've rebooted after the upgrade too, and still no luck. > > Thanks a lot. If the following commands do not succeed, the wireguard kernel module was not installed correctly: $ modprobe wireguard $ lsmod | grep wireguard wireguard 126976 0 x_tables 28672 2 xt_hashlimit,wireguard ip6_udp_tunnel 16384 1 wireguard udp_tunnel 16384 1 wireguard ipv6 401408 162 nf_conntrack_ipv6,nf_defrag_ipv6,wireguard,bridge ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2017-08-06 18:14 UTC | newest] Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2017-08-05 19:38 RTNETLINK answers: Operation not supported Sahil Gupta 2017-08-06 16:30 ` Sahil Gupta 2017-08-06 16:33 ` Sahil Gupta 2017-08-06 16:34 ` Jason A. Donenfeld 2017-08-06 18:31 ` Sahil Gupta 2017-08-06 18:36 ` Jason A. Donenfeld -- strict thread matches above, loose matches on Subject: below -- 2017-02-28 16:08 William Clark 2017-02-28 22:21 ` Lucian Cristian 2017-03-01 8:14 ` Jörg Thalheim
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.