Shorewall users - May 2003 - multiple nic''s of the same card type

I humbly acknowledge that this is a bit off-topic but it is certainly 
something many folks involved in the finer points of networking must have 
come up against.

To keep it brief, I have 3 nic''s in my fw computer and two of these are
the
same model using the 8139 chip.  The question is simple:  When there are 
two or more of the same model of network card, how can I control which card 
gets assigned to which interface (eth0, eth1)?  In my case, when I run 
''modprobe 8139too'' are there some options I''m
missing?

I can assure you I''ve looked all over the place but all I seem to come
with
are horror stories from folks who have been unsuccessful and ended up 
replacing the duplicate card with another make.  I''m hopeful that I
just
haven''t been looking in the right places for the missing information.

Thank you for your patience and for any pointers you can pass along.

Bill


-- 
Using M2, Opera''s revolutionary e-mail client: http://www.opera.com/m2/

I''ve never found a way to control this. OTOH, I''ve never had
them move
either.  Once a card is eth0 it''s always eth0. (Unless I change cards
or
something)

Therefore, I''ve always simply figured it out when building the box and
not
worried about it.

=C* Cal Evans
* http://www.christianperformer.com
* Stay plugged into your audience
* The measure of a programmer is not the number of lines of code he writes
but the number of lines he does not have to write.
*

----- Original Message -----
From: "William Trenker" <wdtrenker@yahoo.ca>
To: <shorewall-users@lists.shorewall.net>
Sent: Monday, May 12, 2003 1:32 PM
Subject: [Shorewall-users] multiple nic''s of the same card type

> I humbly acknowledge that this is a bit off-topic but it is certainly
> something many folks involved in the finer points of networking must have
> come up against.
>
> To keep it brief, I have 3 nic''s in my fw computer and two of
these are
the
> same model using the 8139 chip.  The question is simple:  When there are
> two or more of the same model of network card, how can I control which
card
> gets assigned to which interface (eth0, eth1)?  In my case, when I run
> ''modprobe 8139too'' are there some options I''m
missing?
>
> I can assure you I''ve looked all over the place but all I seem to
come
with
> are horror stories from folks who have been unsuccessful and ended up
> replacing the duplicate card with another make.  I''m hopeful that
I just
> haven''t been looking in the right places for the missing
information.
>
> Thank you for your patience and for any pointers you can pass along.
>
> Bill
>
>
> --
> Using M2, Opera''s revolutionary e-mail client:
http://www.opera.com/m2/
> _______________________________________________
> Shorewall-users mailing list
> Post: Shorewall-users@lists.shorewall.net
> Subscribe/Unsubscribe:
http://lists.shorewall.net/mailman/listinfo/shorewall-users
> Support: http://www.shorewall.net/support.htm
> FAQ: http://www.shorewall.net/FAQ.htm
>

On Mon, 12 May 2003 20:32:36 -0500, Cal Evans <cal@calevans.com> wrote:
> I''ve always simply figured it out when building the box and not
worried
> about it.
That''s a very pragmatic solution and it gets the job done -- I expect
I''ll
just have to live with it.  But it surprises me that there isn''t a way
to
have more refined control over the process of assigning network interfaces.

Thanks for the info.

Bill


-- 
Using M2, Opera''s revolutionary e-mail client: http://www.opera.com/m2/

On Monday 12 May 2003 20:32, Cal Evans wrote:
> I''ve never found a way to control this. OTOH, I''ve never
had them move
> either.  Once a card is eth0 it''s always eth0. (Unless I change
cards or
> something)
Dont you believe it William!  It just bit me big time!  I have used the same 
two nics in the same place for at least two years.  the other day when I 
installed SuSE8.2 everything came up as usual but I couldnt get the network 
to work. I didnt notice that the order of the two nics had changed.    Why I 
dont know, but it did and I spent all night reinstalling 8.1 and then 8.2 
only to discover when I went to remove one of the nics that the order had 
changed, eth0 showed up as eth1 and vice versa and it is still that way!!  

My point is that you should never assume things are the same as when you 
started something least of all the order of the NICs. A similar thing 
happened to my brother on an entirely different system!  When things stop 
working, always go back and check the obvious.  It could save you a lot of 
time and heartache.

I sure would like it if someone could tell me what happened.

Be cautious and never say never!
Richard

Sorry, I wasn''t clear.  I''ve had a box running with 2 Tulip
cards in it for
about 5 years now.  Every time I load a new distro on it I have to figure
out which is which. I''ve NEVER had them switch once the OS is loaded.
(and I
update early and often!)

If it happened right after you loaded a new distro then that may be the
problem.

=C* Cal Evans
* http://www.christianperformer.com
* Stay plugged into your audience
* The measure of a programmer is not the number of lines of code he writes
but the number of lines he does not have to write.
*

----- Original Message -----
From: "Richard" <ratcheson@earthlink.net>
To: <shorewall-users@lists.shorewall.net>
Sent: Monday, May 12, 2003 9:45 PM
Subject: Re: [Shorewall-users] multiple nic''s of the same card type

> Dont you believe it William!  It just bit me big time!  I have used the
same
> two nics in the same place for at least two years.  the other day when I
> installed SuSE8.2 everything came up as usual but I couldnt get the
network
> to work. I didnt notice that the order of the two nics had changed.    Why
I
> dont know, but it did and I spent all night reinstalling 8.1 and then 8.2
> only to discover when I went to remove one of the nics that the order had
> changed, eth0 showed up as eth1 and vice versa and it is still that way!!

On Monday 12 May 2003 06:59 pm, Cal Evans wrote:
> Sorry, I wasn''t clear.  I''ve had a box running with 2
Tulip cards in it for
> about 5 years now.  Every time I load a new distro on it I have to figure
> out which is which. I''ve NEVER had them switch once the OS is
loaded. (and
> I update early and often!)
>
> If it happened right after you loaded a new distro then that may be the
> problem.
The hardware enumerates the nics based on which slot they are in.
But the software decides wether to scan from top down or bottom
up.  I''ve never known one distro of linux to do it different than
another
since they are running mostly the same code.

-- 
John Andersen - NORCOM
http://www.norcomsoftware.com/

This was a real drag on Red Hat 6x and some 7x. I switched all my
systems to Gentoo and life is good as you can count on things like the
onboard being eth0 and pci slot 1 being eth1, slot 2 eth2 etc.

Anyway, not to toot horns here. The solution I found on redhat was to
pass the interrupt somewhere in redhat''s config files. Sorry, I
don''t
remember.

One could assume though that the OS either counts backwards or
forwards...hmm...

http://www.scyld.com/network/tulip.html



On Mon, 12 May 2003 18:57:02 -0000
William Trenker <wdtrenker@yahoo.ca> opened up to us and said:
> On Mon, 12 May 2003 20:32:36 -0500, Cal Evans <cal@calevans.com>
> wrote:
> 
> > I''ve always simply figured it out when building the box and
not
> > worried about it.
> 
> That''s a very pragmatic solution and it gets the job done -- I
expect
> I''ll just have to live with it.  But it surprises me that there
isn''t
> a way to have more refined control over the process of assigning
> network interfaces.
> 
> Thanks for the info.
> 
> Bill
> 
> 
> -- 
> Using M2, Opera''s revolutionary e-mail client:
> http://www.opera.com/m2/
> _______________________________________________
> Shorewall-users mailing list
> Post: Shorewall-users@lists.shorewall.net
> Subscribe/Unsubscribe:
> http://lists.shorewall.net/mailman/listinfo/shorewall-users
> Support: http://www.shorewall.net/support.htm
> FAQ: http://www.shorewall.net/FAQ.htm

-- 
Paul Slinski
System Administrator
Global IQX
http://www.globaliqx.com/
pauls@globaliqx.com

[ The information transmitted is intended only for the addressee   ]
[ and may contain confidential, proprietary and/or privileged      ]
[ material.  Any unauthorized review, distribution or other use    ]
[ of or the taking of any action in reliance upon this information ]
[ is prohibited. If you received this in error, please contact the ]
[ sender and delete or destroy this message and any copies.        ]

# sorry Paul, missed the right ''reply'' button by 10 pixels...

> Anyway, not to toot horns here. The solution I found on redhat was to
> pass the interrupt somewhere in redhat''s config files. Sorry, I
don''t
> remember.
You can assign this IIRC in /etc/modules.conf. Add the Interface (ethX),
the driver, and assign some hardware info to distinguish the cards like
hardware address or interrupt.

That should work, but please do not ask me for details... ;-)

  karsten


-- 
Hi, I''m a signature virus. Copy me into your ~/.signature to help me
spread!

On Wed, 2003-05-14 at 05:24, kb wrote:
> # sorry Paul, missed the right ''reply'' button by 10
pixels...
> 
> 
> > Anyway, not to toot horns here. The solution I found on redhat was to
> > pass the interrupt somewhere in redhat''s config files. Sorry,
I don''t
> > remember.
> 
> You can assign this IIRC in /etc/modules.conf. Add the Interface (ethX),
> the driver, and assign some hardware info to distinguish the cards like
> hardware address or interrupt.
You can actually rename interfaces to whatever you want based on mac
address using the "nameif" utility included in Debian''s
net-tools
package. You can do this by putting the name to mac mapping into
/etc/mactab like the following;

loc    00:40:05:E1:61:18
net    01:46:15:E1:66:FE

Then add things like the following to /etc/modutils/actions and run
update-modules;

post-install ne2k-pci nameif
post-install tulip nameif

This ensures nameif is called after modules are installed to rename the
interfaces based on mac address. You _must_ then refer to the interfaces
by these names everywhere. See "man nameif" for more details.


-- 
----------------------------------------------------------------
Donovan Baarda                http://minkirri.apana.org.au/~abo/
----------------------------------------------------------------