On Sun, Jan 15, 2017 at 8:40 PM, Jason A. Donenfeld wrote:
> Hi Peter,
>
> On Mon, Jan 9, 2017 at 2:43 PM, Peter Dolding wrote:
>> You example gets you a connection. You example does not cope with IP
>> change as that happens in NAT environments.
>
> Yes, example only code.
>
>> VPN detects con
Two things I have not seen so far:
- government regulations that enforce NAT
- ISPs (let alone carriers) "upgrading" their networks to ipv6 nat (i myself
have run both, isp + carrier networks, and i call BS on your future outlook
regarding nat ipv6)
- code from you in this thread
> On 18 Jan 2
On Sun, Jan 15, 2017 at 6:39 PM, Dan Lüdtke wrote:
> Hi Peter,
>
> I followed this thread and like to express some concerns. Although I see the
> problem and ran into it myself, I would like to see a solution outside the
> wireguard code. Like the one Jason proposed or even a new approach. I am
Actually, even more reliable, send the output of:
pacman -Qo /lib/modules/$(uname -r)
___
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
Can you send the output of:
for i in vmlinuz-linux kernel.img Image zImage uImage; do [[ -f
/boot/$i ]] && pacman -Qo /boot/$i; done
___
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
Hi again,
I'm now trying to get wireguard running on my raspberry pi with archARM
[0]. I installed wireguard-dkms, wireguard-tools and
linux-raspberrypi-headers and now get:
alarm@alarmpi ~/wireguard ❯❯❯ sudo modprobe wireguard
modprobe: FATAL: Module wireguard not found in directory
/lib/modules
