thanks Mikkel, now I know it was a nutty idea.
Mikkel L. Ellertson responded
>You might have an interesting time configuring the single NIC as
>eth1. The install program will make it eth0, so you will have to go in
>and edit things afterwords to make it eth1. Besides, the configurations
>will not be the same on the computers on the inside LAN and the
>firewall. The inside conputers will have to have the firewall as their
>gateway, but the firewall will have a different gateway.
I realized this, but just thot having the same name eth1 on both
sides for the internal network was something to strive for.
>Also, it you recompile the kernel with the driver for your NIC compiled
>in, it will be hard to make it eth1. You will have to add paramerors when
>booting to tell the kernel that your card is eth1! Interfaces are numbered
>with the first one being eth0, the second one eth1, and so on. I think you
>can override this when using modules by aliasing eth1 to the module for
>your
>NIC. But you will run into the same problems when you upgrade your
>software, so it probably isn't worth the effort.
>
>Mikkel
I won't even try.
Jack
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
