From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Ahmad Gani <reyuki@gnuweeb.org>
Cc: Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>
Subject: Re: [PATCH gwproxy v5 2/2] dnsparser: Add dns parser code
Date: Sat, 16 Aug 2025 23:40:56 +0700 [thread overview]
Message-ID: <20250816164056.GB144043-ammarfaizi2@gnuweeb.org> (raw)
In-Reply-To: <CAADvAgpegzsanTUzrR91Kt0nmq97+1_gmD-rWtUBLO0p_Q3bXA@mail.gmail.com>
On Sat, Aug 16, 2025 at 11:30:09PM +0700, Ahmad Gani wrote:
> On Sat, Aug 16, 2025 at 11:03 PM Ammar Faizi wrote:
> > Now the question is: How do we integrate this?
> >
> > I see no Makefile changes. I guess it's still not covered by gwproxy
> > build system.
>
> I’ve managed to integrate it into gwproxy’s epoll event loop
> and successfully run a simple single-query test with cURL.
>
> However, the integration process isn't fully completed and still requires
> significant changes across `dns.c`, `gwproxy.c`, and `epoll.c`.
>
> So, It’s still a WIP.
>
> Here’s the gist of how I integrated the parser:
> - A non-blocking UDP socket file descriptor is created each time
> `gwp_dns_queue` is called.
> - A standard DNS query packet is sent over the network through that socket.
> - The UDP socket file descriptor is registered with epoll.
> - On epoll notification, the response is received.
> - The response is parsed and returned as a reply to the SOCKS5
> `CONNECT` command.
Nice, sounds good. Looking forward to the updates!
For now, I take the manpage change only from this series.
--
Ammar Faizi
next prev parent reply other threads:[~2025-08-16 16:40 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 [this message]
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 ` (subset) [PATCH gwproxy v5 0/2] Initial work on integration of DNS parser lib in gwproxy Ammar Faizi
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=20250816164056.GB144043-ammarfaizi2@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