SUSE 10.0 extremely slow internet connection! what is wrong?
 

Hi,


I know there are a few threads arround but I haven't found one that solved my issue.

I have 3 computer connected to my router that is connected to my cable modem.
one laptop, Dell latitude c810, and 2 custom PC.
I installed Suse 10.0 on the laptop and one of the two desktop. In both cases I formated the hd and did a clean install.

before the Install all pc where running windows XP and internet speed was normal.

after a fresh suse 10.0 install and no additional setup or configuration on the laptop and one of the two desktop::

My pc running windows xp internet speed is normal.
The laptop internet speed is normal.

But the Suse 10.0 desktop internet speed is sllllllllllllllow!

Using any web browser when I type a address, the browser is taking a long time looking up then a long time transfering...

I used Firefox 1.07 and konqueror 3.4..2.

Transfering files between the 3 computer seem hapenning at normal speed, Only the internet
speed is slow.

Does anybody know why since I installed suse 10.0 on my desktop I am having poor internet speed? When it was a windows xp box the internet speed was fine.


Please I need help!!!

Alex

Check your firewall, disable it as your router already has a quite good one.
Disable virus scanners, there are on by default (?) on SUSE 10.0.

Also: Check your running services and disable the firewalls you could find upstream in ypour network.

I would also advice getting a Switch and connecting every machine to the router in an independent way. It's not that they would get faster, but debugging your network is easier: Just attach the router to the switch and attach the rest of the boxes also to the switch. It's the way I use my home network, which is very similar to yours (Gentoo+Kubuntu+SUSE).

More stuff:
Open a terminal (Konsole or Gnome-Terminal) and try pinging www.google.com, write the IP down and try to see wether you get better timings using the IP than using the hostname. In this case the problem is in the DNS service, try disabling dns caching, bind and squid.

Also, if you are using NAT or some kond of bridging, test all teh stuff again on the NAT server or bridged machine.

Are you using a DCHP IP or a Static. If your using a static ip be sure to check your router and see if its detecting the same IP as your system. I had the same problem using a static IP and after i changed it mine worked great.

this is crap

Anyway, you have three possible problems:
1) disable IPv6 (all linux distros with 2.6 kernels wahe thi one on)
2) double check network configuration
3) obviously hardware



However good news:
indicates problems caused by ipv6.
disable it and you should be fine.
Open terminal window and enter:
#echo "alias net-pf-10 off" >> /etc/modprobe.conf
#echo "alias ipv6 off" >> /etc/modprobe.conf

restart computer

You may disable ipv6 in FF only:
anter in FF address bar:
about:config
(no spaces above)
in the search bar inter ipv6
change the vaule of
network.dns.disableIPv6
from false to true

This will resolve dns lookup problems in FF

Actually taking a long time to look up addresses would tend to indicate DNS errors in my experience. Maybe you could hardset the DNS servers for your ISP in your network card configuration with YAST. That would help assuming the problem is what I think it is, which is DNS. Linux in my experience is very DNS picky.

Ups, yes, this is prolly the answer which makes sense.

I forgot to say that I was trying to troubleshoot disabling DNS stuff, and that you shuld re-enable it once the culprit was isolated.At 8:30 in the morning my brain is still jelly, LOL
Having a caching DNS server is a good idea.

BTW, I have my SUSE with IPV6 only and have no problem riding WiFi hotspots through Utrecht, neither speed nor complaints, it runs a bloody hell of fine :)

What does this mean?

And how would one go about doing what you suggest?

Well the easy way is this:

1) Find ISPs DNS... How to do this?
a) You can check your router, see what it pulled as DNS.
b) You can check your modem and see what DNS you are assigned.
c) You can call your ISP(or check their online gateway) and see if they will tell you DNS locations. Some also give you them in setup guides.

2) Yast > Network Devices > Network Card
a) Assuming you are using 9.1-10.0 it will go right away.
b) Assuming you are using 10.1 you need to select traditional with ifup, not Network Manager.(that is auto config and doesn't allow DNS setup.

3) Select your current Network Card. Choose "Edit" of the bottom buttons.

4) You should see a bunch of settings, and further menu options accessable via buttons. Choose "Hostname and Host Server".

5) There are 2 sections. The first is your domain information, and information about your computer. Like its Name. For instance "Hostname" and "Domain". The second section is Name Servers and Domain Listings. You should see Name Servers(3 of them) and a field either called "Search List" or something else on the right hand side. You need to change the name servers(which you will have to turn on the little manually configure box. You can't pull through DHCP.

6) Set the Nameserver #1 as the primary DNS server your ISP uses. Set the Nameserver #2 as the Secondary DNS server your ISP uses. Set Nameserver #3 as your Router/Gateway/Modem.

7) Make sure the top box on the right in that section is set as "site"

8) OK, NEXT, NEXT...etc Until it configures the settings and runs the little SuSE config stuff.

You are done, you should now have happy DNS and direct line to the servers so you don't have to try to get the info through router/gateway which seems to not work so well in linux with home routing equiptment.

You rock!

I did read a few suse 9.0 threads that mentioned about the
ipv6 but I was so tired I must have never rebooted the computer... doh!
I just reverted to my modified modprobe.conf (same lines you sugested)
rebooted and my internet speed is now normal.

Thanks Broch!! and thanks everyone for helping me to resolve this problem.

No actually this makes no sense at all. But it does not matter does it? Problem is resolved.:)

It makes plenty of sense. Every linux box I have run, no matter the distro seems to be slow as hell at resolving DNS through routers and gateways on full DHCP(home, not enterprise stuff). And whether IPv6 is the cause, or it is just some kind of issue with the kernel, hardsetting DNS fixes it.

I could try around later tonight to see if IPv6 or DNS are really at fault, but either way I have found DNS fixes it.

"hardsetting" does not exist
also maybe check your /etc/resolv.conf file
This is one of plenty semi "proffesional" myths. :)

You don't need to "check" anything (IPv6), simply read this:

http://www.ietf.org/rfc/rfc4074.txt

Excerpt:
So it is well know fact since ... 199x (NetBSD KAME project. Check KAME site for history).
You may or may not encounter this, author of first post did.

So wait, you mean I cannot directly input my DNS addresses as Name Servers? You had better let my 3 computers currently doing it in SuSE 10.0, SuSE 10.1 beta, and SLICK know, cause if they are doing it, I am really worried then. You may also want to send a memo back in time over the past 3 or 4 years to me about the 30 distros I have used and tried it with before settling on SuSE, cause I did it with all them too. Or wait, does that just mean I accomplished the unpossible! ME 4 TEH WIN!

I meant that in all cases for me, I never bothered to look at IPv6 as a possible culprit, mostly because I had never cared about IPv6 or even frankly known whether or not I was usign it. In some cases had the same issue on multiple distros, some of which do not have IPv6 support(or at least didn't when I tried them) I had the same issue of resolving DNS. But whether the issue is resolving DNS through DHCP or IPv6 is at fault, telling my network connections in every distro I have tried the DNS servers I want them to use, has corrected the issue of long resolving. It would actualy be interested, if only for my self, in knowing whether or not IPv6 is the culprit, or Linux at large, and that I was planning to test that out by turning of IPv^ and letting my network connection try to fully DHCP itself.

That's summarizes this.
About hardsetting, I answered this before.
I don't think that there is reason to argue.

Not really arguing, just curious why would you say something like "it doesn't exsist" when it quite obviously does and many of us use it as a solution to this problem and others which revolve around nonresolving DNS.