Searched hist:"2 f29e846" (Results 1 – 3 of 3) sorted by relevance
| /openbsd/sbin/unwind/ |
| H A D | unwind.h | 2f29e846 Sat Mar 30 12:52:03 GMT 2019 florian <florian@openbsd.org> Shuffle captive portal detection around.
While we are behind a captive portal we have to ask the dhcp provided
resolvers. However it is possible that those resolvers do not like
to talk to unwind because of EDNS0.
Unwind handles this case by closing its listening socket and hands
over to asr. Except for the resolving of the captive portal host which
it still tries to resolve via libunbound.
Turns out there is no need for this we can just use getaddrinfo_async
from asr which then either hits unwind which does the right thing or
unwind closed its listening socket and asr moves on to talk directly
to the dhcp resolvers.
|
| H A D | unwind.c | 2f29e846 Sat Mar 30 12:52:03 GMT 2019 florian <florian@openbsd.org> Shuffle captive portal detection around.
While we are behind a captive portal we have to ask the dhcp provided
resolvers. However it is possible that those resolvers do not like
to talk to unwind because of EDNS0.
Unwind handles this case by closing its listening socket and hands
over to asr. Except for the resolving of the captive portal host which
it still tries to resolve via libunbound.
Turns out there is no need for this we can just use getaddrinfo_async
from asr which then either hits unwind which does the right thing or
unwind closed its listening socket and asr moves on to talk directly
to the dhcp resolvers.
|
| H A D | resolver.c | 2f29e846 Sat Mar 30 12:52:03 GMT 2019 florian <florian@openbsd.org> Shuffle captive portal detection around.
While we are behind a captive portal we have to ask the dhcp provided
resolvers. However it is possible that those resolvers do not like
to talk to unwind because of EDNS0.
Unwind handles this case by closing its listening socket and hands
over to asr. Except for the resolving of the captive portal host which
it still tries to resolve via libunbound.
Turns out there is no need for this we can just use getaddrinfo_async
from asr which then either hits unwind which does the right thing or
unwind closed its listening socket and asr moves on to talk directly
to the dhcp resolvers.
|