Donnerstag, 24. Mai 2012 22:25
I've set up teredo tunneling on one machine successfully, but another 2 machines, both running windows 7 ultimate x32, are giving me the same issue.
The static route required for the tunnel, ::/0, simply disappears off the active routes list after a few seconds. If I run a continuous ping or browse ipv6 websites, the route remains active but as soon as I let it idle, it drops in about one minute and i lose all ipv6 connectivity. It's still listed under persistent, but not active. If I tell netsh to add the route again, it will say it already exists AND spring the route back to life, for another few seconds, before it dies again.
This is extremely frustrating. WHY won't the persistant route remain active?
Things I've tried:
-explicitly used persistent parameter
-removed and re-added the route
-bound the route to the adapter instead of the IP
-made teredo qualified via gpedit.msc so it doesn't shut off
In both netsh's show route and route print, I can see the ::/0 route at the top of the list. If I keep polling it, I can see it stays there for a few seconds then just disappears, and then it only shows up in persistent routes.
Where can I begin to troubleshoot this nonsense?
UPDATE: I've made some disturbing progress. If I add say, ::/1, the route stays active indefinetly. If I add ::/0 and ::/1 at the same time, ::/0 will die after a few seconds but ::/1 remains active for whatever period of time. Why are permanently active routes discriminating against ::/0?
- Bearbeitet Searinox Navras Freitag, 25. Mai 2012 09:39
Freitag, 25. Mai 2012 10:45
What is output from
route print -6
Freitag, 25. Mai 2012 10:49
10...00 0c 29 6e 08 96 ......Intel(R) PRO/1000 MT Network Connection
19...00 ff 98 f4 f6 0f ......Comodo Unite Adapter
12...7a 79 05 96 52 ac ......Hamachi Network Interface
1...........................Software Loopback Interface 1
17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
11...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
15...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
IPv6 Route Table
If Metric Network Destination Gateway
11 306 ::/1 On-link
1 306 ::1/128 On-link
11 58 2001::/32 On-link
11 306 2001:0:5ef5:79fd:3427:3ffa:faf3:a2c8/128
10 266 2002:c0a8:ff02::/48 On-link
10 266 2002:c0a8:ff02::/128 On-link
10 266 fe80::/64 On-link
11 306 fe80::/64 On-link
11 306 fe80::3427:3ffa:faf3:a2c8/128
10 266 fe80::f8e4:71b9:9ac:fbfe/128
1 306 ff00::/8 On-link
11 306 ff00::/8 On-link
10 266 ff00::/8 On-link
If Metric Network Destination Gateway
0 4294967295 ::/0 On-link
0 4294967295 ::/1 On-link
The ::/1 path is there for referrence. Notice how under Persistent routes both ::/0 and ::/1 show up, but under Active only ::/1 appears. ::/0 will also appear under Active for a while, then it will disappear. NO OTHER custom route, other than ::/0, will disappear.
Tell me something... since I can make permanent /1 ranges, would it be the same if, instead of "::/0", I was to add "::/1" and "8000::/1" instead? I think I can route the full ipv6 range through 2x /1 ranges instead of 1x /0 range, and it will work.
- Bearbeitet Searinox Navras Freitag, 25. Mai 2012 11:11
Dienstag, 29. Mai 2012 10:17
Thanks for your reply.
For clarify the issue, I would like to know the questions below:
1. Did you change the IPV6 address when reproducing the problem?
2. Which entry disappear from the Active route-table?
3. Please show me the two screenshots for letting me know which entry does not exist any more after a few seconds.
In my opinion, there can be some possible cause for you to try:
1. Check if you have any task script running on the machine to delete them.
2. Please reboot the machine under the Safe Mode with networking, then try again to see if the entry will disappear.
I will try some tests locally and report to you later.
Thanks for your time.
Dienstag, 29. Mai 2012 14:35
1. I set an ipv6 fixed address on the adapter with internet which I have not changed in any test.
2. The entry that disappears is listed up there, it is the ::/0 entry that you can see in persistent routes. It normally appears right up there at the top of active routes, then disappears after a while.
3. I hope point 2 clarified that.
1. I do not have, to my knowledge, any scripts that do that, unless you know of any builtin tasks that might be doing it.
2. I am not going do do that, reason below.
I have decided to leave the issue as it is, with ::/1 and 8000::/1 instead of the ::/0. It is working fine and remains active, just like the ::/0 was supposed to be, and I have no desire to bother with the matter further. Thank you for your help though.
- Als Antwort markiert Searinox Navras Dienstag, 29. Mai 2012 17:07