assignment of eth* devices

[Jeff Vian]

On Mon, 2005-02-07 at 11:25 -0800, Rick Stevens wrote:
> David Hoffman wrote:
> > On Mon, 7 Feb 2005 14:06:28 -0500 (EST), William Hooper
> > <whooperhsd3 at earthlink.net> wrote:
> > 
> >>David Hoffman said:
> >>
> >>>On Mon, 7 Feb 2005 12:21:46 -0500, Sameer Kamat <sameer at unitrends.com>
> >>>wrote:
> >>>
> >>>
> >>>>Hi,
> >>>>Would anyone know how to force the system to assign a specific
> >>>>network card a specific eth device. Is there a file/ setting that can be
> >>>>adjusted to force this operation.?
> >>>>
> >>>
> >>>I had this problem with my system. I wanted to use my 100-base-T
> >>>connection for the link to the router, but wanted my Gigabit connection for
> >>>the LAN side. But when I did the install, they were reversed.
> >>
> >>I really think for that example that swapping the cables would be the
> >>easiest solution.
> >>
> > 
> > 
> > I hope that was meant to be humerous.
> > 
> > Swapping cables is one thing, but what about having to go into any of
> > a dozen places in your system and swapping eth0 with eth1?
> > Some of us have developed pretty elaborate firewall rules, not to
> > mention many other configurations that point to particular interfaces.
> > Maybe if this was a brand new installation that might work, but not in
> > all cases.
> 
> Have you tried using the "HWADDR=" bit in the ifcfg-ethx scripts?

That would have no effect on what the interface is named at module load
time.

> ----------------------------------------------------------------------
> - Rick Stevens, Senior Systems Engineer     rstevens at vitalstream.com -
> - VitalStream, Inc.                       http://www.vitalstream.com -
> -                                                                    -
> -   To err is human.  To forgive, a large sum of money is needed.    -
> ----------------------------------------------------------------------
>