Re:Scheme 9 interpreter ported to Plan 9 (again)
by JoshTriplett on Saturday July 04, 2015 @09:31AM
(#9830085)
Here are a few examples.
On Plan 9, network sockets are available via the /net filesystem (for instance, /net/tcp and /net/udp). If you use the standard remote filesystem mechanism (9P) to mount a remote system's /net filesystem, you can access files there to create sockets from that system, rather than your local system: VPN with just the filesystem.
If you want to forward a few specific ports from that system to yours, mount the relevant bits of your /net over the remote system's /net: port forwarding with just the filesystem.
If you want to prevent an application from accessing the network, or firewall it from accessing certain ports, you can limit its access to /net or a subset of files in /net: firewalls with just the filesystem.
On Plan 9, network sockets are available via the /net filesystem (for instance, /net/tcp and /net/udp). If you use the standard remote filesystem mechanism (9P) to mount a remote system's /net filesystem, you can access files there to create sockets from that system, rather than your local system: VPN with just the filesystem.
If you want to forward a few specific ports from that system to yours, mount the relevant bits of your /net over the remote system's /net: port forwarding with just the filesystem.
If you want to prevent an application from accessing the network, or firewall it from accessing certain ports, you can limit its access to /net or a subset of files in /net: firewalls with just the filesystem.