Hi, oh great eagles (um.. penguins )

I am running a small network at home consisting of several Debian boxes as well as a W$98 box, and a laptop, all with a physical connection to a DLink 604 router / switch. As I am forever swithcing machines and distros around, I recently changed the LAN to use DHCP. (My ISP also uses DHCP).

I was mucking around today and discovered the following:

knoppix@laptop:~$ ping steve
PING steve.home.net (xx.xx.xxx.xxx): 56 data bytes
64 bytes from xx.xx.xxx.xxx: icmp_seq=0 ttl=234 time=125.7 ms
64 bytes from xx.xx.xxx.xxx: icmp_seq=1 ttl=234 time=125.6 ms
64 bytes from xx.xx.xxx.xxx: icmp_seq=2 ttl=234 time=126.4 ms
64 bytes from xx.xx.xxx.xxx: icmp_seq=3 ttl=234 time=127.1 ms
64 bytes from xx.xx.xxx.xxx: icmp_seq=4 ttl=234 time=126.9 ms

Then I logged onto the router, and found the router assigned address for steve, and pinged that:

knoppix@laptop:~$ ping 192.168.0.103
PING 192.168.0.103 (192.168.0.103): 56 data bytes
64 bytes from 192.168.0.103: icmp_seq=0 ttl=64 time=0.6 ms
64 bytes from 192.168.0.103: icmp_seq=1 ttl=64 time=0.2 ms
64 bytes from 192.168.0.103: icmp_seq=2 ttl=64 time=0.2 ms
64 bytes from 192.168.0.103: icmp_seq=3 ttl=64 time=0.2 ms

Wow! Is this difference reasonable?

Does everyone use static IP internally with type of setup?



Steve

I may be wrong, but it looks more like a dns problem than dhcp.

Anyone else?

Regards

Sorry, I hit the send button too quick.

I have Dlink 704 router.
1. Redhat 8.0 Static IP
2. Redhat 8.0 Static IP
3. Dual boot WinXP dhcp / Redhat 9.0 Static IP
4. Dual boot WinXP dhcp / Redhat 9.0 dhcp

All four of these are connected to the Dlink router. I don't see any lag in the name resolving on any of them.

Hope this helps.

Regards

Thanx for the response.

Isn't THIS "dns" provided by the switch, though? I just assumed that it would store that information on itself?


Steve

Check and make sure that your machine is using the real dns addresses instead of your routers address for dns.

Are you having any delay on resolving name for websites?

Regards

Hmmm ...

resolv.conf:

search home.net
nameserver 192.168.0.1

I had noticed this, but thought this was normal for DHCP (My ISP recently changed over to DHCP)

YES!!!!!!
I thought it was just my POS ISP (Just joking - they're pretty good, usually)
So .. , even hen my ISP is on DHCP I should still enter the DNS manually?


Steve

Is it just the linux box that lags? Or does the Win98 box do the same thing?

Try manually input of the dns and see if it helps.

This is wierd.

Sorry about the delay - I had to reset a few things

I have gone back to static ethernet, and things are much better:

4 bytes from 192.168.0.11: icmp_seq=0 ttl=64 time=0.1 ms
64 bytes from 192.168.0.11: icmp_seq=1 ttl=64 time=0.0 ms
64 bytes from 192.168.0.11: icmp_seq=2 ttl=64 time=0.0 ms
64 bytes from 192.168.0.11: icmp_seq=3 ttl=64 time=0.0 ms
64 bytes from 192.168.0.11: icmp_seq=4 ttl=64 time=0.1 ms
64 bytes from 192.168.0.11: icmp_seq=5 ttl=64 time=0.0 ms

--- debian1.home.net ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 0.0/0.0/0.1 ms
root@laptop:/home/knoppix# ping 192.168.0.11
PING 192.168.0.11 (192.168.0.11): 56 data bytes
64 bytes from 192.168.0.11: icmp_seq=0 ttl=64 time=0.1 ms
64 bytes from 192.168.0.11: icmp_seq=1 ttl=64 time=0.0 ms
64 bytes from 192.168.0.11: icmp_seq=2 ttl=64 time=0.0 ms
64 bytes from 192.168.0.11: icmp_seq=3 ttl=64 time=0.1 ms
64 bytes from 192.168.0.11: icmp_seq=4 ttl=64 time=0.0 ms


Still confused, but getting there. Now to UNDERSTAND what is going on!
Thanx for the help1


Steve

OK, brainfart - I was pinging myself there, things are still good, though:

root@laptop:/home/knoppix# ping debian1
PING debian1.home.net (192.168.0.3): 56 data bytes
64 bytes from 192.168.0.3: icmp_seq=0 ttl=64 time=1.6 ms
64 bytes from 192.168.0.3: icmp_seq=1 ttl=64 time=0.2 ms
64 bytes from 192.168.0.3: icmp_seq=2 ttl=64 time=0.2 ms
64 bytes from 192.168.0.3: icmp_seq=3 ttl=64 time=0.1 ms
64 bytes from 192.168.0.3: icmp_seq=4 ttl=64 time=0.1 ms

--- debian1.home.net ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.1/0.4/1.6 ms
root@laptop:/home/knoppix# ping 192.168.0.3
PING 192.168.0.3 (192.168.0.3): 56 data bytes
64 bytes from 192.168.0.3: icmp_seq=0 ttl=64 time=0.2 ms
64 bytes from 192.168.0.3: icmp_seq=1 ttl=64 time=0.2 ms
64 bytes from 192.168.0.3: icmp_seq=2 ttl=64 time=0.2 ms
64 bytes from 192.168.0.3: icmp_seq=3 ttl=64 time=0.1 ms
64 bytes from 192.168.0.3: icmp_seq=4 ttl=64 time=0.1 ms
64 bytes from 192.168.0.3: icmp_seq=5 ttl=64 time=0.1 ms


Steve

put your ISP's DNS server ip's in your resolv.conf i think then it should work.

Yes, that's what I did. (See above) "Something" had changed my resolv.conf. Things are much better now.

Thanx!
Steve

I'm glad it's working for you now. Always glad to help.

Regards

I am also trying to configure the same, my drivers are loaded on Red hat 5.5 with Dlink 125 and it shows it's connected but internet still does not work

100% packet drops , any suggestions