On Sat, 1 Jul 2000, Jack Byers wrote:
> For an internal MASQed computer, with a single nic
> is it ok to configure that nic as eth1 instead of eth0?
>
> I ask because my main Masqserver linux box uses eth0 for
> its connection via dsl to outside,
> and hence eth1 for the internal net.
>
> So it seems to me, simply for symmetry if nothing else,
> best to keep this internal lan named eth1 on all computers
> on the internal lan.
>
> {Of course i could reconfigure my mainlinuxbox to use
> eth1 as the dsl-to-outside and eth0 as inside,
> but I don't want to.)
>
> This isnt a big deal, can configure the internal box(soon to arrive)
> as eth0 if necessary,
> but I would like to know best practices....
>
> I cant seem to find anything about this in the howtos.
>
> regards,
> Jack
>
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.
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
--
Do not meddle in the affairs of dragons,
for you are crunchy and taste good with ketchup.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
