internet doesn't work in jaunty

Bug #311941 reported by Dominik Boehi
This bug report is a duplicate of:  Bug #313218: IPV6 causes slow internet access. Edit Remove
4
Affects Status Importance Assigned to Milestone
Ubuntu
Incomplete
Undecided
Unassigned

Bug Description

With jaunty, internet no longer works on my machine. I can download updates and ping sites on the internet, but browsing the web and IRC doesn't work any more. I believe it's an issue with IPv6, because when I disable it in firefox on the about:config page (network.dns.disableIPv6 = true), firefox works.

Revision history for this message
Noel J. Bergman (noeljb) wrote :

> I believe it's an issue with IPv6, because when I disable it in firefox
> on the about:config page (network.dns.disableIPv6 = true).

Are you saying that when you disable IPv6, firefox starts working for you?

You can disable IPv6 in firefox, and see also http://www.google.com/search?hl=en&q=disable+ipv6+ubuntu&btnG=Google+Search&aq=2&oq=disable+ipv for a variety of discussions on how to do it generally. Very simple, if you actually need to disable it.

Revision history for this message
Dominik Boehi (dboehi) wrote : Re: [Bug 311941] Re: internet doesn't work in jaunty

Yes, when I disable IPv6 in firefox, it works for me. Sorry when that wasn't
clear.

On Sun, Dec 28, 2008 at 17:26, Noel J. Bergman <email address hidden> wrote:

> > I believe it's an issue with IPv6, because when I disable it in firefox
> > on the about:config page (network.dns.disableIPv6 = true).
>
> Are you saying that when you disable IPv6, firefox starts working for
> you?
>
> You can disable IPv6 in firefox, and see also
>
> http://www.google.com/search?hl=en&q=disable+ipv6+ubuntu&btnG=Google+Search&aq=2&oq=disable+ipv
> for a variety of discussions on how to do it generally. Very simple, if
> you actually need to disable it.
>
> --
> internet doesn't work in jaunty
> https://bugs.launchpad.net/bugs/311941
> You received this bug notification because you are a direct subscriber
> of the bug.
>

description: updated
Revision history for this message
Noel J. Bergman (noeljb) wrote :

So is this a firefox only problem, or is Pidgin/mIRC or other also giving you issues? If the latter, again, you can disable IPv6 entirely if necessary.

Revision history for this message
Dominik Boehi (dboehi) wrote :

I have this problem with pidgin, XChat and firefox.

The strange thing is that everything works with IPv6 enabled in Intrepid, but in Jaunty it doesn't.

Revision history for this message
Noel J. Bergman (noeljb) wrote :

What happens if you disable IPv6 for Jaunty? Do they start working again?

Revision history for this message
Dominik Boehi (dboehi) wrote :

If I disable it (I tried everything in this post: http://ubuntuforums.org/showthread.php?t=6841), firefox works without disabling IPv6 in firefox, but the other applications don't work.

Revision history for this message
Noel J. Bergman (noeljb) wrote :

Dominik, they made a change to how IPv6 is loaded with Jaunty. See http://ubuntuforums.org/showthread.php?t=1026105.

What does

  $ ip a | grep inet6

show?

It might not be IPv6, but so far we haven't eliminated that as a prime suspect. If we do, we'll look elsewhere.

Revision history for this message
Dominik Boehi (dboehi) wrote :

$ ip a | grep inet6 shows nothing.

Revision history for this message
Noel J. Bergman (noeljb) wrote :

Still finding it interesting that firefox works as soon as you turn off IPv6, but that doesn't help with the others. Ok, on to the next phase of diagnostics ...

Are you hooked directly to the Internet or going through a LAN with a router? Would it e possible for you to connect directly to your cable/xDSL modem?

An odd request, but we run into this every year at a conference facility in Colorado ... could you please run

  sysctl -w net.ipv4.tcp_window_scaling=0

with root privs, and if that doesn't anything helpful? Next ... how network savvy are you, e.g., are you familiar with wireshark and how to use it?

You say that xChat fails. What does it say? If you do something like run wget or curl against a website, does that work?

Revision history for this message
Dominik Boehi (dboehi) wrote :

The computer is connected through a LAN with a router. It's not possible to connect it directly.

The command doesn't change anything.

When I use wget or curl, I get the error "unable to resolve host" or something similar. xChat just says unkown host. I have the wireshark output for a simple "wget launchpad.net" attached. The other applications produce exactly the same output.

Revision history for this message
Noel J. Bergman (noeljb) wrote :

Presumably, you disabled IPv6, but I still see queries for AAAA records in your wireshark capture, along with A record queries and A record responses. So I don't believe that you have successfully disabled IPv6. It looked like you were able to resolve launchpad.net to 91.189.90.211, but only for the A record type. What happens if you query with dig, manually?

Revision history for this message
Lupine (thelupine) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. I am marking this bug as Incomplete, as there is a request for more information.

Revision history for this message
Dominik Boehi (dboehi) wrote :

I marked this as a duplicate of #313218, since everything is working fine now and I think my issue was the same as in the other bug.

Revision history for this message
Ostien (ostiencf) wrote :

Are we sure this is a duplicate? the other bug this is attached to is only for SLOW internet access with ipv6 enabled. I cannot resolve at all in programs like pidgin unless I point right to the IP. This also affects apt-get. Firefox works when I disable ipv6 in about:config but does not work at all with it enabled.

This is also a new bug for me, and I have been using jaunty for a while now.

but again are we sure this is the same?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.