> Please help.
> I have a Redhat 6.2 system with a SMC9432TX network card installed.My machine
> is on a LAN.
> If my machine is pinged from another machine the response time is good, if I
> ping the loopback adaptor the response is also good. If I try ping another ma
> chine from my Redhat box the response time is terrible, 7412.0 ms and worse.
> My conf.modules file reads alias eth0 epic100.
> Thanks
> Ian
> [EMAIL PROTECTED]
First, I think you're on the wrong list; there's a separate list for RHL 6.2
stuff, and this belongs there.
I suggest you ask your question there. And offer better information.
I also have SMC9432TX cards.
Here are my figures; this is what you should provide:
eth0 Link encap:Ethernet HWaddr 00:E0:29:07:3B:1B
inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2122009 errors:0 dropped:0 overruns:0 frame:6
TX packets:1838252 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:10 Base address:0x2000
[summer@possum SPECS]$ ping -c3 192.168.1.6
PING 192.168.1.6 (192.168.1.6) from 192.168.1.6 : 56(84) bytes of data.
64 bytes from 192.168.1.6: icmp_seq=0 ttl=255 time=0.1 ms
64 bytes from 192.168.1.6: icmp_seq=1 ttl=255 time=0.1 ms
64 bytes from 192.168.1.6: icmp_seq=2 ttl=255 time=0.1 ms
--- 192.168.1.6 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.1/0.1/0.1 ms
[summer@possum SPECS]$ ping -c3 192.168.1.2
PING 192.168.1.2 (192.168.1.2) from 192.168.1.6 : 56(84) bytes of data.
64 bytes from 192.168.1.2: icmp_seq=0 ttl=255 time=0.8 ms
64 bytes from 192.168.1.2: icmp_seq=1 ttl=255 time=0.7 ms
64 bytes from 192.168.1.2: icmp_seq=2 ttl=255 time=0.7 ms
--- 192.168.1.2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.7/0.7/0.8 ms
[summer@possum SPECS]$ ping -c3 192.168.0.2
PING 192.168.0.2 (192.168.0.2) from 192.168.1.6 : 56(84) bytes of data.
64 bytes from 192.168.0.2: icmp_seq=0 ttl=255 time=1.1 ms
64 bytes from 192.168.0.2: icmp_seq=1 ttl=255 time=0.5 ms
64 bytes from 192.168.0.2: icmp_seq=2 ttl=255 time=0.8 ms
--- 192.168.0.2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.5/0.8/1.1 ms
[summer@possum SPECS]$ ping -c3 bilby
PING bilby.os2.ami.com.au (192.168.0.128) from 192.168.1.6 : 56(84) bytes of
data.
64 bytes from 192.168.0.128: icmp_seq=0 ttl=254 time=1.2 ms
64 bytes from 192.168.0.128: icmp_seq=1 ttl=254 time=1.2 ms
64 bytes from 192.168.0.128: icmp_seq=2 ttl=254 time=1.2 ms
--- bilby.os2.ami.com.au ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 1.2/1.2/1.2 ms
[summer@possum SPECS]$
As you can see, the IP address for the local machine is 192.168.1.6. Ping
times are good. 192.168.1.2 is at the other end of the same wire, and
192.168.0.2 is another interface on the second box. Traffic to bilby (the
final ping) passes through all these interfaces.
If you perform equivalent pings on your system, you will see (and show) just
where the time is spent.
Post that to the RHL 6.2 list.
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list