From: "H. William Welliver" <william@welliver.org>
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] [REVIEW] 16763: dladm simnet functionality should be documented
Date: Thu, 12 Sep 2024 00:20:52 -0400 [thread overview]
Message-ID: <862F4DFB-01AF-4639-BA61-8A87BC5060B6@welliver.org> (raw)
In-Reply-To: <22C789E4-5811-43E0-A48D-B361F75A7CF0@eenfach.de>
Hi!
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.
As a side-note: I didn’t specifically describe simnets as a debugging facility because I think they can be handy for other things, as well. I first (mis)used them by adding one to a bridge created from the physical nics on the device. I then configured the other end as the host’s primary interface. This enabled the host to be accessible without a particular port needing to be physically “up”. Strange and very niche, but pretty handy for making network appliances.
Bill
> On Sep 11, 2024, at 2:48 PM, Olaf Bohlen <olbohlen@eenfach.de> wrote:
>
> Dear William,
>
> maybe the create-simnet subcommand should include a very brief explanation what “simnet” actually is. So that end users understand that it is mostly a debugging facility.
>
> Regards,
>
> Olaf Bohlen
> olbohlen@eenfach.de
next prev parent reply other threads:[~2024-09-12 4:20 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 [this message]
2024-09-12 8:33 ` Olaf Bohlen
2024-09-12 8:46 ` Joshua M. Clulow
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=862F4DFB-01AF-4639-BA61-8A87BC5060B6@welliver.org \
--to=william@welliver.org \
--cc=developer@lists.illumos.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).