Ask Your Question

dustin's profile - activity

2018-04-05 03:19:35 -0500 received badge  Popular Question (source)
2015-01-05 15:26:20 -0500 commented answer Intel wireless chipset + ipv6 = no google

It's a good answer, just not to this problem (it's based on a misunderstanding as discussed in comments on the question)

2015-01-04 17:14:17 -0500 commented answer Intel wireless chipset + ipv6 = no google

Setting MTU and disabling IPv6 are workarounds, not solutions, so I haven't accepted this answer.

2015-01-04 17:13:55 -0500 commented question Intel wireless chipset + ipv6 = no google

Sorry, you misread my comment. There are three things going wrong here, all intermittent: host fails PTMUD (ignoring IMCPv6 type 2 packets); host fails to transmit 900+-byte packets (packets not received at the next hop), and host wireless firmware crashes. So basically a disconnected set of symptoms so far.

2015-01-03 19:44:59 -0500 commented question Intel wireless chipset + ipv6 = no google

Also, packets > 1280 bytes work fine with IPv4, so artificially limiting the MTU seems silly. But you're right that it's as effective a workaround as disabling IPv6.

2015-01-03 19:25:32 -0500 commented question Intel wireless chipset + ipv6 = no google

You're missing the point, though - even packets as small as 900 bytes are being dropped by the host (never arriving at the gateway).

I've just confirmed I'm using the latest firmware from Intel, so I think my next step is to report a crash at the kernel Bugzilla.

2015-01-03 18:19:35 -0500 commented question Intel wireless chipset + ipv6 = no google

No, because there might be network elements on down the line with a smaller MTU. I suspect that the ignored ICMPv6 messages are a symptom of a larger problem (presumably in the firmware, since it later crashed).

2015-01-03 15:36:42 -0500 commented question Intel wireless chipset + ipv6 = no google

@bitwiseoperator, I don't see a sysctl to disable IPv4. Hints?

2015-01-03 15:34:35 -0500 commented question Intel wireless chipset + ipv6 = no google

Well, I have a little more data. Running tcpdump to capture tra IPv6 traffic, I see that my host sometimes ignores the "Packet too big" ICMPv6 messages it gets. These are used to indicate that the sender should use a smaller packet size (1280 in my case, to fit in the GRE tunnel to Hurricane Electric).

I say "sometimes" because I managed to replicate this first with my browser, then with dd if=/dev/zero | nc -v arin.net 80 (sorry, arin.net!). Then the Intel firmware crashed and stopped sending any packets over a few hundred bytes. After a restart, I can't reproduce with the nc command anymore.