|
Win7 looses IPv6 connection after approx. 20min
![[de]](/s/countries/de.gif) Shadow Hawkins on Thursday, 21 February 2013 10:57:01
Hello,
a while ago I have set up my HB tunnel (T114438) via Fritzbox (7320) and it works fine for nearly every device (a mac, my android phone even on virtual mashines on the laptop I'm having trouuble with) BUT:
On my Asus K53, Win 7 Pro x64 I am loosing the IPv6 connectivity after approximatly 20mins from boot/connecting to wifi on. From that on I still do have IPv4 connectiivity but thats slightly less I wanted.
I really appreciate any help.
Lny
Win7 looses IPv6 connection after approx. 20min
Sounds like you might have multicast issues in your wireless network, as that coincides with a machine doing a Router Solicitation, it then getting a Advertisement back and using it for a while and then later that advertisement failing as the updates/renewals which are sent with multicast every once in a while did not reach it.
Check "ipconfig /all" in a cmd to see if you still have an address, that should confirm the above theory.
What wireless card do you have?
And if you can, check this with Wireshark, just filter on icmp6 and you should not see any RAs coming in after the initial one.
A "ipconfig /renew" in a cmd or start->run should btw bring connectivity back.
Win7 looses IPv6 connection after approx. 20min
Shadow Hawkins on Friday, 22 February 2013 01:12:35
ipconfig /all:
After IPv6 connectivity loss: I still have my (sixxs-prfix) address (+1 temporary)
wifi card:
Qualcomm Atheros AR9002WB-1NG Wireless Network Adapter (driver v10.0.0.221 - date: 22.11.2012)
wireshark:
Every 1-2mins there is a Solicitation (router -> me) followed by Advertisement reply (me -> router). After loss: no more messages like this (or better: no more which are dedicated for me).
ipconfig /renew:
fails (timeout). still no connectivity.
Hope that info is accurate enough.
Win7 looses IPv6 connection after approx. 20min
After IPv6 connectivity loss: I still have my (sixxs-prfix) address (+1 temporary)
That is interesting. But hold on, you thus have a sixxs-prefix and temporary, but do you also have an fe80::/10 address (Link Local) ?
Qualcomm Atheros AR9002WB-1NG Wireless Network Adapter (driver v10.0.0.221 - date: 22.11.2012)
Should be fine, anything in the last few years should (note the should ;) not have any issues with multicast.
And the Fritz!Box should be fine too. You do not have any other wireless devices in between those I guess?
Every 1-2mins there is a Solicitation (router -> me) followed by Advertisement reply (me -> router).
You mean Neighbour Discovery I assume; as Router Solicitation would be from "me -> router", and a Router Advertisement would be from "router -> me".
After loss: no more messages like this (or better: no more which are dedicated for me).
Multicast is not dedicated to you. It depends on the switching fabric (L2 / Ethernet, or in your case wifi) to deliver it.
What does wireshark show after this, as that would be quite interesting.
Also, do you have any special firewalling or anti-virus tools enabled? (There are a couple which completely mess up IPv6)
Win7 looses IPv6 connection after approx. 20min
Shadow Hawkins on Friday, 22 February 2013 12:46:49After IPv6 connectivity loss: I still have my (sixxs-prfix) address (+1 temporary)
That is interesting. But hold on, you thus have a sixxs-prefix and temporary, but do you also have an fe80::/10 address (Link Local) ?
Yes, I do have a link local (Verbindungslokale IPv6-Adresse) address (prefered, always). As far as I've seen before loss all addresses and a while after they are marked as prefered. After a while (maybe 5mins?) they get to depricated (sixxs, temp).
Qualcomm Atheros AR9002WB-1NG Wireless Network Adapter (driver v10.0.0.221 - date: 22.11.2012)
Should be fine, anything in the last few years should (note the should ;) not have any issues with multicast.
And the Fritz!Box should be fine too. You do not have any other wireless devices in between those I guess?
Other wireless devices in between? Like wifi repeater? No, I dont. Right now I'm the only one in the network.
Every 1-2mins there is a Solicitation (router -> me) followed by Advertisement reply (me -> router).
You mean Neighbour Discovery I assume; as Router Solicitation would be from "me -> router", and a Router Advertisement would be from "router -> me".
Well I might mixed it up with source/destination :).
After loss: no more messages like this (or better: no more which are dedicated for me).
Multicast is not dedicated to you. It depends on the switching fabric (L2 / Ethernet, or in your case wifi) to deliver it.
What does wireshark show after this, as that would be quite interesting.
I'm not so sure about the IPv6 address generation but I know the MAC addresses are involved so I would like to avoid posting the capture here. Is there any possibility to send it to you discretely?
Also, do you have any special firewalling or anti-virus tools enabled? (There are a couple which completely mess up IPv6)
The usual (not so restrictiv) Win7 firewall and VirusScan Enterprise + AntiSpyware Enterprise 8.8 (for free from my university - not cracked or so).
Win7 looses IPv6 connection after approx. 20min
After a while (maybe 5mins?) they get to depricated
Which means that the regular Router Advertisement was not received by your host.
I'm not so sure about the IPv6 address generation but I know the MAC addresses are involved so I would like to avoid posting the capture here. Is there any possibility to send it to you discretely?
As typically the EUI-64 portion of a link-local is involved you will always have that. But what concern do you have about the MAC address, it is not useable in any way. There are a lot more ways to identify a person than by MAC or EUI-64.
The usual (not so restrictiv) Win7 firewall and VirusScan Enterprise + AntiSpyware Enterprise 8.8 (for free from my university - not cracked or so).
There are a lot of "anti virus" tools which break IPv6 and just 'disabling' them does not make IPv6 work either, uninstalling is the only way to make them work.
The primary one that actually is useful and that does not break IPv6 is the one that comes with Windows, try it, it works great.
(As a side note: having a license from some place, even if valid or not, does not mean you are entitled to use that license in that location/purpose, especially university-style license tend to be bound to being a student/employee and using it on university related computers etc...)
Win7 looses IPv6 connection after approx. 20min
Shadow Hawkins on Friday, 22 February 2013 16:31:48
I was constantly v6-pinging google to see when exactly the connectivity gets lost. So here you are:
No. Time Source Destination Protocol Length Info
17427 12:54:17.572045000 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d 2a00:1450:4016:803::1018 ICMPv6 94 Echo (ping) request id=0x0001, seq=819
17428 12:54:17.627241000 2a00:1450:4016:803::1018 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d ICMPv6 94 Echo (ping) reply id=0x0001, seq=819
17452 12:54:18.572350000 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d 2a00:1450:4016:803::1018 ICMPv6 94 Echo (ping) request id=0x0001, seq=820
17453 12:54:18.627847000 2a00:1450:4016:803::1018 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d ICMPv6 94 Echo (ping) reply id=0x0001, seq=820
17489 12:54:23.192189000 fe80::4c21:3e43:f282:82b7 fe80::be05:43ff:fe9a:2b67 ICMPv6 86 Neighbor Solicitation for fe80::be05:43ff:fe9a:2b67 from 00:08:ca:3c:7d:bd
17490 12:54:23.193443000 fe80::be05:43ff:fe9a:2b67 fe80::4c21:3e43:f282:82b7 ICMPv6 78 Neighbor Advertisement fe80::be05:43ff:fe9a:2b67 (rtr, sol)
17611 12:54:34.028394000 fe80::be05:43ff:fe9a:2b67 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d ICMPv6 86 Neighbor Solicitation for 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d from bc:05:43:9a:2b:67
17612 12:54:34.028539000 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d fe80::be05:43ff:fe9a:2b67 ICMPv6 86 Neighbor Advertisement 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d (sol, ovr) is at 00:08:ca:3c:7d:bd
17982 12:55:25.741572000 fe80::be05:43ff:fe9a:2b67 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d ICMPv6 86 Neighbor Solicitation for 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d from bc:05:43:9a:2b:67
17983 12:55:25.742029000 fe80::4c21:3e43:f282:82b7 ff02::1:ff9a:2b67 ICMPv6 86 Neighbor Solicitation for fe80::be05:43ff:fe9a:2b67 from 00:08:ca:3c:7d:bd
17984 12:55:25.743630000 fe80::be05:43ff:fe9a:2b67 fe80::4c21:3e43:f282:82b7 ICMPv6 86 Neighbor Advertisement fe80::be05:43ff:fe9a:2b67 (rtr, sol, ovr) is at bc:05:43:9a:2b:67
17985 12:55:25.743742000 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d fe80::be05:43ff:fe9a:2b67 ICMPv6 86 Neighbor Advertisement 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d (sol, ovr) is at 00:08:ca:3c:7d:bd
18031 12:55:30.741947000 fe80::be05:43ff:fe9a:2b67 fe80::4c21:3e43:f282:82b7 ICMPv6 86 Neighbor Solicitation for fe80::4c21:3e43:f282:82b7 from bc:05:43:9a:2b:67
18032 12:55:30.742263000 fe80::4c21:3e43:f282:82b7 fe80::be05:43ff:fe9a:2b67 ICMPv6 86 Neighbor Advertisement fe80::4c21:3e43:f282:82b7 (sol, ovr) is at 00:08:ca:3c:7d:bd
18720 12:56:20.754836000 fe80::be05:43ff:fe9a:2b67 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d ICMPv6 86 Neighbor Solicitation for 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d from bc:05:43:9a:2b:67
18721 12:56:20.754976000 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d fe80::be05:43ff:fe9a:2b67 ICMPv6 86 Neighbor Advertisement 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d (sol, ovr) is at 00:08:ca:3c:7d:bd
18767 12:56:25.690241000 fe80::4c21:3e43:f282:82b7 fe80::be05:43ff:fe9a:2b67 ICMPv6 86 Neighbor Solicitation for fe80::be05:43ff:fe9a:2b67 from 00:08:ca:3c:7d:bd
18768 12:56:25.691414000 fe80::be05:43ff:fe9a:2b67 fe80::4c21:3e43:f282:82b7 ICMPv6 78 Neighbor Advertisement fe80::be05:43ff:fe9a:2b67 (rtr, sol)
18822 12:56:30.685513000 fe80::be05:43ff:fe9a:2b67 fe80::4c21:3e43:f282:82b7 ICMPv6 86 Neighbor Solicitation for fe80::4c21:3e43:f282:82b7 from bc:05:43:9a:2b:67
18823 12:56:30.685648000 fe80::4c21:3e43:f282:82b7 fe80::be05:43ff:fe9a:2b67 ICMPv6 86 Neighbor Advertisement fe80::4c21:3e43:f282:82b7 (sol, ovr) is at 00:08:ca:3c:7d:bd
19081 12:57:00.607229000 fe80::be05:43ff:fe9a:2b67 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d ICMPv6 86 Neighbor Solicitation for 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d from bc:05:43:9a:2b:67
19082 12:57:00.607369000 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d fe80::be05:43ff:fe9a:2b67 ICMPv6 86 Neighbor Advertisement 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d (sol, ovr) is at 00:08:ca:3c:7d:bd
19085 12:57:05.200852000 fe80::4c21:3e43:f282:82b7 fe80::be05:43ff:fe9a:2b67 ICMPv6 86 Neighbor Solicitation for fe80::be05:43ff:fe9a:2b67 from 00:08:ca:3c:7d:bd
19086 12:57:05.202194000 fe80::be05:43ff:fe9a:2b67 fe80::4c21:3e43:f282:82b7 ICMPv6 78 Neighbor Advertisement fe80::be05:43ff:fe9a:2b67 (rtr, sol)
19097 12:57:10.197950000 fe80::be05:43ff:fe9a:2b67 fe80::4c21:3e43:f282:82b7 ICMPv6 86 Neighbor Solicitation for fe80::4c21:3e43:f282:82b7 from bc:05:43:9a:2b:67
19098 12:57:10.198085000 fe80::4c21:3e43:f282:82b7 fe80::be05:43ff:fe9a:2b67 ICMPv6 86 Neighbor Advertisement fe80::4c21:3e43:f282:82b7 (sol, ovr) is at 00:08:ca:3c:7d:bd
19538 12:58:13.792121000 fe80::be05:43ff:fe9a:2b67 ff02::1:ffb0:967d ICMPv6 86 Neighbor Solicitation for 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d from bc:05:43:9a:2b:67
19539 12:58:13.792836000 fe80::4c21:3e43:f282:82b7 ff02::1:ff9a:2b67 ICMPv6 86 Neighbor Solicitation for fe80::be05:43ff:fe9a:2b67 from 00:08:ca:3c:7d:bd
19540 12:58:13.794375000 fe80::be05:43ff:fe9a:2b67 fe80::4c21:3e43:f282:82b7 ICMPv6 86 Neighbor Advertisement fe80::be05:43ff:fe9a:2b67 (rtr, sol, ovr) is at bc:05:43:9a:2b:67
19541 12:58:13.794493000 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d fe80::be05:43ff:fe9a:2b67 ICMPv6 86 Neighbor Advertisement 2001:6f8:900:8f4e:11be:b3d4:8bb0:967d (sol, ovr) is at 00:08:ca:3c:7d:bd
19583 12:58:18.792145000 fe80::be05:43ff:fe9a:2b67 fe80::4c21:3e43:f282:82b7 ICMPv6 86 Neighbor Solicitation for fe80::4c21:3e43:f282:82b7 from bc:05:43:9a:2b:67
19584 12:58:18.792461000 fe80::4c21:3e43:f282:82b7 fe80::be05:43ff:fe9a:2b67 ICMPv6 86 Neighbor Advertisement fe80::4c21:3e43:f282:82b7 (sol, ovr) is at 00:08:ca:3c:7d:bd
21803 12:59:01.850505000 fe80::be05:43ff:fe9a:2b67 ff02::1 ICMPv6 142 Router Advertisement from bc:05:43:9a:2b:67
35695 13:07:10.880656000 fe80::be05:43ff:fe9a:2b67 ff02::1 ICMPv6 142 Router Advertisement from bc:05:43:9a:2b:67
Win7 looses IPv6 connection after approx. 20min
I was constantly v6-pinging google
What does Google have to do with your local issue???
Please stop pinging random things there is enough of that already on the Internet.
For whatever reason (broken multicast or your host not accepting the RA) your host is 'forgetting' the IPv6 address. Definitely check that firewall of yours.
Win7 looses IPv6 connection after approx. 20min
Shadow Hawkins on Friday, 22 February 2013 19:02:22...to see when exactly the connectivity gets lost.
Ok then I will try to uninstall VirusScan and see if that will fix it. Thank you a lot! Will report if it has done the job.
Win7 looses IPv6 connection after approx. 20min
![[it]](/s/countries/it.gif) Shadow Hawkins on Wednesday, 27 February 2013 21:02:55
some years ago I had a similar problem.
My problem was that my access point or supplicant did not correctly rekey the wlan group key when using wpa2. Using wpa however worked (Pairwise keying is still aes, but I thing group keying falls back to tkip instead of ccmp).
The result was that multicast traffic did not work anymore. so ipv6 was practically dead since ndp did also stop working
Win7 looses IPv6 connection after approx. 20min
Shadow Hawkins on Thursday, 28 February 2013 18:31:22
Hello Jeroen, I tried your advice (deinstalling the anti-virus software) but it didnt make a change, nor Michael Saxl's fix did.
But I made a mistake in one of my last reports:
A "ipconfig /renew" in a cmd or start->run should btw bring connectivity back.
I said it didnt work but I was just "/renew"-ing; a "/renew6" worked and brought back the connectivity. This is good but just works as long as the usual connectivity persists.
I guess this is not much more enlightning as everything before but I wanted to tell you just in case it is.
Best wishes
Win7 looses IPv6 connection after approx. 20min
A 'ipconfig /renew6' will send a unicast Router Solicitation, as unicast apparently works in your network, then the connectivity will come back in deed.
But clearly multicast is broken in your network.
Win7 looses IPv6 connection after approx. 20min
Shadow Hawkins on Thursday, 28 February 2013 20:58:06
to rule that out:
can you prove that your windows firewall (in advanced view) has the role
router advertisements (ipv6 incomming) (in german called "Kernnetzwerk - Routerankndigung (ICMPv6 eingehend)")
enabled?
In the dump you send the last two line ARE router advertisements sent by your fritzbox, event some lines before proves that multicast indeed works
So it seams that your windows box ignores that packet.
Win7 looses IPv6 connection after approx. 20min
Shadow Hawkins on Friday, 01 March 2013 12:53:14
Gosh! Thats it!
But now I'm pretty embarrassed that its been firewall issues. But why did it work from beginning on for a while?
Now it seemes to be solved. I went to:
Systemsettings > Windows-Firewall > Extended Settings > Incomming Rules > Aktion > New Rule... >
Predefined > Core Network (?) > Next > mark: Core Network - Router Advertisment (ICMPv6 incomming) > Next >
Allow (connection) > Finish
To allow incomming v6 router advertisments.
Thank you again Jeroen and Michael! Thanks a lot.
Win7 looses IPv6 connection after approx. 20min
Shadow Hawkins on Friday, 01 March 2013 18:21:14
The reason why it worked after booting is because in that case windows sends a RS to ff02::2 (all routers). the answer is sent directly to your pc, so that counts for a outgoing "connection". windows by default always allows outgoing connections if not explicitly denied by outgoing rules
after that, every packet sent to ff02::1 (all hosts) counts as a incomming "connection", which must be explicitly be allowd by default
|
![[ch]](/s/countries/ch.gif)
on Thursday, 21 February 2013 15:22:11
Posting is only allowed when you are