Linux/BSDI boot-up diskettes.

Albert_Garrido_at_RUPOST2@ccmail.nextel.com
Fri, 11 Apr 97 08:04:02 EST


Hi.

I'm currently working on adding additional machines to the effort, but I'm a bit
stumped. I'm limited in the number of "real" IP addresses that actually that I
can actually use. The machines I can get access to, are mainly Windows 3.1
machines. Several people mentioned creating boot diskettes for these machines.
Here is my situation. I know that I can use a Windows NT server to hide the IP
addresses, or in theory, that the NT machine would act as the proxy for all the
remaining machines on the network. Is this possible? My other question, the
network here appears to be heavily subnetted, such that only a small range of IP
addresses appear to work, if I just make up a random IP address (well, not too
random, similar to ours, but in a range that my organization isn't using) and
then map those to the NT box, wouldn't the NT server handle all those incoming
and outgoing connections from there? Using DHCP or something, the clients would
poll the NT server, and it would assign fake addresses from there?

I also have access to Slackware (2.0.2) and Red Hat's 4.0 Linux, and I could
attempt to create boot diskettes from this, but I don't know enough about Linux
to know what I'd have to stick on the diskettes to make it work (and fit on one
or two diskettes)

Lastly. I have access to several stand alone machines near me, that aren't
network enabled, but do run Windows 95/NT, however I have a single 10Base-T
connection going to them. My thought, (highly unapproved of as yet), was to buy
a small five or 8 port 10Base-T hub, and assigning them fictitious IP addresses
like my scheme of above. The NT server in the example above isn't on the
network yet, and this is the only manner I can think of to juggle the
arrangements to get it to fit.

Anyone, please tell me if I'm pissing in the dark, thanks!