LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 06-19-2004, 06:38 PM   #1
kareltjekrul
LQ Newbie
 
Registered: Jun 2004
Distribution: suse9.1
Posts: 2

Rep: Reputation: 0
Internet slow with suse9.1


I have installed suse9.1 a couple of weeks ago and everything works fine
now except for my internetconnection.
The connection itself is not the problem but it takes a long while after typing an url in
the webbrowser ( konqueror or firefox ) before it even starts searching, and building the pages takes a while too. When I use windowsXP on the same machine there's no problem at all.The box is behind a regular router and other machines (windows) have no problems.
I have tried dhcp and static adresses but that makes no difference,using another Nic
gives the same result.Switching off the firewall same,etc.
I suppose it must be something in my networkconfigurations,but I've checked
all as far as I know.
Anyone know where to look for?
 
Old 06-19-2004, 08:43 PM   #2
homey
Senior Member
 
Registered: Oct 2003
Posts: 3,057

Rep: Reputation: 61
I've seen that question pop up a few times and the general idea is that it's related to ipv6. Searching around on the web, a solution which seems to work is to add this line to your /etc/modprobe.conf file.....
alias net-pf-10 off

Last edited by homey; 06-19-2004 at 08:44 PM.
 
Old 06-20-2004, 02:49 AM   #3
yichun
LQ Newbie
 
Registered: Mar 2004
Distribution: Debian Sid
Posts: 18

Rep: Reputation: 0
I have a similiar problem with Debian sid. I can ping domain names (name resolved quickly). but browser takes ages to resolve a url. I adjust the MTU of my NIC to the same value with it is under windows, and disabled ipv6, but still no joy.

Even, my laptop even timeouts when "telnet www.google.com 80" or "telnet [IP] 80"
But this might be another problem.
 
Old 06-20-2004, 04:56 AM   #4
andrewdodsworth
Member
 
Registered: Oct 2003
Location: United Kingdom
Distribution: SuSE 10.0 - 11.4
Posts: 347

Rep: Reputation: 30
I had this problem when I first installed SuSE 9.0 a while back and thought it was IPv6 but it turned out to be a DNS problem - because the DNS lookups were being done with IPv6 first before normal IP it had to wait a long time for no response before dropping down to normal stuff - hence I also was blaming IPv6 for the problem.

I solved the issue by making sure the default gateway is set to my router and if you don't have a local DNS server putting your ISPs DNS server addresses in as your nameservers. I use YaST to do this - Network services .. DNS and Hostname.

Good luck.

If this doesn't solve your problem then I suggest using ethereal (or similar) to capture the packets and identify what's going on.

Last edited by andrewdodsworth; 06-20-2004 at 05:05 AM.
 
Old 06-20-2004, 04:14 PM   #5
kareltjekrul
LQ Newbie
 
Registered: Jun 2004
Distribution: suse9.1
Posts: 2

Original Poster
Rep: Reputation: 0
thnx homey and andrewdodsworth,

I,ve used both suggestions and my internetspeed has improved a lot.
Internet is still slower than the other machines but has speeded up with 60% or so !
I will keep searching for the maybe 100% solution but up to now you,ve helped me
a lot. Thanks again.

Greetings Ben............
 
Old 06-21-2004, 01:56 PM   #6
yichun
LQ Newbie
 
Registered: Mar 2004
Distribution: Debian Sid
Posts: 18

Rep: Reputation: 0
Quote:
Originally posted by andrewdodsworth

If this doesn't solve your problem then I suggest using ethereal (or similar) to capture the packets and identify what's going on.
These are what I got from tcpdump when `lynx www.usc.edu`:
(192.168.0.6 is my NIC, gateway is 192.168.0.1, the ns7 and ns10.attbi.com is the nameserver in /etc/resolv.conf)

09:22:34.459658 IP 192.168.0.6.1043 > ns7.attbi.com.domain: 3747+ AAAA? www.usc.edu. (29)
09:22:39.458444 arp who-has 192.168.0.1 tell 192.168.0.6
09:22:39.459569 IP 192.168.0.6.1044 > ns10.attbi.com.domain: 3747+ AAAA? www.usc.edu. (29)
09:22:39.460586 arp reply 192.168.0.1 is-at 00:09:5b:9f:2a:32
09:22:44.459687 IP 192.168.0.6.1043 > ns7.attbi.com.domain: 3747+ AAAA? www.usc.edu. (29)
09:22:49.459922 IP 192.168.0.6.1044 > ns10.attbi.com.domain: 3747+ AAAA? www.usc.edu. (29)
09:22:54.460287 IP 192.168.0.6.1044 > ns7.attbi.com.domain: 3748+ AAAA? www.usc.edu.we1.client2.attbi.com. (51)
09:22:59.460425 IP 192.168.0.6.1045 > ns10.attbi.com.domain: 3748+ AAAA? www.usc.edu.we1.client2.attbi.com. (51)
09:23:04.460678 IP 192.168.0.6.1044 > ns7.attbi.com.domain: 3748+ AAAA? www.usc.edu.we1.client2.attbi.com. (51)
09:23:09.460924 IP 192.168.0.6.1045 > ns10.attbi.com.domain: 3748+ AAAA? www.usc.edu.we1.client2.attbi.com. (51)
09:23:14.460118 arp who-has 192.168.0.1 tell 192.168.0.6
09:23:14.461248 IP 192.168.0.6.1045 > ns7.attbi.com.domain: 3749+ A? www.usc.edu. (29)
09:23:14.464744 arp reply 192.168.0.1 is-at 00:09:5b:9f:2a:32
09:23:14.520730 IP ns7.attbi.com.domain > 192.168.0.6.1045: 3749 2/2/2 A cwis.usc.edu, (145)
09:23:14.524524 IP 192.168.0.6.1045 > ns7.attbi.com.domain: 3273+ AAAA? www.usc.edu. (29)
09:23:19.524416 IP 192.168.0.6.1046 > ns10.attbi.com.domain: 3273+ AAAA? www.usc.edu. (29)
09:23:24.524592 IP 192.168.0.6.1045 > ns7.attbi.com.domain: 3273+ AAAA? www.usc.edu. (29)
09:23:29.524829 IP 192.168.0.6.1046 > ns10.attbi.com.domain: 3273+ AAAA? www.usc.edu. (29)
09:23:34.525139 IP 192.168.0.6.1046 > ns7.attbi.com.domain: 3274+ AAAA? www.usc.edu.we1.client2.attbi.com. (51)
09:23:39.525346 IP 192.168.0.6.1047 > ns10.attbi.com.domain: 3274+ AAAA? www.usc.edu.we1.client2.attbi.com. (51)
09:23:39.687539 IP ns7.attbi.com.domain > 192.168.0.6.1029: 29 2/6/6[|domain]
09:23:39.687599 IP 192.168.0.6 > ns7.attbi.com: icmp 348: 192.168.0.6 udp port 1029 unreachable
09:23:44.524553 arp who-has 192.168.0.1 tell 192.168.0.6
09:23:44.525556 IP 192.168.0.6.1046 > ns7.attbi.com.domain: 3274+ AAAA? www.usc.edu.we1.client2.attbi.com. (51)
09:23:44.527730 arp reply 192.168.0.1 is-at 00:09:5b:9f:2a:32
09:23:49.525829 IP 192.168.0.6.1047 > ns10.attbi.com.domain: 3274+ AAAA? www.usc.edu.we1.client2.attbi.com. (51)
09:23:54.526163 IP 192.168.0.6.1047 > ns7.attbi.com.domain: 3275+ A? www.usc.edu. (29)
09:23:54.630050 IP ns7.attbi.com.domain > 192.168.0.6.1047: 3275* 2/2/2 A[|domain]
09:23:54.632134 IP 192.168.0.6.1033 > cwis.usc.edu.www: S 1472938783:1472938783(0) win 5808 <mss 1452,sackOK,timestamp 864420 0,nop,wscale 0>
09:23:54.652061 IP cwis.usc.edu.www > 192.168.0.6.1033: S 281057898:281057898(0) ack 1472938784 win 51480 <nop,nop,timestamp 313868834 864420,nop,wscale 2,nop,nop,sackOK,mss 1460>
09:23:54.652118 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 1 win 5808 <nop,nop,timestamp 864440 313868834>
09:23:54.654076 IP 192.168.0.6.1033 > cwis.usc.edu.www: P 1:217(216) ack 1 win 5808 <nop,nop,timestamp 864442 313868834>
09:23:54.689054 IP cwis.usc.edu.www > 192.168.0.6.1033: . ack 217 win 51480 <nop,nop,timestamp 313868837 864442>
09:23:54.718038 IP cwis.usc.edu.www > 192.168.0.6.1033: . 1:1441(1440) ack 217 win 51480 <nop,nop,timestamp 313868840 864442>
09:23:54.718078 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 1441 win 8640 <nop,nop,timestamp 864506 313868840>
09:23:54.726043 IP cwis.usc.edu.www > 192.168.0.6.1033: P 2881:4321(1440) ack 217 win 51480 <nop,nop,timestamp 313868840 864442>
09:23:54.726128 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 1441 win 8640 <nop,nop,timestamp 864514 313868840,nop,nop,sack sack 1 {2881:4321} >
09:23:54.728034 IP cwis.usc.edu.www > 192.168.0.6.1033: P 1441:2881(1440) ack 217 win 51480 <nop,nop,timestamp 313868840 864442>
09:23:54.728074 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 4321 win 11520 <nop,nop,timestamp 864516 313868840>
09:23:54.750036 IP cwis.usc.edu.www > 192.168.0.6.1033: . 4321:5761(1440) ack 217 win 51480 <nop,nop,timestamp 313868843 864506>
09:23:54.750087 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 5761 win 14400 <nop,nop,timestamp 864538 313868843>
09:23:54.755032 IP cwis.usc.edu.www > 192.168.0.6.1033: . 5761:7201(1440) ack 217 win 51480 <nop,nop,timestamp 313868843 864506>
09:23:54.755069 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 7201 win 17280 <nop,nop,timestamp 864543 313868843>
09:23:54.757031 IP cwis.usc.edu.www > 192.168.0.6.1033: . 7201:8641(1440) ack 217 win 51480 <nop,nop,timestamp 313868844 864516>
09:23:54.757056 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 8641 win 20160 <nop,nop,timestamp 864545 313868844>
09:23:54.774075 IP cwis.usc.edu.www > 192.168.0.6.1033: . 10081:11521(1440) ack 217 win 51480 <nop,nop,timestamp 313868844 864516>
09:23:54.774209 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 8641 win 20160 <nop,nop,timestamp 864562 313868844,nop,nop,sack sack 1 {10081:11521} >
09:23:54.800025 IP cwis.usc.edu.www > 192.168.0.6.1033: . 11521:12961(1440) ack 217 win 51480 <nop,nop,timestamp 313868848 864538>
09:23:54.800055 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 8641 win 20160 <nop,nop,timestamp 864588 313868844,nop,nop,sack sack 1 {10081:12961} >
09:23:54.812023 IP cwis.usc.edu.www > 192.168.0.6.1033: . 12961:14401(1440) ack 217 win 51480 <nop,nop,timestamp 313868848 864538>
09:23:54.812057 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 8641 win 20160 <nop,nop,timestamp 864600 313868844,nop,nop,sack sack 1 {10081:14401} >
09:23:54.816017 IP cwis.usc.edu.www > 192.168.0.6.1033: . 14401:15841(1440) ack 217 win 51480 <nop,nop,timestamp 313868848 864543>
09:23:54.816045 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 8641 win 20160 <nop,nop,timestamp 864604 313868844,nop,nop,sack sack 1 {10081:15841} >
09:23:54.818022 IP cwis.usc.edu.www > 192.168.0.6.1033: . 15841:17281(1440) ack 217 win 51480 <nop,nop,timestamp 313868848 864543>
09:23:54.818053 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 8641 win 20160 <nop,nop,timestamp 864606 313868844,nop,nop,sack sack 1 {10081:17281} >
09:23:54.820020 IP cwis.usc.edu.www > 192.168.0.6.1033: . 17281:18721(1440) ack 217 win 51480 <nop,nop,timestamp 313868849 864545>
09:23:54.820046 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 8641 win 20160 <nop,nop,timestamp 864608 313868844,nop,nop,sack sack 1 {10081:18721} >
09:23:54.822020 IP cwis.usc.edu.www > 192.168.0.6.1033: . 18721:20161(1440) ack 217 win 51480 <nop,nop,timestamp 313868849 864545>
09:23:54.822047 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 8641 win 20160 <nop,nop,timestamp 864610 313868844,nop,nop,sack sack 1 {10081:20161} >
09:23:54.852015 IP cwis.usc.edu.www > 192.168.0.6.1033: . 8641:10081(1440) ack 217 win 51480 <nop,nop,timestamp 313868853 864600>
09:23:54.852051 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 20161 win 23040 <nop,nop,timestamp 864640 313868853>
09:23:54.869054 IP cwis.usc.edu.www > 192.168.0.6.1033: . 20161:21601(1440) ack 217 win 51480 <nop,nop,timestamp 313868855 864606>
09:23:54.869175 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 21601 win 25920 <nop,nop,timestamp 864657 313868855>
09:23:54.874015 IP cwis.usc.edu.www > 192.168.0.6.1033: . 21601:23041(1440) ack 217 win 51480 <nop,nop,timestamp 313868856 864608>
09:23:54.874065 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 23041 win 28800 <nop,nop,timestamp 864662 313868856>
09:23:54.887010 IP cwis.usc.edu.www > 192.168.0.6.1033: . 23041:24481(1440) ack 217 win 51480 <nop,nop,timestamp 313868857 864610>
09:23:54.887056 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 24481 win 31680 <nop,nop,timestamp 864675 313868857>
09:23:54.891007 IP cwis.usc.edu.www > 192.168.0.6.1033: . 24481:25921(1440) ack 217 win 51480 <nop,nop,timestamp 313868857 864640>
09:23:54.891038 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 25921 win 34560 <nop,nop,timestamp 864679 313868857>
09:23:54.893008 IP cwis.usc.edu.www > 192.168.0.6.1033: . 25921:27361(1440) ack 217 win 51480 <nop,nop,timestamp 313868857 864640>
09:23:54.893042 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 27361 win 34560 <nop,nop,timestamp 864681 313868857>
09:23:54.911006 IP cwis.usc.edu.www > 192.168.0.6.1033: . 27361:28801(1440) ack 217 win 51480 <nop,nop,timestamp 313868857 864657>
09:23:54.911036 IP 192.168.0.6.1033 > cwis.usc.edu.www: . ack 28801 win 34560 <nop,nop,timestamp 864699 313868857>
09:23:54.913002 IP cwis.usc.edu.www > 192.168.0.6.1033: FP 28801:29873(1072) ack 217 win 51480 <nop,nop,timestamp 313868858 864662>
09:23:54.915056 IP 192.168.0.6.1033 > cwis.usc.edu.www: F 217:217(0) ack 29874 win 34560 <nop,nop,timestamp 864703 313868858>
09:23:54.941002 IP cwis.usc.edu.www > 192.168.0.6.1033: . ack 218 win 51480 <nop,nop,timestamp 313868863 864703>

Any suggestion appreciated!

Last edited by yichun; 06-21-2004 at 05:48 PM.
 
Old 06-21-2004, 04:44 PM   #7
sfamonkey
LQ Newbie
 
Registered: Jun 2004
Posts: 7

Rep: Reputation: 0
hope you can solve problem
 
Old 06-21-2004, 05:47 PM   #8
andrewdodsworth
Member
 
Registered: Oct 2003
Location: United Kingdom
Distribution: SuSE 10.0 - 11.4
Posts: 347

Rep: Reputation: 30
Quote:
Originally posted by yichun
I have a similiar problem with Debian sid. I can ping domain names (name resolved quickly). but browser takes ages to resolve a url. I adjust the MTU of my NIC to the same value with it is under windows, and disabled ipv6, but still no joy.

Even, my laptop even timeouts when "telnet www.google.com 80" or "telnet [IP] 80"
But this might be another problem.
Don't think this is the same problem - if you're resolving DNS names and pinging successfully then doesn't sound like DNS issue. Have you tried the Debian forum to see if it's a problem with your distro or the browser you are using? It could also be the MTU settings dependant on what your router can handle.
 
Old 06-21-2004, 05:51 PM   #9
yichun
LQ Newbie
 
Registered: Mar 2004
Distribution: Debian Sid
Posts: 18

Rep: Reputation: 0
Quote:
Originally posted by andrewdodsworth
Don't think this is the same problem - if you're resolving DNS names and pinging successfully then doesn't sound like DNS issue. Have you tried the Debian forum to see if it's a problem with your distro or the browser you are using? It could also be the MTU settings dependant on what your router can handle.
No, I feel it is not the same issue. But did you notice that this resolution take about 2min to get a result? That is the problem.

It is not an MTU issue because `lynx "ip"` works just fine. I've adjusted the MTU value to the value in Windowz XP, but still no joy.

I will try Debian forum, but do you mean debian forum of LInuxQuestions?(sorry)

Last edited by yichun; 06-21-2004 at 05:57 PM.
 
Old 06-22-2004, 02:47 AM   #10
andrewdodsworth
Member
 
Registered: Oct 2003
Location: United Kingdom
Distribution: SuSE 10.0 - 11.4
Posts: 347

Rep: Reputation: 30
Well I've found a lot on the LQ forums but search any forum for help. I don't know what browser you are using - if it's specific to that one have you tried another? I tend to use Konqueror (KDE) by default as it's the most compatible with the financial sites I use that expect IE but I also like Firefox.

I'll have another look later on today.

Good luck
 
Old 06-22-2004, 05:11 PM   #11
andrewdodsworth
Member
 
Registered: Oct 2003
Location: United Kingdom
Distribution: SuSE 10.0 - 11.4
Posts: 347

Rep: Reputation: 30
yichun
Had a chance to look at your tcpdump listing and it does indeed look similar to the IPv6 issue I had. The 'AAAA' queries are IPv6 DNS queries which aren't finding anything whereas the 'A' query is the IPv4 type which gets an instant response.

A long shot - I know you've said that you've specified the nameservers but have you specified them as names or IPv4 numbers in resolv.conf?
 
Old 06-22-2004, 10:07 PM   #12
javierm
LQ Newbie
 
Registered: Jun 2004
Posts: 3

Rep: Reputation: 0
what was end-of-this-history ... Suse 9.1+Internet = too slow ?
 
Old 06-23-2004, 05:19 AM   #13
andrewdodsworth
Member
 
Registered: Oct 2003
Location: United Kingdom
Distribution: SuSE 10.0 - 11.4
Posts: 347

Rep: Reputation: 30
yichun

Had a play around on my system to see if I could break it and get the same errors as you did. What I found was that without a default gateway nothing works. I have a local DNS server. I tried pinging your 2 nameservers and got slowish responses back (as expected as I'm in the UK). I then stopped my DNS server took 127.0.0.1 out of resolv.conf and put your nameserver in as my default - timed out eventually with no response. I then put my DNS server back in but after yours which then gave me the symptoms you're observing - very long waits for a response from your nameserver -which it doesn't get in time - before dropping through to my DNS server which then gets the pages up.

Therefore it looks like a problem with the nameservers you are using possibly complicated by the IPv6 requests. I suggest try a different nameserver.
 
Old 06-23-2004, 05:22 AM   #14
andrewdodsworth
Member
 
Registered: Oct 2003
Location: United Kingdom
Distribution: SuSE 10.0 - 11.4
Posts: 347

Rep: Reputation: 30
Quote:
Originally posted by javierm
what was end-of-this-history ... Suse 9.1+Internet = too slow ?
Not necessarily - I've used SuSE 9.1 successfully - few issues but not internet speed.
 
Old 06-23-2004, 07:49 PM   #15
yichun
LQ Newbie
 
Registered: Mar 2004
Distribution: Debian Sid
Posts: 18

Rep: Reputation: 0
andrewdodsworth

Thanks so much! I guess It did be the dns issue. These two dns servers are specified as IPv4 addresses in /etc/resolv.conf when the interface gets brought up by an ifup (using dhclient). The ISP is Comcast.

Is there an elegant way to customize resolv.conf (just modified the dns servers entry to better ones) every time the interface got brought up?

Last edited by yichun; 06-23-2004 at 07:50 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
New Fedora Internet connection slow slow slow matrim Fedora 9 07-29-2005 01:39 PM
Help? Slow SUSE9.3 after upgrade from 9.2 dirdej SUSE / openSUSE 2 07-04-2005 03:10 PM
SUSE9.1 Internet Connection lswanson SUSE / openSUSE 2 05-27-2005 02:00 AM
sata+suse9.0=slow ? xxphdg Linux - Hardware 2 03-09-2004 04:27 PM
suse9.0 internet connection danger Linux - General 1 02-04-2004 10:18 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 12:19 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration