From: David Gibson <david@gibson.dropbear.id.au>
To: "Castelli, Anton" <anton.castelli@siu.edu>
Cc: "passt-user@passt.top" <passt-user@passt.top>
Subject: Re: Rootless Podman with VRRP
Date: Wed, 18 Sep 2024 12:14:10 +1000 [thread overview]
Message-ID: <Zuo3cuE8WRlOzhBP@zatzit.fritz.box> (raw)
In-Reply-To: <ZuolxLJtJuUg8R6K@zatzit.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 2167 bytes --]
On Wed, Sep 18, 2024 at 10:58:44AM +1000, David Gibson wrote:
> On Tue, Sep 17, 2024 at 03:22:04PM +0000, Castelli, Anton wrote:
> > David,
> >
> > Thank you very much for the quick reply!
> >
> > I tried querying the DNS with TCP and it worked correctly, using the
> > VRRP address in the reply packet. Unfortunately, UDP is the default
> > for DNS queries.
>
> Right.
>
> > Thanks for the advice about the options and the workaround. I had
> > just copied them from the Podman docs and modified them slightly. I
> > tried the '--publish 10.1.1.1:53:53/udp --publish
> > 10.1.1.2:53:53/udp' options, and it worked great on the primary
> > server that had the active VRRP address. I was able to query both
> > the regular and VRRP addresses and get a response. Unfortunately,
> > when I tried the same on the secondary server that doesn't have the
> > VRRP address, it refused to bind to the non-existent '10.1.1.2'
> > address.
>
> Ah, right, of course. I was just thinking about the primary, and
> didn't consider how the secondaries would also need to listen on that
> address at some future time.
>
> > I tried with both the publish options and got an error (10.1.1.3 is
> > the regular IP of the secondary server).
> >
> > --publish 10.1.1.3:53:53/udp --publish 10.1.1.2:53:53/udp
> >
> > Error: unable to start container "XXXX": pasta failed with exit code 1:
> > Altering mapping of already mapped port number: 10.1.1.2/53-53:53-53
>
> This looks like a different bug - although one that I think will be
> fixed by some work that's pretty close to the top of my queue. It's
> not all that relevant for your case right now, because..
I just had a closer look at the code which produces this error. The
error is not really correct here - it is a bug. However, it's issued
as only a warning and I think this shouldn't actually break anything
for your situation (assuming we can work around the other issues).
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-09-18 3:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <172649928722.151934.9874324737582181440@maja>
2024-09-17 1:08 ` Rootless Podman with VRRP David Gibson
[not found] ` <172658946856.151934.7414720839553284015@maja>
2024-09-17 16:14 ` Stefano Brivio
[not found] ` <SA1PR07MB8738A2C2355C0CA3E1C0822092612@SA1PR07MB8738.namprd07.prod.outlook.com>
[not found] ` <SA1PR07MB8738CADA17DFA7FDA3D9BD4C92612@SA1PR07MB8738.namprd07.prod.outlook.com>
2024-09-17 20:11 ` Stefano Brivio
[not found] ` <SA1PR07MB87384D729F3FC0543F54BF4392612@SA1PR07MB8738.namprd07.prod.outlook.com>
2024-09-18 0:58 ` David Gibson
2024-09-18 2:14 ` David Gibson [this message]
[not found] ` <SA1PR07MB87382333E58D662293E51E0B92622@SA1PR07MB8738.namprd07.prod.outlook.com>
2024-09-19 2:15 ` David Gibson
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=Zuo3cuE8WRlOzhBP@zatzit.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=anton.castelli@siu.edu \
--cc=passt-user@passt.top \
/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;
as well as URLs for IMAP folder(s).