It appears there is a diff in snaps. Should be fixed soon.
-Otto
On Wed, Nov 06, 2019 at 04:41:42PM +0100, Felix Maschek wrote:
> Done so. But I'm not able to understand the trace. I have attached it.
>
> Kind regards
>
> Felix
>
> On 2019-11-06 16:29, Otto Moerbeek wrote:
> > On Wed, Nov 06, 2019 at 04:16:10PM +0100, Felix Maschek wrote:
> >
> > > Hi,
> > >
> > > unwind is running and does talk to 9.9.9.9 (checked with DNS Leak Test -
> > > bash.ws <https://bash.ws/dnsleak>):
> > >
> > > vatrox$ ps -A | grep unwind
> > > 42668 ?? Ip 0:00.01 /sbin/unwind
> > > 42070 ?? IpU 0:03.27 unwind: resolver (unwind)
> > > 43163 ?? Ip 0:00.09 unwind: frontend (unwind)
> > > 59857 ?? Ip 0:00.01 unwind: captive portal (unwind)
> > > 72389 p1 R+/2 0:00.00 grep unwind
> > >
> > > The socket is missing:
> > >
> > > vatrox$ ls /var/run
> > > ConsoleKit cron.sock dev.db ld.so.hints rc.d
> > > syslog.pid utmp
> > > apmdev dbus dmesg.boot ntpd.sock smtpd.sock user
> > Strange. Tge code is structured in such a way that failure to cerate the
> > socket is fatal.
> >
> > Once thing to try:
> >
> > run
> > ktrace -i rcctl start unwind
> >
> > and then
> > rcctl stop unwind
> > kdump > /tmp/d
> >
> > amd inspect /tmp/d to find out what happended to the socket.
> >
> > -Otto
> >
> > > Kind regards
> > >
> > > Felix
> > >
> > > On 2019-11-06 16:08, Otto Moerbeek wrote:
> > > > On Wed, Nov 06, 2019 at 03:41:10PM +0100, Felix Maschek wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I've used unwind for some weeks and observed a problem after
> > > > > upgrading to
> > > > > last snapshot (after some weeks).
> > > > >
> > > > > Calling unwindctl leads to the following error message:
> > > > >
> > > > > vatrox$ unwindctl status DoT
> > > > > unwindctl: connect: /var/run/unwind.sock: No such file or
> > > > > directory
> > > > >
> > > > > My configuration (which still is functional):
> > > > >
> > > > > /etc/rc.conf.local:
> > > > >
> > > > > unwind_flags=""
> > > > >
> > > > > /etc/dhclient.conf:
> > > > >
> > > > > prepend domain-name-servers 127.0.0.1;
> > > > >
> > > > > /etc/unwind.conf:
> > > > >
> > > > > forwarder 9.9.9.9 port 853 authentication name
> > > > > dns.quad9.net DoT
> > > > >
> > > > > Any idea?
> > > > Is unwind running? Does /var/run/unwind.sock exist?
> > > >
> > > > -Otto
> > > >
>
