Re: Wireguard on Asahi Debian
Thats Asahi with Arch Linux however and not Debian On Thu, Dec 1, 2022 at 2:10 PM Jason A. Donenfeld wrote: > > On Thu, Dec 01, 2022 at 01:24:07PM +0100, Daniel wrote: > > Hi All, > > > > I installed Asahi/Debian Bookworm from > > > > https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/ > > > > and face a problem: installing wireguard shipped the Debian arm kernel > > and I can't get wg to work. > > > > Is there a solution for this ? > > Appears to be available in Asahi's kernel: > https://github.com/AsahiLinux/PKGBUILDs/blob/9fb6fddfdd388190c099a723f046acf7b8b6bd39/linux-asahi/config#L2462
Re: Wireguard on Asahi Debian
Ah i see On Thu, Dec 1, 2022 at 3:49 PM Daniel wrote: > > > Le 01/12/2022 à 15:26, Luna Jernberg a écrit : > > Thats Asahi with Arch Linux however and not Debian > https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/ > > > > On Thu, Dec 1, 2022 at 2:10 PM Jason A. Donenfeld wrote: > >> On Thu, Dec 01, 2022 at 01:24:07PM +0100, Daniel wrote: > >>> Hi All, > >>> > >>> I installed Asahi/Debian Bookworm from > >>> > >>> https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/ > >>> > >>> and face a problem: installing wireguard shipped the Debian arm kernel > >>> and I can't get wg to work. > >>> > >>> Is there a solution for this ? > >> Appears to be available in Asahi's kernel: > >> https://github.com/AsahiLinux/PKGBUILDs/blob/9fb6fddfdd388190c099a723f046acf7b8b6bd39/linux-asahi/config#L2462 > > -- > Daniel Huhardeaux > +33.368460...@tootai.net sip:8...@sip.tootai.net > +41.445532...@swiss-itech.chtootaiNET
DNS endpoint resolution in container namespace
Hi, I tried to follow the example here https://www.wireguard.com/netns/#ordinary-containerization but I found out that the DNS endpoint resolution through ip netns exec container wg setconf wg0 /etc/wireguard/wg0.conf won't work, because it is run in the new container namespace not yet capable of DNS resolution. Looking at the source code here https://git.zx2c4.com/wireguard-tools/tree/src/config.c#n242 confirmed my suspicion that the DNS resolution is done by the wg tool in the container namespace rather than in the original namespace. In an ideal world the DNS resolution should IMHO happen in the original namespace capable of DNS resolution where the world-facing UDP socket using that endpoint IP is anyway. Often one could use just a hard-coded IP (that's indeed what I resorted to in the end, or perform DNS resolution at container provisioning time as suggested by mrngm in IRC) for the wg0.conf in the container, but with DynDNS and similar setups this may not be possible. But since that might require significant changes (e.g. requesting DNS resolution in the original namespace through the kernel?), perhaps at least in the short term I would recommend that this caveat is mentioned on the webpage and/or perhaps in the example the `wg setconf` step would be run in the original namespace (unless there is some repercussion to that I did not consider). Best wishes and thanks for all your work making wireguard what it is today, Ondrej G.
Re: Wireguard - no logs iOS 16.1
Agreed, Save and Read do work. --oa On Mon, Nov 28, 2022 at 12:59 PM Ulrich Kalloch wrote: > > Am 05.11.22 um 23:20 schrieb Omkhar Arasaratnam: > > Wireguard 1.0.15 (26) > > Wireguard Go backend 2ef39d47 > > > > I am unable to view logs. Clicking on the view log button momentarily > > renders text, then it goes blank. Tried this on two different phones > > (iPhone 11 pro max, iPhone 13 Pro) > > > > --oa > > Same here. > > But Save and Read in Notes Works. > > Best
M1 Mac with OSX 12.6 wifi dropouts
Not sure if this is the right place to ask about it. But I have been using wireguard recently, and I have noticed that when I enable the VPN, my wifi signal immediately goes down 1 bar. Also, after some time of using it, the wifi will experience periodic dropouts (on the order of every 10 minutes to 2 hours) I’m clueless as to how wireguard can be causing this, but I found this situation by rebooting into safe mode, noting that the wifi did not have any problems, and then starting up wireguard to see the drop occur. I’m noticing that WG for mac hasn’t been updated for 1 year. Does anyone else experience this issue, or know of its cause? Will also agree that it’s possible WG isn’t the culprit, but I’m having a hard time narrowing it down. If anyone has experience in how to find what causes this, please let me know. -Steve
Re: Wireguard on Asahi Debian
On Thu, Dec 01, 2022 at 01:24:07PM +0100, Daniel wrote: > Hi All, > > I installed Asahi/Debian Bookworm from > > https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/ > > and face a problem: installing wireguard shipped the Debian arm kernel > and I can't get wg to work. > > Is there a solution for this ? Appears to be available in Asahi's kernel: https://github.com/AsahiLinux/PKGBUILDs/blob/9fb6fddfdd388190c099a723f046acf7b8b6bd39/linux-asahi/config#L2462
Re: Wireguard - no logs iOS 16.1
I have reproduced the issue on iPhone 13. Also occurred on iOS 16.0 -D > On 5 Nov 2022, at 22:20, Omkhar Arasaratnam wrote: > > Wireguard 1.0.15 (26) > Wireguard Go backend 2ef39d47 > > I am unable to view logs. Clicking on the view log button momentarily > renders text, then it goes blank. Tried this on two different phones > (iPhone 11 pro max, iPhone 13 Pro) > > --oa
Re: Wireguard on Asahi Debian
OK, wg is in the kernel, sorry to have bother you. Le 01/12/2022 à 13:24, Daniel a écrit : Hi All, I installed Asahi/Debian Bookworm from https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/ and face a problem: installing wireguard shipped the Debian arm kernel and I can't get wg to work. Is there a solution for this ? -- Daniel Huhardeaux +33.368460...@tootai.net sip:8...@sip.tootai.net +41.445532...@swiss-itech.chtootaiNET
Wireguard on Asahi Debian
Hi All, I installed Asahi/Debian Bookworm from https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/ and face a problem: installing wireguard shipped the Debian arm kernel and I can't get wg to work. Is there a solution for this ? -- Daniel
