From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Ahmad Gani <reyuki@gnuweeb.org>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>
Subject: Re: (subset) [PATCH gwproxy v5 0/2] Initial work on integration of DNS parser lib in gwproxy
Date: Sat, 16 Aug 2025 23:41:16 +0700 [thread overview]
Message-ID: <175536228502.177146.5466707683679177795@gnuweeb.org> (raw)
In-Reply-To: <20250814044658.252579-1-reyuki@gnuweeb.org>
On Thu, 14 Aug 2025 11:46:53 +0700, Ahmad Gani wrote:
> This is revision v5 of initial work on integration of DNS parser lib in
> gwproxy. This is an RFC draft, the patches itself aren't final.
>
> With current model, the caller is responsible to do the socket part, this
> imply unlike conventional glibc's getaddrinfo that handle both socket and
> crafting payload inside its abstraction, thus allow AF_UNSPEC, the build
> query only craft packet for particular family at a time [1], either
> AF_INET or AF_INET6, not both, I see this not as a limitation, but rather
> an advantage, most of the time we don't need to request for both IPv6 and
> IPv4, but there's still a case where both family is desired, it's often
> happened for fallback mechanism. I'll spend some time thinking about how
> to integrate these functions into gwproxy.
>
> [...]
Applied, thanks!
[1/2] dns: Allow only port string number
commit: efad824958d533fc943c2b0ac27f76d20f0d3957
Best regards,
--
Ammar Faizi <ammarfaizi2@gnuweeb.org>
prev parent reply other threads:[~2025-08-16 16:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 4:46 [PATCH gwproxy v5 0/2] Initial work on integration of DNS parser lib in gwproxy Ahmad Gani
2025-08-14 4:46 ` [PATCH gwproxy v5 1/2] dns: Allow only port string number Ahmad Gani
2025-08-14 7:15 ` Alviro Iskandar Setiawan
2025-08-14 4:46 ` [PATCH gwproxy v5 2/2] dnsparser: Add dns parser code Ahmad Gani
2025-08-14 7:28 ` Alviro Iskandar Setiawan
2025-08-14 7:43 ` Alviro Iskandar Setiawan
2025-08-16 16:03 ` Ammar Faizi
2025-08-16 16:30 ` Ahmad Gani
2025-08-16 16:40 ` Ammar Faizi
2025-08-21 16:50 ` Alviro Iskandar Setiawan
2025-08-22 5:43 ` Ahmad Gani
2025-08-22 13:48 ` Alviro Iskandar Setiawan
2025-08-22 19:09 ` Alviro Iskandar Setiawan
2025-08-22 19:52 ` Ammar Faizi
2025-08-23 1:07 ` Ahmad Gani
2025-08-23 1:52 ` Ammar Faizi
2025-08-23 2:17 ` Ahmad Gani
2025-08-23 2:22 ` Ammar Faizi
2025-08-23 2:20 ` Alviro Iskandar Setiawan
2025-08-23 2:28 ` Ammar Faizi
2025-08-24 13:36 ` Ahmad Gani
2025-08-25 14:37 ` Ammar Faizi
2025-08-28 0:13 ` Ammar Faizi
2025-08-28 1:51 ` Ahmad Gani
2025-08-28 2:29 ` Ahmad Gani
2025-08-28 2:45 ` Ahmad Gani
2025-08-28 2:52 ` Ahmad Gani
2025-08-28 4:19 ` Ammar Faizi
2025-08-28 4:00 ` Ammar Faizi
2025-08-16 16:41 ` Ammar Faizi [this message]
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=175536228502.177146.5466707683679177795@gnuweeb.org \
--to=ammarfaizi2@gnuweeb.org \
--cc=alviro.iskandar@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