SixXS::Sunset 2017-06-06

IPv6 not working & not pingable.
[si] Shadow Hawkins on Friday, 29 October 2010 19:01:55
Hello! My IPv6 is not working. I am using OS: Windows XP. I have dynamic ip address. I choosed AICCU to function. I have downloaded & installed: aiccu-windows-gui aiccu-console-current Installation Package (Both 32-bit and 64-bit TAP driver included) from (http://openvpn.se/download.html) I have done the process showed and explain on page: https://www.sixxs.net/faq/connectivity/?faq=ossetup&os=windows It says: On XP it can be installed quite easily by typing "netsh interface ipv6 install" in the command prompt. For Windows XP/2003/.Net and up, according to Updating IPv6.exe Commands to Netsh Commands this should be: C:\> netsh interface etc.etc.etcetc.etc - I've done all this. Strange is that this does not work for me: C:\> netsh firewall set icmpsetting SixXS enable all ---------------------------------------------------- I have configured correctly SixXS AICCU. I have portforwarded all the ports correctly (TCP 3874, UDP 3740, UDP 5072...) I have also set the DMZ host to my local ip at home and still when I ping6 my ipv6 host it says the following: icmp_seq=1 Destination unreachable: No route I've read the whole FAQ and I have checked everything as far AS I KNOW. I would like to ask politely to any help possible. Thank you & kind regards, Barbara
IPv6 not working & not pingable.
[si] Shadow Hawkins on Friday, 29 October 2010 19:49:30
my v6: 2001:15c0:65ff:4bf::2
IPv6 not working & not pingable.
[ch] Jeroen Massar SixXS Staff on Friday, 29 October 2010 20:27:10
I have done the process showed and explain on page:
https://www.sixxs.net/faq/connectivity/?faq=ossetup&os=windows
That is for static protocol 41 tunnels. Not for AYIYA, this is written at the top of the page with an exclamation mark in front of it.
I have configured correctly SixXS AICCU. I have portforwarded all the ports correctly [..]
There is no need at all to do any port forwards ever. Where did you read this? What one does need to forward is protocol 41, but only when one uses that. Which is not case for AYIYA, which you are using.
I've read the whole FAQ and I have checked everything as far AS I KNOW.
If you read the FAQ you would be showing the output of AICCU (the console version, as the GUI version does not have it). As you have now configured a static tunnel, I suggest that you do a "netsh interface ipv6 reset" first though to remove at least parts of the brokenness.
IPv6 not working & not pingable.
[si] Shadow Hawkins on Friday, 29 October 2010 20:54:49
Jeroen Massar - Thank you for your fast reply. I wanted to say I did everything for everything just because of precaution. I have done the command netsh interface ipv6 reset Now I removed the dmz host, because I am using aiccu under type ayiya. But all in all the first time I did everything right and I didn't get any ping. http://yfrog.com/5tsixxsaiccup When I start the aiccu console only a black window open and then nothing. Can you explain me please for what more or when should I use the aiccu console? I think you really understood me as a lazy women trying to get the easy way to do the ipv6, but I really spent today mostly reading the sixxs page... Maybe I tried too much at once. Thank you for your answer, Barbara.
IPv6 not working & not pingable.
[si] Shadow Hawkins on Friday, 29 October 2010 21:02:42
In addition. I have reset now my computer. I have started the aiccu console and then the gui it looks at tunel is working correctly. But when I ping it, I get the following: PING 2001:15c0:65ff:4bf::2(2001:15c0:65ff:4bf::2) 56 data bytes From 2001:15c0:ffff:7::2 icmp_seq=1 Destination unreachable: No route From 2001:15c0:ffff:7::2 icmp_seq=2 Destination unreachable: No route From 2001:15c0:ffff:7::2 icmp_seq=3 Destination unreachable: No route From 2001:15c0:ffff:7::2 icmp_seq=4 Destination unreachable: No route
IPv6 not working & not pingable.
[ch] Jeroen Massar SixXS Staff on Friday, 29 October 2010 21:23:19
The GUI edition does not work with the new TUN/TAP Drivers as stated on the AICCU page. You will have to use the console edition. First create a configuration file, which is something that the GUI edition can do and most likely did now. Then start the console version and show the output here. It is advised to set the verbosity enabled using the configuration file.
IPv6 not working & not pingable.
[si] Shadow Hawkins on Friday, 29 October 2010 21:29:30
I'm very sorry if this is a silly question. But how can the GUI make me a configuration file? I'm going to search the sixxs page about the configuration file, because currently I dont have enough imagination what I should insert in conf file, how it should look and how will the aiccu console took the data form the conf file...
IPv6 not working & not pingable.
[ch] Jeroen Massar SixXS Staff on Friday, 29 October 2010 22:02:12
I'm very sorry if this is a silly question. But how can the GUI make me a configuration file?
Well, when you get as far as what you showed in the screenshot, it will have made it and stored it in C:\Windows\aiccu.conf (That is the windows installation directory which might differ). There is an example on the AICCU page. (and yes, we are very aware, it is far from ideal that one has to jump so many hoops, it works for most people though and unfortunately time is too limited to fix it, but maybe maybe soon we might get to that again...)
IPv6 not working & not pingable.
[si] Shadow Hawkins on Friday, 29 October 2010 23:42:51
I have found the config. Don't know howto load it with the console. Tried even a lame thing as run as it did not work. It's late today so I will try to smash my head with it tomorow:) Thanks for all for today:)
IPv6 not working & not pingable.
[si] Shadow Hawkins on Saturday, 30 October 2010 16:36:35
If I understand everything correctly now. I should leave the aiccu.conf file in c:\windows and I should run aiccu console trough cmd from the folder where aiccu is located. Then it should work... Is there anything else neccessary? thank you again for your time and patience with me. Kind regards, Barbara
IPv6 not working & not pingable.
[ch] Jeroen Massar SixXS Staff on Saturday, 30 October 2010 16:43:27
That should be it. One can set "verbose true" in the configuration file so that AICCU provides a lot more details to what it is doing, which should help you solve your problem, and otherwise provide the output of the tool here.
IPv6 not working & not pingable.
[si] Shadow Hawkins on Sunday, 31 October 2010 09:20:56
I've started the windows console and I got this error: C:\Documents and Settings\Barbara Pesek>aiccu-2008-03-15-windows-console start Succesfully retrieved tunnel information for T44457 [warning] Couldn't open registry key: SYSTEM\CurrentControlSet\Control\Class\{4D 36E972-E325-11CE-BFC1-08002BE10318}\0000\ComponentId (t2/2 vs 0/1700 vs 1) [warning] [NULL] {40F9FF21-6D50-44D3-9304-AF0D21A72936} [warning] *** Adapter with GUID {40F9FF21-6D50-44D3-9304-AF0D21A72936} doesn't h ave a link from the control panel [warning] [NULL] {3BE1F638-E88A-4326-A651-3F4C1356A6AD} [warning] *** Adapter with GUID {3BE1F638-E88A-4326-A651-3F4C1356A6AD} doesn't h ave a link from the control panel [warning] Found = 0, Count = 0 [error] [tun-start] TAP-Win32 Adapter not configured properly... I know installed the tap-win32 driver, but looks like it's not correctly configured. I went to see the manual on this page: http://openvpn.net/index.php/open-source/documentation/howto.html#windows I know everything is installed. I did the following in the config, I might have done something wrong...: # Edit this file, and save to a .ovpn extension # so that OpenVPN will activate it when run # as a service. # Change 'myremote' to be your remote host, # or comment out to enter a listening # server mode. remote 82.149.3.79 # Uncomment this line to use a different # port number than the default of 1194. ; port 1194 # Choose one of three protocols supported by # OpenVPN. If left commented out, defaults # to udp. ; proto [tcp-client] # You must specify one of two possible network # protocols, 'dev tap' or 'dev tun' to be used # on both sides of the connection. 'tap' creates # a VPN using the ethernet protocol while 'tun' # uses the IP protocol. You must use 'tap' # if you are ethernet bridging or want to route # broadcasts. 'tun' is somewhat more efficient # but requires configuration of client software # to not depend on broadcasts. Some platforms # such as Solaris, OpenBSD, and Mac OS X only # support 'tun' interfaces, so if you are # connecting to such a platform, you must also # use a 'tun' interface on the Windows side. Enable dev tap # This is a 'dev tap' ifconfig that creates # a virtual ethernet subnet. # 10.3.0.1 is the local VPN IP address # and 255.255.255.0 is the VPN subnet. # Only define this option for 'dev tap'. ifconfig 82.149.3.79 255.255.255.0 # If you have fragmentation issues or misconfigured # routers in the path which block Path MTU discovery, # lower the TCP MSS and internally fragment non-TCP # protocols. ;fragment 1300 ;mssfix # If you have set up more than one TAP-Win32 adapter # on your system, you must refer to it by name. ;dev-node my-tap # You can generate a static OpenVPN key # by selecting the Generate Key option # in the start menu. # # You can also generate key.txt manually # with the following command: # openvpn --genkey --secret key.txt # # key must match on both ends of the connection, # so you should generate it on one machine and # copy it to the other over a secure medium. # Place key.txt in the same directory as this # config file. secret key.txt # If this section is enabled and "myremote" # above is a dynamic DNS name (i.e. dyndns.org), # OpenVPN will dynamically "follow" the IP # address of "myremote" if it changes. ; ping-restart 60 ; ping-timer-rem ; persist-tun ; persist-key ; resolv-retry 86400 # keep-alive ping ping 10 # enable LZO compression comp-lzo # moderate verbosity verb 4 mute 10 The first line says: and save to a .ovpn extension I just saved this into config file in OVP.... Maybe the problem trully is my incompability, I'm very sorry to bother that much, but I decided that ipv6 will be my university project and I need to work this trough...
IPv6 not working & not pingable.
[si] Shadow Hawkins on Sunday, 31 October 2010 09:36:03
I removed these lines: # You can also generate key.txt manually # with the following command: # openvpn --genkey --secret key.txt # # key must match on both ends of the connection, # so you should generate it on one machine and # copy it to the other over a secure medium. # Place key.txt in the same directory as this # config file. secret key.txt And I could insert now the config into openvpn client but it seems it doesn't connect and when I do aiccu test it still says tap drivers is not configured correctly...
IPv6 not working & not pingable.
[ch] Jeroen Massar SixXS Staff on Sunday, 31 October 2010 11:03:19
You do not have to do anything with the OpenVPN configuration; the only part of OpenVPN that is being used is the TUN/TAP driver... Obviously, as AICCU is telling, the installation of the TUN/TAP driver is broken. It seems you didn't use the version of TUN/TAP as linked from the AICCU page. Download that one, unpack it, go to either the 32-bit or 64-bit directory based on your OS; then run the deltapall.bat, then reboot. After the reboot go back to that directory and once run the addtap.bat. Now that is done you should have a functional TUN/TAP driver installed. Now just run AICCU again and all should be fine, the output will tell you at least.
IPv6 not working & not pingable.
[si] Shadow Hawkins on Sunday, 31 October 2010 13:02:44
You saved my life. I did the aiccu test and everything seems fine now. The only thing that went wrong in the test is that I cannot tracert simbx01.sixxs.net does now works. Sledenje smeri do simbx01.sixxs.net [212.18.63.73] prek najve 30 preskokov: 1 * * * Iztekla se je asovna omejitev za zahtevo. 2 * * * Iztekla se je asovna omejitev za zahtevo. 3 * * * Iztekla se je asovna omejitev za zahtevo. 4 * * * Iztekla se je asovna omejitev za zahtevo. 5 * * * Iztekla se je asovna omejitev za zahtevo. 6 10 ms 12 ms 11 ms simbx01.sixxs.net [212.18.63.73] Sledenje konano. But all in all the IPv6 works now. The 'calc' on your page shows I'm connecting trough my ipv6 address. You really have helped so much and if I look at my posts up I screwed manny things and now I when I have done it it seems so damn easy that I seem a bit stupid to myself. Jeroen Massar you really helped a lot. If it is possible I am willing to contribute you a small donation for your time. Kind regards, Barbara

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker