Netdev List
 help / color / mirror / Atom feed
From: Cong Wang <cwang@multikernel.io>
To: Jon Maser <jonmaser8@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Proposal: module for optional /net directory for network data
Date: Thu, 16 Jul 2026 19:52:36 -0700	[thread overview]
Message-ID: <almY9NvR4nJtpW_o@pop-os.localdomain> (raw)
In-Reply-To: <CAF=mWJMErgOuTML7hFy6gEH5zqACOdZU62Xh=bR55=VbB4fJ2g@mail.gmail.com>

On Tue, Jun 16, 2026 at 06:13:51PM -0700, Jon Maser wrote:
> A little under the weather but hopefully this comes across well lol
> 
> This may not be for the sensitive. and yeah I do have a mental
> disorder as well, and I'm not an expert

Any idea is welcome!

> 
> But it would be nice for network operations to be aided by a /net
> directory, where devices can have full access to network data,
> including hardcore bit by bit access, complete control of data coming
> in,and out, shell access to network data, you can easily cache network
> operations for forensics, you can enhance firewall technology, even
> with hardware firewalls by giving vendors time to adapt to a high
> level access of network data
> 
> It needs to be a module to be a true unix imho
> 
> It can be as easy as cat sendack.ns > /net/0/in && cat /dev/eth0
> 
> Its also easy to write a firewall in shell script

Linux networking subsystem is ruled by netlink, devices are less
preferred interfaces, because netlink is binary-rich and flexible.

Of course, you can always write out-of-tree modules without
arguing with the upstream community. :)

Regards,
Cong

      reply	other threads:[~2026-07-17  2:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-17  1:13 Proposal: module for optional /net directory for network data Jon Maser
2026-07-17  2:52 ` Cong Wang [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=almY9NvR4nJtpW_o@pop-os.localdomain \
    --to=cwang@multikernel.io \
    --cc=jonmaser8@gmail.com \
    --cc=netdev@vger.kernel.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