From: "Joshua M. Clulow" <josh@sysmgr.org>
To: illumos-developer <developer@lists.illumos.org>
Cc: "H. William Welliver" <william@welliver.org>
Subject: Re: [developer] [REVIEW] 16763: dladm simnet functionality should be documented
Date: Thu, 12 Sep 2024 01:46:34 -0700 [thread overview]
Message-ID: <CAEwA5nJBQB_GBJG-MwZR5ML3S3UmTVsy=7qyBm3+vhtKM1kFww@mail.gmail.com> (raw)
In-Reply-To: <wu3ikv12rvn.fsf@eenfach.de>
On Thu, 12 Sept 2024 at 01:33, Olaf Bohlen <olbohlen@eenfach.de> wrote:
> "H. William Welliver" <william@welliver.org> writes:
> > I did add a brief description of what simnets are in the “Description”
> > section, as that is where other types of objects (vnics, etherstubs,
> > etc) are introduced. I’ll also willingly admit that I don’t normally
> > read that section and jump right to the command details but I was
> > trying to remain consistent with the existing document.
>
> Yes, I meant something like "the dladm create-simnet creates an
> instance of a simulated network device mostly used for debugging
> purposes" or similar...so an indirect formulation - because a lot
> of people just skip the descriptions ;)
I think "debugging purposes" is a bit too editorial, to be honest.
You can use them for really any purpose, including tinkering and
simulating different network topologies between zones or VMs. At
Oxide, we have a framework called Falcon for driving networking and
virtualisation test topologies that makes pretty heavy use of simnets
for certain things:
https://github.com/oxidecomputer/falcon
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
next prev parent reply other threads:[~2024-09-12 8:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 5:24 william
2024-09-11 18:48 ` [developer] " Olaf Bohlen
2024-09-12 4:20 ` H. William Welliver
2024-09-12 8:33 ` Olaf Bohlen
2024-09-12 8:46 ` Joshua M. Clulow [this message]
2024-09-27 21:21 william
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='CAEwA5nJBQB_GBJG-MwZR5ML3S3UmTVsy=7qyBm3+vhtKM1kFww@mail.gmail.com' \
--to=josh@sysmgr.org \
--cc=developer@lists.illumos.org \
--cc=william@welliver.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;
as well as URLs for NNTP newsgroup(s).