Internet Painfully slow in Fedora

[markcynt]

I'm still on my first day of using Fedora and the internet is painfully slow.

I ran a test on Speedtest.net and got almost identical speeds in Fedora and Mint. However, Fedora takes forever to load webpages and install software from Kpackagekit.

I had this problem in openSUSe and disabling IPV6 fixed it but I can't find that option in Fedora. I'm using KDE 4 by the way.

I was reading in this thread that it might be good to have dnsmasq running but when checked it wasn't. I don't get that running either.

Any help or suggestions would be appreciated.

Thanks

Mark

[markcynt]

I found out that IPV6 was disabled already. So much for that. I also tried openDNS.

[garaden]

Do you ever lose your connection entirely? That's the problem I'm encountering and I'm curious if your issue is similar... sometimes everything works fine, and sometimes I can't access anything, despite no error messages anywhere except "timeout".

[edit] Also, DHCP sends/receives fine. I don't encounter any problems until *after* DHCP configures everything, and even then the connection sometimes behaves... but sometimes it drops out entirely. o_0 [edit]

[markcynt]

Originally Posted by garaden

Do you ever lose your connection entirely? That's the problem I'm encountering and I'm curious if your issue is similar... sometimes everything works fine, and sometimes I can't access anything, despite no error messages anywhere except "timeout".

No I don't lose connection entirely. I'm back to using Mint for now untill I get the problem fixed.

[Cuvou]

I had a similar problem a while back, although mine was DNS-related.

I had my old Linksys router that I got when I lived on the opposite end of the country with a different ISP... when I installed software for my new ISP here on my Windows partition, the internet worked and was fast. On Fedora the Internet was super slow. Turns out my Linksys router cached my old ISP's name servers (on the other end of the country), and 90% of the time it took to load a web page was spent resolving the domain name, and then the page actually loaded really fast after that.

Windows already knew the correct DNS servers thanks to the software my new ISP had me run, but Linux was getting the old DNS servers from the Linksys and it took much longer to resolve domains on the old servers. After clearing the cache from Linksys it was fine.

This probably isn't the problem in your case but it's handy to keep in mind.

[marko]

Originally Posted by markcynt

I found out that IPV6 was disabled already. So much for that. I also tried openDNS.

Turning off ipv6 in the operating system might not be enough,
run firefox, and put in as the location

about:config

and when the config page loads, go to the search tool and put in ipv6
so it shows the settings related to ipv6, of those two set this one to true

network.dns.disableIPv6 true

If by slow you mean you try to go to a page and there's long wait for it to start
then that could be the problem. What's going on is that you've got no ipv 6 in
the OS but Firefox is trying IPV6 DNS first, that times out and it then reverts to
IPV4.

[markcynt]

Originally Posted by marko

Turning off ipv6 in the operating system might not be enough,
run firefox, and put in as the location

about:config

and when the config page loads, go to the search tool and put in ipv6
so it shows the settings related to ipv6, of those two set this one to true

network.dns.disableIPv6 true

If by slow you mean you try to go to a page and there's long wait for it to start
then that could be the problem. What's going on is that you've got no ipv 6 in
the OS but Firefox is trying IPV6 DNS first, that times out and it then reverts to
IPV4.

Thanks marko, that did it.

[superfreek]

Originally Posted by marko

Turning off ipv6 in the operating system might not be enough,
run firefox, and put in as the location

about:config

and when the config page loads, go to the search tool and put in ipv6
so it shows the settings related to ipv6, of those two set this one to true

network.dns.disableIPv6 true

If by slow you mean you try to go to a page and there's long wait for it to start
then that could be the problem. What's going on is that you've got no ipv 6 in
the OS but Firefox is trying IPV6 DNS first, that times out and it then reverts to
IPV4.

I've configured my firefox like Marko sad and the google page it opens it super fast but I tried to open http://forums.fedoraforum.org/ and it tocked 2m & 23s to fully open the page !!!! what can i do ????

[royor]

I cannot claim I know why your network is slow, but I can point out some possible
contributing factors.

1. edit /etc/resolv.conf and be sue you have the right nameservers in it.
Here's mine:

search sbcglobal.net
nameserver 68.94.156.1
nameserver 68.94.157.1
nameserver 192.168.1.254

Notice that the third nameserver is the router. I put it in there for a fallback because sometimes the main dns servers fail, and the router will automatically update it's nameservers.
I do not like to use the router as the first nameserver because of a slight delay it incurrs, and it has no cache.

2. Check yout iptables rules (/etc/sysconfig/iptables). Do you have a bazillion rules? If so, it might cause a slight addition delay for the processing of each paquet. If you wish to modify those rules, then you must

sudo service iptables stop
sudo service ip6tables stop

edit /etc/sysconfig/iptables and /etc/sysconfig/ip6tables.

I do not run ip6tables, because I have no need for that.

When you finish editing:

sudo service iptables start

3. If you are running dnsmasq, then you must see to it that
a. /etc/resolv.conf contains only:

search localhost
nameserver 127.0.0.1

and that /etc/resolv.dnsmasq contains the real stuff which is normally in /etc/resolv.conf

The man page says:

In order to configure dnsmasq to act as cache for the host on which it
is running, put "nameserver 127.0.0.1" in /etc/resolv.conf to force
local processes to send queries to dnsmasq. Then either specify the
upstream servers directly to dnsmasq using --server options or put
their addresses real in another file, say /etc/resolv.dnsmasq and run
dnsmasq with the -r /etc/resolv.dnsmasq option. This second technique
allows for dynamic update of the server addresses by PPP or DHCP.

So, I edited my /etc/init.d/dnsmasq and changed the line:


daemon $dnsmasq $OPTIONS
to
daemon $dnsmasq $OPTIONS -r /etc/resolv.dnsmasq

and then

sudo service dnsmasq restart

I hope this little bit will help.

R.