From: Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>
To: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Cc: Ahmad Gani <reyuki@gnuweeb.org>,
"GNU/Weeb Mailing List" <gwml@vger.gnuweeb.org>
Subject: Re: [PATCH gwproxy v13 0/8] Initial work on integration of DNS parser lib in gwproxy
Date: Thu, 2 Oct 2025 14:20:44 +0700 [thread overview]
Message-ID: <CAOG64qM-OAzmf=1-DLFMgXkcRAbOY2NbmCHJBTH8U=-jxenwhA@mail.gmail.com> (raw)
In-Reply-To: <20251002070502.GA18177-ammarfaizi2@gnuweeb.org>
On Thu, Oct 2, 2025 at 2:05 PM Ammar Faizi wrote:
> It fails to connect when "socks5h" protocol is used.
ic ic, I think I found the problem. In short, we should resend the UDP
buffer if gwp_dns_res_complete_query() throws -EAGAIN.
How does it work?
* First, the DNS resolver will try to resolve IPv4 first if
--socks5-prefer-ipv6 is not used.
* If no IPv4 record is not found and it has the ability to go with
IPv6, gwp_dns_res_complete_query() will return -EAGAIN and fill the
UDP buffer with IPv6 resolution payload.
* The resolver is expected to send the IPv6 resolution payload in
that case, but my code didn't handle that.
Can you test this patch and confirm if it fixes the problem?
https://gist.githubusercontent.com/alviroiskandar/f8d5b3ce7f30753613646508dd7ef356/raw/be63c7b68e9f576e7904fa21ee13857b1b3031b1/ipv6_fix.diff
next prev parent reply other threads:[~2025-10-02 7:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 8:54 [PATCH gwproxy v13 0/8] Initial work on integration of DNS parser lib in gwproxy Alviro Iskandar Setiawan
2025-09-30 8:54 ` [PATCH gwproxy v13 1/8] gwproxy: Remove 'struct gwp_dns_query' declaration Alviro Iskandar Setiawan
2025-09-30 8:54 ` [PATCH gwproxy v13 2/8] gwproxy: Introduce __unused macro Alviro Iskandar Setiawan
2025-09-30 8:54 ` [PATCH gwproxy v13 3/8] Add DNS parser code Alviro Iskandar Setiawan
2025-09-30 8:54 ` [PATCH gwproxy v13 4/8] Add DNS resolver code Alviro Iskandar Setiawan
2025-09-30 8:54 ` [PATCH gwproxy v13 5/8] dns_resolver: Add DNS resolution interface APIs Alviro Iskandar Setiawan
2025-09-30 8:54 ` [PATCH gwproxy v13 6/8] gwproxy: Introduce --dns-server and --raw-dns Alviro Iskandar Setiawan
2025-09-30 8:54 ` [PATCH gwproxy v13 7/8] epoll: Intregrate the raw DNS feature to epoll Alviro Iskandar Setiawan
2025-09-30 8:54 ` [PATCH gwproxy v13 8/8] Makefile: Introduce --use-new-dns-resolver configure option Alviro Iskandar Setiawan
2025-10-02 7:05 ` [PATCH gwproxy v13 0/8] Initial work on integration of DNS parser lib in gwproxy Ammar Faizi
2025-10-02 7:20 ` Alviro Iskandar Setiawan [this message]
2025-10-02 8:07 ` Ammar Faizi
2025-10-02 8:19 ` Alviro Iskandar Setiawan
2025-10-26 21:10 ` Ammar Faizi
2025-10-29 16:33 ` Alviro Iskandar Setiawan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOG64qM-OAzmf=1-DLFMgXkcRAbOY2NbmCHJBTH8U=-jxenwhA@mail.gmail.com' \
--to=alviro.iskandar@gnuweeb.org \
--cc=ammarfaizi2@gnuweeb.org \
--cc=gwml@vger.gnuweeb.org \
--cc=reyuki@gnuweeb.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox