Redhat 9 - DHCP Config problem

[Nikster]

I'm on a college campus where we have automatic DHCP config for on campus users.

I just installed Redhat 9 and the network seems to be extremely slow! website load up slow or not at all, ssh to on campus servers is choppy.

How can I figure out if the configuration is set correctly or not?

Thanks,

N

 

[Buddha Bart]

i sincerely doubt this has anything to do with dhcp, but...

/sbin/ifconfig

/sbin/route

and

cat /etc/resolv.conf

should give you the info you're looking for.

 

[Nikster]

everything seems to be alright except the errors are a bit high.

eth0 Link encap:Ethernet HWaddr 00:50A:2B:07:8C
inet addr:128.211.111.111 Bcast:128.211.111.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:51894 errors:155 dropped:0 overruns:1 frame:230
TX packets:3752 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:5448644 (5.1 Mb) TX bytes:702840 (686.3 Kb)
Interrupt:11 Base address:0x1080


How do I set a value for the gateway?

 

[Buddha Bart]

How do I set a value for the gateway?

you shouldn't have to, it should come from your dhcp configuration. What did "/sbin/route" print out?

 

[Nikster]

If you need more debug info I'll post that aswell.

Thanks

 

[Buddha Bart]

Originally posted by: Buddha Bart
What did "/sbin/route" print out?

 

[Nikster]

/sbin/route

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
128.211.203.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default tel-210-c6msfc- 0.0.0.0 UG 0 0 0 eth0

/sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:50A:2B:07:8C
inet addr:128.211.203.157 Bcast:128.211.203.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1058 errors:34 dropped:0 overruns:53 frame:52
TX packets:538 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:269461 (263.1 Kb) TX bytes:54965 (53.6 Kb)
Interrupt:11 Base address:0x1080

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3412 errors:0 dropped:0 overruns:0 frame:0
TX packets:3412 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:291904 (285.0 Kb) TX bytes:291904 (285.0 Kb)

/etc/resol.conf
; generated by /sbin/dhclient-script
search resnet.purdue.edu
nameserver 128.210.11.57
nameserver 128.210.11.5

 

[Buddha Bart]

Your host seems fine. keep in mind some of the sloppyest networks on earth are those found in good old academia.

Trace route a few websites, pick a few of the first couple hops, and try running a series of pings against them. If you've got 15ms to your building's router, and 35ms do your campus router, and 250ms to the next router out, its a safe bet that pipe's hurtin. It helps if you can get at a host off-campus and traceroute back in to yourself too, to isolate the problem.

bart

 

[Nikster]

The pings are really good! Maybe it's something with Mozilla.....anandtech loads faster than www.purdue.edu!

What do you say?


[bhogal@hawk-d-157 bhogal]$ ping tel-210-c6msfc-01-203b.tcom.purdue.edu
PING tel-210-c6msfc-01-203b.tcom.purdue.edu (128.211.203.1) 56(84) bytes of data.
64 bytes from tel-210-c6msfc-01-203b.tcom.purdue.edu (128.211.203.1): icmp_seq=1 ttl=255 time=0.496 ms
64 bytes from tel-210-c6msfc-01-203b.tcom.purdue.edu (128.211.203.1): icmp_seq=2 ttl=255 time=0.504 ms
64 bytes from tel-210-c6msfc-01-203b.tcom.purdue.edu (128.211.203.1): icmp_seq=3 ttl=255 time=0.491 ms
64 bytes from tel-210-c6msfc-01-203b.tcom.purdue.edu (128.211.203.1): icmp_seq=4 ttl=255 time=0.598 ms
64 bytes from tel-210-c6msfc-01-203b.tcom.purdue.edu (128.211.203.1): icmp_seq=5 ttl=255 time=0.462 ms

--- tel-210-c6msfc-01-203b.tcom.purdue.edu ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4036ms
rtt min/avg/max/mdev = 0.462/0.510/0.598/0.048 ms
[bhogal@hawk-d-157 bhogal]$ ping tel-210-m10-01-242.tcom.purdue.edu
PING tel-210-m10-01-242.tcom.purdue.edu (128.210.242.251) 56(84) bytes of data.
64 bytes from tel-210-m10-01-242.tcom.purdue.edu (128.210.242.251): icmp_seq=1 ttl=254 time=0.864 ms
64 bytes from tel-210-m10-01-242.tcom.purdue.edu (128.210.242.251): icmp_seq=2 ttl=254 time=7.08 ms
64 bytes from tel-210-m10-01-242.tcom.purdue.edu (128.210.242.251): icmp_seq=3 ttl=254 time=0.880 ms
64 bytes from tel-210-m10-01-242.tcom.purdue.edu (128.210.242.251): icmp_seq=4 ttl=254 time=8.70 ms
64 bytes from tel-210-m10-01-242.tcom.purdue.edu (128.210.242.251): icmp_seq=5 ttl=254 time=0.882 ms
64 bytes from tel-210-m10-01-242.tcom.purdue.edu (128.210.242.251): icmp_seq=6 ttl=254 time=1.10 ms
64 bytes from tel-210-m10-01-242.tcom.purdue.edu (128.210.242.251): icmp_seq=7 ttl=254 time=0.816 ms
64 bytes from tel-210-m10-01-242.tcom.purdue.edu (128.210.242.251): icmp_seq=8 ttl=254 time=0.869 ms
64 bytes from tel-210-m10-01-242.tcom.purdue.edu (128.210.242.251): icmp_seq=9 ttl=254 time=7.78 ms

--- tel-210-m10-01-242.tcom.purdue.edu ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8051ms
rtt min/avg/max/mdev = 0.816/3.221/8.708/3.303 ms
[bhogal@hawk-d-157 bhogal]$ ping gigapop.tcom.purdue.edu
PING gigapop.tcom.purdue.edu (192.5.40.14) 56(84) bytes of data.
64 bytes from gigapop.tcom.purdue.edu (192.5.40.14): icmp_seq=1 ttl=253 time=2.53 ms
64 bytes from gigapop.tcom.purdue.edu (192.5.40.14): icmp_seq=2 ttl=253 time=2.74 ms
64 bytes from gigapop.tcom.purdue.edu (192.5.40.14): icmp_seq=3 ttl=253 time=2.74 ms
64 bytes from gigapop.tcom.purdue.edu (192.5.40.14): icmp_seq=4 ttl=253 time=2.34 ms
64 bytes from gigapop.tcom.purdue.edu (192.5.40.14): icmp_seq=5 ttl=253 time=3.86 ms
64 bytes from gigapop.tcom.purdue.edu (192.5.40.14): icmp_seq=6 ttl=253 time=2.80 ms
64 bytes from gigapop.tcom.purdue.edu (192.5.40.14): icmp_seq=7 ttl=253 time=2.68 ms

--- gigapop.tcom.purdue.edu ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6059ms
rtt min/avg/max/mdev = 2.348/2.817/3.861/0.455 ms
[bhogal@hawk-d-157 bhogal]$ ping sd-ul.indiana.gigapop.net
PING sd-ul.indiana.gigapop.net (192.12.206.245) 56(84) bytes of data.
64 bytes from sd-ul.indiana.gigapop.net (192.12.206.245): icmp_seq=1 ttl=252 time=2.56 ms
64 bytes from sd-ul.indiana.gigapop.net (192.12.206.245): icmp_seq=3 ttl=252 time=2.81 ms
64 bytes from sd-ul.indiana.gigapop.net (192.12.206.245): icmp_seq=4 ttl=252 time=2.68 ms
64 bytes from sd-ul.indiana.gigapop.net (192.12.206.245): icmp_seq=5 ttl=252 time=3.47 ms
64 bytes from sd-ul.indiana.gigapop.net (192.12.206.245): icmp_seq=6 ttl=252 time=2.60 ms

--- sd-ul.indiana.gigapop.net ping statistics ---
6 packets transmitted, 5 received, 16% packet loss, time 5044ms
rtt min/avg/max/mdev = 2.569/2.827/3.470/0.336 ms

[bhogal@hawk-d-157 bhogal]$ ping www.google.com
PING www.google.com (216.239.53.99) 56(84) bytes of data.
64 bytes from 216.239.53.99: icmp_seq=1 ttl=44 time=68.3 ms
64 bytes from 216.239.53.99: icmp_seq=2 ttl=44 time=68.2 ms
64 bytes from 216.239.53.99: icmp_seq=3 ttl=44 time=68.2 ms
64 bytes from 216.239.53.99: icmp_seq=4 ttl=44 time=67.1 ms
64 bytes from 216.239.53.99: icmp_seq=5 ttl=44 time=68.6 ms

--- www.google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 5184ms
rtt min/avg/max/mdev = 67.186/68.157/68.636/0.577 ms
[bhogal@hawk-d-157 bhogal]$ ping www.yahoo.com
PING www.yahoo.akadns.net (216.109.125.69) 56(84) bytes of data.
64 bytes from w16.www.dcn.yahoo.com (216.109.125.69): icmp_seq=1 ttl=48 time=22.7 ms
64 bytes from w16.www.dcn.yahoo.com (216.109.125.69): icmp_seq=2 ttl=48 time=23.2 ms
64 bytes from w16.www.dcn.yahoo.com (216.109.125.69): icmp_seq=3 ttl=48 time=22.7 ms
64 bytes from w16.www.dcn.yahoo.com (216.109.125.69): icmp_seq=4 ttl=48 time=22.7 ms
64 bytes from w16.www.dcn.yahoo.com (216.109.125.69): icmp_seq=5 ttl=48 time=22.9 ms

--- www.yahoo.akadns.net ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 8188ms
rtt min/avg/max/mdev = 22.709/22.880/23.248/0.242 ms
[bhogal@hawk-d-157 bhogal]$ ping expert.cc.purdue.edu
PING expert.ics.purdue.edu (128.210.10.11) 56(84) bytes of data.
64 bytes from expert.ics.purdue.edu (128.210.10.11): icmp_seq=1 ttl=253 time=1.72 ms
64 bytes from expert.ics.purdue.edu (128.210.10.11): icmp_seq=2 ttl=253 time=1.47 ms
64 bytes from expert.ics.purdue.edu (128.210.10.11): icmp_seq=3 ttl=253 time=1.61 ms
64 bytes from expert.ics.purdue.edu (128.210.10.11): icmp_seq=4 ttl=253 time=1.47 ms
64 bytes from expert.ics.purdue.edu (128.210.10.11): icmp_seq=5 ttl=253 time=1.41 ms

--- expert.ics.purdue.edu ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4035ms
rtt min/avg/max/mdev = 1.418/1.541/1.724/0.117 ms
[bhogal@hawk-d-157 bhogal]$ ping www.purdue.edu
PING mortar.cc.purdue.edu (128.210.11.200) 56(84) bytes of data.
64 bytes from mortar.cc.purdue.edu (128.210.11.200): icmp_seq=1 ttl=253 time=0.496 ms
64 bytes from mortar.cc.purdue.edu (128.210.11.200): icmp_seq=2 ttl=253 time=0.549 ms
64 bytes from mortar.cc.purdue.edu (128.210.11.200): icmp_seq=3 ttl=253 time=0.466 ms
64 bytes from mortar.cc.purdue.edu (128.210.11.200): icmp_seq=4 ttl=253 time=0.490 ms
64 bytes from mortar.cc.purdue.edu (128.210.11.200): icmp_seq=5 ttl=253 time=0.636 ms

--- mortar.cc.purdue.edu ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4043ms
rtt min/avg/max/mdev = 0.466/0.527/0.636/0.064 ms

 

[Buddha Bart]

So this server to which you said ssh'ing is slow and choppy... ping that. Also, is it a heavily used server?

If you're used to something like IE on Win2K, the hell yea Mozilla on Gnome/KDE on Linux will be so slow you could honstly mistake it for network problems. Especially on a relativly slow machine.

Try using Phoenix. It got so much support for being a trimmer and faster version of mozilla, that its going to become the new main-browser of the mozilla project. Just to avoid some confusion for you, its also gonna be named Firebird when the next one comes out. Thats why the pages are all labeled that.

bart

 

[Nikster]

I used ethereal to capture packets on eth0

Apart from other traffic this is what I got that was related to me my ip when no net application was running.

It looks like a periodic 5 second DNS query, maybe something needs to changed to fix this?

[root@hawk-d-157 bhogal]# grep 128.211.203.157 trace
0.665372 128.211.203.157 -> 128.210.11.57 DNS Standard query A localhost.resnet.purdue.edu
0.667469 128.210.11.57 -> 128.211.203.157 DNS Standard query response A 127.0.0.1
5.675364 128.211.203.157 -> 128.210.11.57 DNS Standard query A localhost.resnet.purdue.edu
5.678724 128.210.11.57 -> 128.211.203.157 DNS Standard query response A 127.0.0.1
10.685362 128.211.203.157 -> 128.210.11.57 DNS Standard query A localhost.resnet.purdue.edu
10.688798 128.210.11.57 -> 128.211.203.157 DNS Standard query response A 127.0.0.1
15.695352 128.211.203.157 -> 128.210.11.57 DNS Standard query A localhost.resnet.purdue.edu
15.697410 128.210.11.57 -> 128.211.203.157 DNS Standard query response A 127.0.0.1