Bug 10663 - RH 6.2 Networking causing problems
Summary: RH 6.2 Networking causing problems
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: net-tools
Version: 6.2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Crutcher Dunnavant
QA Contact:
URL: news:alt.linux.networking
Depends On:
TreeView+ depends on / blocked
Reported: 2000-04-08 17:20 UTC by Dian Pamilih
Modified: 2008-05-01 15:37 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2000-04-18 08:30:23 UTC

Attachments (Terms of Use)

Description Dian Pamilih 2000-04-08 17:20:05 UTC
I've personally experienced problems setting up networking in RH 6.2, but
in 6.1 it worked flawlessly.  It has happened on two separate machines,
I've downloaded the ISO again and reinstalled to check if it was a bad iso
or a bad burn (the iso passed md5).  Here's the basic problem:

I have a lan, and computer 1 running linux just fine can ping the rh 6.2
box no problem (0 PL low ping) computer (rh 6.2) can ping computer 1 with
~80% PL and increasingly long return times (first is ~100 ms, then 4s then
8s, then 16s...(yes it does appear to happen at 2^x more or less... i dont
know why) Both systems have i686 architecture (PIII 450@558 and
MobileCeleron 400) and both ran perfectly with RH 6.1

Comment 1 Alan Cox 2000-04-17 19:58:59 UTC
What network card are you using

Comment 2 Tim Waugh 2000-04-18 08:30:59 UTC
This is because of name lookups failing.  Does 'ping -n ...' give you better

In 6.2, ping will by default give both the IP address and the hostname for ping
replies -- -n turns off DNS lookups, just like traceroute, tcpdump, etc.

Comment 3 Anonymous 2000-04-18 14:02:59 UTC
It is NOT because of name lookup failures.  I am doing 'ping'.  It
is NOT card specific.  Happens with Linksys EtherFAST PCMCIA, Linksys Ether16
(ne2000), D-Link ??? (tulip), an NE2000 PCI card from Kingston I think... as
well as a 3com 3595.

Comment 4 Anonymous 2000-04-18 14:10:59 UTC
It shouldn't be an IP-Masq problem (which is what you'll probably say next) as
the masq server has been running fine for the past 6 months and RH 6.1 is using
it just fine now.

Comment 5 Cristian Gafton 2000-04-18 16:57:59 UTC
can you please try the ping -n as suggested? ping does a reverse lookup on the
address your are giving.

Note You need to log in before you can comment on or make changes to this bug.