Re: Two NICs on one modprobe? (slack 9.1)

Rich Grise wrote:
>
> I spent some time trying to get it to configure the internal
> as eth0, which goes to the ISP, and the NIC as eth1, the
> internal subnet. But it kept seeing the Rhine III first, no
> matter which order I put the /sbin/modprobe <whichever> in
> /etc/rc.d/rc.netdevice. So, I'm trying to get the damn thing
> configured, tying to figure out what's going on, got echo
> and read statements about every third line in my scripts,
> and lo and behold, during one trial run, I execute only
> the line /sbin/modprobe via-rhine, and it reports a Rhine
> III as eth0 _AND_ a Rhine II as eth1. "WTF??!?!??!!??" I sez
> to meself. So I plug the modem into the NIC ($5.99 at Fry's -
> I bought four.) and the switch into the internal, and it's
> just chugging away like it's the most natural thing in
> the world.
>
> Rebooted a couple of times, with just the one
> /sbin/modprobe via-rhine in /etc/rc.d/rc.netdevice, and
> it still loads up both adapters, still backwards, and still
> running like it was set up by somebody who knew what the
> heck they were doing! (i.e., not only is it working, but
> it's repeatable, which really really shouldn't surprise
> me - I haven't repeated a lot of error conditions because
> I usually don't have the patience to redo whatever I just
> did to spot that there _was_ an error - I just jump in and
> hack, which almost invariably makes the malfunction act
> differently, so the only lack of repeatability I can
> cop to with Linux is my version of what a setup config
> looks like. ;-P )
>
Sorry I am sort of late responding to this post. Look at "nameif" (man
nameif), it will let you name nics by their MAC addresses. I do believe
that nameif needs to be called from ifconfig.

--
jamess
Slackware Linux... The choice of professionals.