Patrick M. Hausen

A query to the primary IP address of the interface: ``` dig @172.16.0.2 www.punkt.de [...] ;; ANSWER SECTION: www.punkt.de. 299 IN A 217.29.40.141 ``` ``` 2021/05/13 07:57:42 [info] Received OOB...

Some more comments from Peter: > As I see it, the possibilities boil down to: > 1) The Go code isn't enabling IPPROTO_IP.IP_RECVDSTADDR on the socket. > 2) There's a...

``` $ dig @172.16.0.2 www.punkt.de [...] www.punkt.de. 299 IN A 217.29.40.141 [...] $ dig @172.16.0.3 www.punkt.de ;; reply from unexpected source: 172.16.0.2#53, expected 172.16.0.3#53 ;; reply from unexpected source: 172.16.0.2#53,...

I don't quite get it. I observe: ``` root@OPNsense:~ # netstat -na|grep 53 tcp46 0 0 *.53 *.* LISTEN udp46 0 0 *.53 *.* ``` But why is that the...

I see now. You are using an IPv4-mapped IPv6 address. Since you have an AF_INET6 socket, you cannot use AF_INET options via setsockopt(). Peter Jeremy wrote: > On Sun, May...

``` $ dig @172.16.0.2 www.punkt.de [...] ;; ANSWER SECTION: www.punkt.de. 299 IN A 217.29.40.141 $ dig @172.16.0.3 www.punkt.de ;; reply from unexpected source: 172.16.0.2#53, expected 172.16.0.3#53 ;; reply from unexpected...

I attached a system call trace. Possibly helpful? [ktrace.txt](https://github.com/AdguardTeam/AdGuardHome/files/6495968/ktrace.txt)

Thank you so very much. Glad I could help to pin this somewhere in the FreeBSD - golang - AdGuard Home Bermuda triangle.

Hi folks, just routinely checking my open issues. Is there any progress? Is there anything I can do to help? Kind regards, Patrick

> > Same - manually running sudo nfsd update in terminal resolves > > @unlovedsam What exactly did you do? I've run the command before the vagrant up command -...