From: Stefano Brivio <sbrivio@redhat.com>
To: DUO Labs <dvdugo333@gmail.com>
Cc: passt-dev@passt.top
Subject: Re: Porting to macOS
Date: Tue, 10 Sep 2024 23:26:52 +0200 [thread overview]
Message-ID: <20240910232652.29fddf4c@elisabeth> (raw)
In-Reply-To: <bb69ddf4-9f20-49ce-b319-ae79622b918b@gmail.com>
Hi,
On Tue, 10 Sep 2024 16:15:33 -0400
DUO Labs <dvdugo333@gmail.com> wrote:
> I started doing some preliminary work on porting passt to macOS
That's great to hear!
> (I would have responded to issue 6 directly, but I can't seem to make an
> account);
Sorry for that, you should have your request confirmation email now.
I'm reviewing those manually as we have botnets sending automated
account requests for seemingly no benefit, so they might be a bit
delayed from time to time.
> however, I wanted to know how exactly the system works ---
> does it _require_ a tap device, or can I safely remove that file from
> the compilation target (I know that pasta requires it, though)?
passt itself doesn't need a tap device, but note that tap.c is a bit of
a misnomer: it refers to anything guest/container side (be it a UNIX
domain socket, a pre-opened file, or an actual tuntap network
interface).
I guess a reasonable way forward would be to conditionally disable
pasta-related functions, in tap.c and elsewhere, for non-Linux targets
(perhaps easier: conditionally enable them for Linux?).
That is, you won't need tap_handler_pasta() and friends, but you'll need
tap_handler_passt().
--
Stefano
next prev parent reply other threads:[~2024-09-10 21:26 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 [this message]
[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
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=20240910232652.29fddf4c@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).