public inbox for gwml@vger.gnuweeb.org
 help / color / mirror / Atom feed
From: Ahmad Gani <reyuki@gnuweeb.org>
To: Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
	"GNU/Weeb Mailing List" <gwml@vger.gnuweeb.org>
Subject: Re: [PATCH gwproxy v5 2/2] dnsparser: Add dns parser code
Date: Fri, 22 Aug 2025 12:43:22 +0700	[thread overview]
Message-ID: <CAADvAgpD=ywC7ZUwNOoUz_ZRS0c2=0R3H4PTnix3A8u5bstTZw@mail.gmail.com> (raw)
In-Reply-To: <CAOG64qO6j82YncitigR-wV8uJMf0_s2x83d+9h1YGWRLT4EJuQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]

On Thu, Aug 21, 2025 at 11:50 PM Alviro Iskandar Setiawan wrote:
> Do you have a git tree for the public to fetch your WIP?

I just pushed a new branch at my github fork of gwproxy [1], you can take
a look if you want in the branch refactor-dns-feature.

The work-in-progress contain several TODOs:
- fix the parser (watch only for A record, ignore others like CNAME)
- handle both IPv6 and IPv4 when preferred family is AF_UNSPEC (see
dns.c:480 and dns.c:426)
- insert cache and house-keeping cache
- special domain name handling (e.g., allow localhost but refuse
.onion) and /etc/hosts
- integration with io_uring
- polishing the overall changes

> I've just been back to my home. I'd like to take a look into it. I may
> also continue the work if you don't have time. I am free for the rest
> of the week, so I'll use it to tackle this one.

Actually, I do have plenty of time. But I tend to lose focus when things
don't go well, and then it's hard for me to get back into it.

Maybe it'll be a different story if I talk things out and discuss it with
other
gwproxy contributors, but argh, it's hard to explain—or to change my habits.

Maybe, if you don't mind, it'd be nice to do it in more of a Q&A style
instead
of you continuing the work all by yourself. That way, I might actually start
changing my own habits, but only if you're comfortable with that suggestion.

[1]:
- https://github.com/realyukii/gwproxy/tree/refactor-dns-feature

--
Ahmad Gani

[-- Attachment #2: Type: text/html, Size: 1893 bytes --]

  reply	other threads:[~2025-08-22  5:43 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 [this message]
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='CAADvAgpD=ywC7ZUwNOoUz_ZRS0c2=0R3H4PTnix3A8u5bstTZw@mail.gmail.com' \
    --to=reyuki@gnuweeb.org \
    --cc=alviro.iskandar@gnuweeb.org \
    --cc=ammarfaizi2@gnuweeb.org \
    --cc=gwml@vger.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