Ethernet interface solved

[Rick Stevens]

Kenneth Tindle wrote:
> Oh joy!  It works!!!
> 
> Bob McClure Jr <robertmcclure at earthlink.net> said:
> 
>  >I don't know how it's used (Rick Stevens or Jeff Kinz may be able to
>  >explain), but look in /etc/sysconfig/networking/profiles/default/.
>  >There's an ifcfg-eth0 you may need to change.
> 
> Yep.  How's about blowing it away?  Then the blasted static IP
> (which lived there) *finally* exited stage left.  I think this
> might be some detritus left by redhat-config-network...
> 
> Thanks be to Bob.  Oh, and-
> 
> Rick Stevens <rstevens at vitalstream.com> said:
> 
>  >You may wish to delete the "GATEWAY=" in /etc/sysconfig/network if the
>  >DHCP server gives you a gateway to use.
> 
> Indeed. It was a problem.  Had to config this, then forgot to throw it
> away.
> 
>  >Optional things that should work:
>  >       HWADDR=xx:xx:xx:xx:xx:xx  (MAC address of the card)
>  >       TYPE=wireless  or  TYPE=ethernet
> 
> Not sure how optional these params really are, when you have three
> interfaces!  I used both TYPE and HWADDR (which seems to use nameif)
> and many ruffled feathers were soothed.  Thanks to Rick for the syntax
> and the pointer.

They're still optional.  Yes, HWADDR is useful, but if you don't have
it you just have to figure out which card is which (hint:  their names
are based on the PCI probe sequence--so take a good look at dmesg).

>  >Basically, what I'm saying is that the device is probably now "wlan0"
> 
> Well, no, not this time.  But you can't read minds, Rick, so chill!

Okey doke.  Back in the 2.2 and early 2.4 kernel days, wireless devices
were still "ethX", but starting about kernel 2.4.15 or so, "wlanX" was
adopted.  Still, many drivers still use "ethX" (despite the kernel
authors' admonitions to the contrary).  Many people who were hardwired
and are now going wireless do forget the "wlanX" name, which is why I
brought it up.

> FYI, I have a Cisco Aironet PCI-352 in this box, which DOES use eth0.
> The drivers "airo" and "airo_cs" depend upon the "acu" utility that
> gets dumped into /opt/cisco/bin, which lets you config all the
> wonderful wireless params that are normally handled with wireless
> kernel extensions and iwconfig in the user land.  Note that this is
> prettier, but requires X.  AND you must get (*exactly*) libgtkmm
> 1.2.10 AND libsigc 1.0.4!

Ewwww!  X and version dependency!  Not good for headless machines!

>                             Anyhow, this is what you must do to
> make the "genuine" Cisco 2.1 driver and utility set work.

Hmmm.  Well, I suppose they have their reasons for that.  It'd be nice
to have that fixed.

> Praise be, to problems solved, and let me not forget- Bob and Rick,
> who know their stuff.

I can't speak for Bob, but as for me, "Eventually, even a blind pig
finds the occasional truffle."

[snort!]  SoooEEEEEEEE!  Here Rick, Rick, Rick!  Slop time!
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     rstevens at vitalstream.com -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-        Change is inevitable, except from a vending machine.        -
----------------------------------------------------------------------