[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Installing a NIC





 ---- you wrote: 
> > Unfortunately, I got slap happy and tried ping -f (don't do this) just to see
> >what it would do.  I had to cold boot both my boxes to recover.  It's the
> first >time I've actually seen my Linux box lock right up.  Even Alt-F2
> wouldn't work.
> 
> This should not have happened,  I think you have some type of hardware
> conflict.

Maybe it's that full/half duplex thing John mentioned.  I'll look into it and report back.

> 
> > So, as of today, I have pinged, ftp'd, and telneted across my network.  I'm
> >still working on the web browser.  (Anybody know why Netscrape can't find my
> >Linux box when everything else can?)
> 
> What do you mean by "can't find"?

Well, when I look for http://192.168.0.1 on the browser on my windows box, it just times out.
If I do this on the Linux box, I get expected results.

> 
> >
> > Also, I still don't know where to put the startup commands ifconfig and
> route. > I have this vague notion that they belong in a file called ifcfg-eth0,
>  or >that such a file should exist.  The HowTos say to consult your RedHat
> manual.  >Where's that?  (Funny. While "R"ing the FM, I'm told to RTFM.  Give
> it a rest!)
> 
> If you setup your interface in the Redhat Control panel it will do all this for
> you.

I pointed this out to John, but I think I forgot to post to this group.  The RH Control Panel app says that eth0 is an "unmanaged device" and I cannot edit it.  After executing the following:

find / -type f | xargs grep "unmanaged device" > /tmp/umdev.txt

I was able to discover that it's because ifcfg-eth0 doesn't exist.  Seems kind of circular to me. 

> > Oh, one more thing.  Every so often I get a message that says something like
> >"CU Wedged in eth0 ... resetting" It corresponds to an excessive response time
> >in ping (60-80ms).  Also, I'm getting a 20-30% packet loss.  Is that normal?
>  >(I guess that was 2 more things.  Sorry)
> 
> More evidence of a hardware issue,  or possible bad cable. it is not normal,  I
> can do a ping -f from host to host for hours and only loose a very few packets.
>  And that is on a network with other traffic.

I'll play with the duplicity(what?) of my cards and see what happens.

Thanks Adam.


----------------------------------------------------------------
Get your free email from AltaVista at http://altavista.iname.com