> Now, suppose IC goes to listen on TCP:80, by opening /net.alt/tcp/clone.
> The same flow of events happen, and to a certain extent, G's network stack
> thinks that the exportfs program (running on G) is listening on TCP:80.
> exportfs dutifully copies the /net data back to its client.
great post.
small point:
it turns out that running httpd, or any proc that becomes none,
doesn't work because the importee won't let none run exportfs.
also, i wanted to point out another scheme for dealing with the
external interface. what i typically do is keep the external network
on /net.alt and the internal network on /net on all machines.
for example
term; ipifc
0:/net/ether0 001b21028754 1514
192.168.0.57/120 192.168.0.0
term; cpu -c ipifc
0:/net/ether0 001b2102873b 1514
192.168.0.136/120 192.168.0.0
0:/net.alt/ether1 001d92350045 1514
192.168.10.1/120 192.168.10.0
so if i "import $cpu /net.alt /net.alt" from the terminal,
the networking appears the same on the terminal and cpu server.
- erik
