Well, I've got the network pretty much set up, in W2K.
There's a diagram at:
http://home.earthlink.net/~entheos_e...ntheos_LAN.gif
I've got everything talking to each other and the internet in W2K;
Installing and RTFMing Linux and Networking has taught me enough
that I believe I could go out and configure networks like the big
boys - I've discovered their dirty little secret - that one setting
that nobody tells you about, that you have to either find out by
inexorable digging, or enroll in their course and be anointed as
a network expert or whatever.
And for $125.00/hr, I'll tell you the secret! ;-)
Anyway, at the moment I've got Entheos-ws1 plugged right into the
hub, so I can type this; Thunderbird plugged into the hub, and
Vehicle plugged into 192.168.0.1 on Thunderbird.
When I plug Entheos-ws1 into Thunderbird, it doesn't get any
kind of network connection, of course.
With Vehicle, when I boot, it says network unreachable. Of course.
I haven't touched anything on the fresh virgin install on Thunderbird
(Slack 9.1), other than vga=ext in lilo.conf and with
/sbin/modprobe sis900
inserted _before_
/sbin/modprobe tulip
..
Thunderbird can ping out, but nobody else is talking. I'm not
going to try to ping 192.168.0.1 from Entheos-ws1, because it's
off the subnet at the moment.
Vehicle didn't get a connection because I haven't done _any_
configuring of Thunderbird yet. I'm going to change Vehicle
from DHCP to 192.168.0.2, boot, and see what happens:
....
OK, still won't ping, but I notice ifconfig on Tbird shows
eth1 not up. So, ...
/sbin/ifconfig eth1 192.168.0.1 broadcast 192.168.0.255 netmask
255.255.255.0
they can ping each other! YAY! :-D
But Vehicle can't ping out. (Tbird can ping, e.g.
www.yahoo.com.).
So, what's next? DHCP? masquerading? forwarding? DNS? hosts?
Waiting, like the cat that ate the cheese, with baited breath,
Rich