public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top, Paul Holzinger <pholzing@redhat.com>
Subject: Re: [PATCH v2 0/2] Broaden DNS forwarding
Date: Thu, 25 Jul 2024 13:27:31 +0200	[thread overview]
Message-ID: <20240725132731.213176c7@elisabeth> (raw)
In-Reply-To: <20240724075112.1279868-1-david@gibson.dropbear.id.au>

On Wed, 24 Jul 2024 17:51:10 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:

> When looking through outstanding bugs in various trackers, I noticed
> this one:
> 	https://github.com/containers/podman/issues/23239
> 
> Now that the flow table is merged, this is very easy to fix, so,
> here's a fix.  While we're at it, handle encrypted DNS on port 853 as
> well, which Red Hat certainly seems to be interested in for one.
> 
> Changes since v1:
>  * Fix some stylistic errors in 1/2
>  * Update man page to reflect new behaviour in 2/2
> 
> David Gibson (2):
>   fwd: Refactor tests in fwd_nat_from_tap() for clarity
>   fwd: Broaden what we consider for DNS specific forwarding rules

Applied.

-- 
Stefano


      parent reply	other threads:[~2024-07-25 11:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-24  7:51 [PATCH v2 0/2] Broaden DNS forwarding David Gibson
2024-07-24  7:51 ` [PATCH v2 1/2] fwd: Refactor tests in fwd_nat_from_tap() for clarity David Gibson
2024-07-24  7:51 ` [PATCH v2 2/2] fwd: Broaden what we consider for DNS specific forwarding rules David Gibson
2024-07-24  9:41   ` Paul Holzinger
2024-07-24 14:30     ` Stefano Brivio
2024-07-25  4:44       ` David Gibson
2024-07-25  8:39         ` Paul Holzinger
2024-07-25 11:27 ` Stefano Brivio [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=20240725132731.213176c7@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    --cc=pholzing@redhat.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).