Proposal: module for optional /net directory for network data

Proposal: module for optional /net directory for network data

[Jon Maser]

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

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


Hopefully that impresses the Linux community!! lol

Jon

Also if it gets down to interception, wiretapping, and other felonies
I dont mind being told no, Its the linux communities job to crack down
on illegal stuff, just like the nerds before us

Re: Proposal: module for optional /net directory for network data

[Cong Wang]

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