From: Stefano Brivio <sbrivio@redhat.com>
To: DUO Labs <dvdugo333@gmail.com>
Cc: passt-dev@passt.top
Subject: Re: Porting to macOS
Date: Thu, 12 Sep 2024 09:00:04 +0200 [thread overview]
Message-ID: <20240912090004.7166ff01@elisabeth> (raw)
In-Reply-To: <CADYS5mCYj0pc3iCOU5Z=VUkm-KXiB9hbwqm_KkqxT-FLRd1gtg@mail.gmail.com>
On Wed, 11 Sep 2024 22:19:15 -0400
DUO Labs <dvdugo333@gmail.com> wrote:
> Looking at the archives, it looks like my message was never received (I'm
> still figuring this mailing list stuff out). I'm pasting my message below:
Non-subscribers' posts are held to avoid spam, I have to approve them
manually. You can register to the list to avoid delays:
https://lists.passt.top/postorius/lists/passt-dev.passt.top/
> Is AF_NETLINK required for passt usage, or is it only for pasta?
It's more heavily needed for pasta because, there, we use it to
directly configure the networking in the container (with --config-net),
whereas with passt the configuration happens via DHCP/NDP/DHCPv6.
With passt, we use netlink just to source addresses and routes from the
host. I see two alternatives for Darwin:
- use sysctls with NET_RT_DUMP / NET_RT_IFLIST2 / NET_RT_DUMP2 to fetch
the same information. It's not clear to me if it needs root, though,
or if there's a different way to fetch information without root
- force the user to give a manual configuration (with options -a, -g at
least)
--
Stefano
prev parent reply other threads:[~2024-09-12 7:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 20:15 Porting to macOS DUO Labs
2024-09-10 21:26 ` Stefano Brivio
[not found] ` <f872b2a5-107f-4ee5-92f8-0832f1e771ea@gmail.com>
[not found] ` <20240910234105.5ef93691@elisabeth>
2024-09-11 1:33 ` DUO Labs
2024-09-11 1:46 ` DUO Labs
2024-09-11 23:01 ` DUO Labs
[not found] ` <CADYS5mCYj0pc3iCOU5Z=VUkm-KXiB9hbwqm_KkqxT-FLRd1gtg@mail.gmail.com>
2024-09-12 7:00 ` 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=20240912090004.7166ff01@elisabeth \
--to=sbrivio@redhat.com \
--cc=dvdugo333@gmail.com \
--cc=passt-dev@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.
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).