DNS packets getting mangled over Wi-Fi connection

DNS Bug was not the file I intended to attach, sorry. The file I wanted to send is:

Malform Packet

This Wireshark output was captured during WiFi connect, then Ping www.google.com.

I'd like to say it's this cheap router that I bought, but DNS resolution works fine on my iMac, so it should work. I'm running Karmic.

I have a Dlink DI-604

My /etc/resolv.conf reads like this

domain dlink
search dlink
nameserver 192.168.0.1
nameserver 208.67.222.222
nameserver 208.67.220.220

and now I can use Karmic just fine now.

@Neskie : By including OpenDNS servers into your router's config, you have effectively bypassed this bug. Remove the OpenDNS server entries by updating your router and you'll see the issue is very much apparent on Karmic, but is NOT apparent on Macs, Windows or earlier versions of Ubuntu. The issue might be resolver, might be IPv6, might be Network Manager, but it was definitely introduced in Karmic and remains an active bug today.

If anyone on the Network Manager team would like to investigate this issue more fully, I'm pretty handy with Wireshark/tcpdump traces too and I'm happy to back up any of the.scarecrows initial reports/traces, if it would be useful to do so.

It seems to be only a problem with lower end Dlink routers, because I've been at a place with a DIR-655 and it doesn't have this problem. I'd like to see this get resolved as well, and can help work on this.

Well guess what...I DO have a DIR 655 and the problem persists. So this needs to get fixed.

Can I also say that I have this problem as well. Using an Acer Aspire 7003 laptop with an Atheros AR2413 wifi card connecting via BT Voyager 2110 wireless router. Using either Ubuntu Karmic or Lucid Beta. Previous versions of Ubuntu never gave a problem.

One very crude way around, I have found, is to exit Ubuntu, boot into windows xp (which never fails to connect), exit windows and then boot back into Ubuntu. This NEVER fails to work.

Sure, it's annoying and is not the end of the world, but anyone new ot Ubuntu is going to be utterly stumped. It needs fixing, please.

Why is this bug being completely ignored?

We are encouraged to participate and have offered to help with the solution but not a word from the developers. Its very discouraging to meet with complete silence. LTS released complete with this bug, ho hum.

Is this fixed in Precise?

I don't see how NM can be responsible for the fact that malformed and incorrect DNS packets get returned.

Frame 25

    Queries
        ntp.ubuntu.com: type AAAA, class IN
            Name: ntp.ubuntu.com
            Type: AAAA (IPv6 address)
            Class: IN (0x0001)
[Malformed Packet: DNS]
    [Expert Info (Error/Malformed): Malformed Packet (Exception occurred)]
        [Message: Malformed Packet (Exception occurred)]
        [Severity level: Error]
        [Group: Malformed]

Frame 27

    Answers
        ntp.ubuntu.com: type A, class IN, addr 1.0.0.0
            Name: ntp.ubuntu.com
            Type: A (Host address)
            Class: IN (0x0001)
            Time to live: 2 hours, 46 minutes, 40 seconds
            Data length: 4
            Addr: 1.0.0.0

If you can figure out that some component of Ubuntu is responsible, please set the status back to New and reassign the report to the relevant package.