Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

Browsing very slow in iceweasel/firefox/konqueror/etc

Options
  • 31-01-2008 12:37am
    #1
    BrandonBlock
    Closed Accounts Posts: 570 ✭✭✭


    This happens with every site I go, using any web browser for example if I try www.boards.ie or www.breakingnews.ie it says "Looking up www.boards.ie" for about 15 seconds before loading, and even then it's a little slow. I'm using a netopia wireless router and on BT broadband. The ping results for those 2 sites show:

    # ping www.boards.ie
    PING www.boards.ie (89.234.66.107) 56(84) bytes of data.
    64 bytes from 89.234.66.107: icmp_seq=1 ttl=57 time=21.0 ms
    64 bytes from 89.234.66.107: icmp_seq=2 ttl=57 time=23.3 ms
    64 bytes from 89.234.66.107: icmp_seq=3 ttl=57 time=22.2 ms
    64 bytes from 89.234.66.107: icmp_seq=4 ttl=57 time=19.5 ms
    64 bytes from 89.234.66.107: icmp_seq=5 ttl=57 time=22.0 ms
    64 bytes from 89.234.66.107: icmp_seq=6 ttl=57 time=22.4 ms

    and..

    # ping www.breakingnews.ie
    PING www.breakingnews.ie (193.120.250.21) 56(84) bytes of data.
    64 bytes from cork1.wan.tch.ie (193.120.250.21): icmp_seq=1 ttl=119 time=27.6 ms
    64 bytes from cork1.wan.tch.ie (193.120.250.21): icmp_seq=2 ttl=119 time=27.0 ms
    64 bytes from cork1.wan.tch.ie (193.120.250.21): icmp_seq=3 ttl=119 time=27.1 ms
    64 bytes from cork1.wan.tch.ie (193.120.250.21): icmp_seq=4 ttl=119 time=27.5 ms
    64 bytes from cork1.wan.tch.ie (193.120.250.21): icmp_seq=5 ttl=119 time=23.8 ms

    so it's not the connection anyway. Any ideas? This happens in both debian and back|track linux. Thanks


Comments

  • Options
    #2
    sobriquet
    Closed Accounts Posts: 413 ✭✭sobriquet


    Had similar trouble ages ago with Firefox on Ubuntu, it turned out to be related to ipv6 support IIRC. Pretty common too as I recall. Piles of links out there about it, this might get you started.

    Try killing the ipv6 modules as per that link (though google for debian specific instructions just in case), and in firefox type about:config into the address bar, and set 'network.dns.disableIPv6' to true. (That it's happening in more than FF implies that that on its' own is probably not it though.)

    Other than that, it could be a DNS issue, if your /etc/resolv.conf is pointing to the gateway it could be stalling there - maybe set it to the ISPs one.


  • Options
    #3
    Khannie
    Registered Users Posts: 37,485 ✭✭✭✭Khannie


    yeah, was gonna say the ipv6 thing. Have a search in this forum for a fix in a previous thread. If that doesn't sort you, try switching to opendns.


  • Options
    #4
    niallb
    Registered Users Posts: 2,734 ✭✭✭niallb


    This can sometimes happen if you have a lot of dns entries in resolv.conf
    and they can't be reached - it will time out each one in turn.

    Try installing pdnsd to speed up dns requests.
    It's a must have for slow links, but it could probably really help you here too.

    In ubuntu, typing
    apt-get install pdnsd resolvconf
    will install it and have it use your normal dns servers as its source for addresses it doesn't already know.
    It's likely that the package names are the same in debian.

    Once they're installed, take a look at the file /etc/resolv.conf and make
    sure the line
    nameserver 127.0.0.1
    is the first one in it.


  • Options
    #5
    bman
    Registered Users Posts: 590 ✭✭✭bman


    sobriquet wrote: »
    in firefox type about:config into the address bar, and set 'network.dns.disableIPv6' to true.

    I'd imagine this will probably sort it out.


  • Options
    #6
    niallb
    Registered Users Posts: 2,734 ✭✭✭niallb


    Coincidentally, IPv6 went live today, so that particular issue may be on the way out. ;-)


  • Advertisement
  • Options
    #7
    bman
    Registered Users Posts: 590 ✭✭✭bman


    niallb wrote: »
    Coincidentally, IPv6 went live today, so that particular issue may be on the way out. ;-)

    What do you mean by this? Wasn't it already live? Have you got any links?


  • Options
    #8
    Capt'n Midnight
    Moderators, Recreation & Hobbies Moderators, Science, Health & Environment Moderators, Technology & Internet Moderators Posts: 91,679 Mod ✭✭✭✭Capt'n Midnight


    niallb wrote: »
    Coincidentally, IPv6 went live today, so that particular issue may be on the way out. ;-)

    http://www.iana.org/reports/root-aaaa-announcement.html
    oh my


Advertisement