Yay: Another Suse 9.1 networking problem

Fenster

Well due to the fact that I more or less killed my hard drive (resetting the mbr is bad, m'kay?), I was obliged to reinstall Win 2k, back everything of note to dvd, wipe my hard drive and then reinstall Suse as its the best choice of OS to get my machine back running how I like it.

Anyways, I followed the same steps as in my last thread to fix up my networking, but my problem now is that I can ping and browse via IP and its as fast as it should be, but when I browse via a url, its slow, slower than a 28k modem would be.

Once again I'll provide any outputs as needed. Here's the basic from ifdown, ifup and ifconfig:

linux:/home/xxxx # ifdown eth0
    eth0      device: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
    eth0      configuration: eth-id-00:0b:6a:2b:ce:d0

linux:/home/xxxx # ifup eth0
    eth0      device: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
    eth0      configuration: eth-id-00:0b:6a:2b:ce:d0
Starting DHCP Client Daemon on eth0... . IP/Netmask: 192.168.1.1 / 255.255.255.0

linux:/home/xxxx # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0B:6A:2B:CE:D0
          inet addr:192.168.1.1  Bcast:255.255.255.255  Mask:255.255.255.0
          inet6 addr: fe80::20b:6aff:fe2b:ced0/64 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4308 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2942 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2216545 (2.1 Mb)  TX bytes:480397 (469.1 Kb)
          Interrupt:11 Base address:0xc000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:742 errors:0 dropped:0 overruns:0 frame:0
          TX packets:742 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:48113 (46.9 Kb)  TX bytes:48113 (46.9 Kb)

Once again, I'm indebted to anyone who can point me the right way.

nadir

/etc/resolv.conf

make sure thats pointing to a good resolving server

also sometimes if your firewall is blocking 'lo' interface wierd time delay problems like this can occur. So if changing the dns resolving server doesnt work try iptables --flush

Fenster

Well I restarted my router when I crawled out of bed this morning and it seems to have fixed it. It was just weird.