|
AICCU on Windows7 64 bit -> Works!
![[us]](/s/countries/us.gif) Shadow Hawkins on Friday, 30 January 2009 19:32:58
My tunnel is working with no issues so far, using the Wiki page
https://www.sixxs.net/wiki/Aiccu/Installing_on_Vista64
openvpn-2.1_rc15-install.exe has to be run in Vista compatibility mode, else it says it is only for Windows.
aiccu-2006-07-23-windows-gui installs ok but doesn't seem to get the tunnel going.
aiccu-2008-03-15-windows-console.exe works.
Apparently you still have to manually assign an IP6 address to the ethernet or wireless interface in order to get ipv6 DNS lookups in firefox or IE8
AICCU on Windows7 64 bit -> Works!
![[se]](/s/countries/se.gif) Carmen Sandiego on Thursday, 29 October 2009 18:16:30
My TAP driver installation fails in Win7 x64. I am using the Vista compatibility mode and i run the installer as Administrator. Setup hangs on TAP UPDATE for a couple minutes and then chokes on the driver installation. The error is "An error occurred installing the TAP device driver".
Any ideas please?
AICCU on Windows7 64 bit -> Works!
Shadow Hawkins on Thursday, 29 October 2009 18:35:12
There was a newer version of OpenVPN released since the first post..what version are you using?
AICCU on Windows7 64 bit -> Works!
Carmen Sandiego on Thursday, 29 October 2009 18:36:53
I have both r15, r19 and r20. I finally got r20 to install by disabling driver signing in Win7. The TAP-Win32 Adapter however says that the network cable is unplugged. Any ideas on that perhaps?
AICCU on Windows7 64 bit -> Works!
Carmen Sandiego on Thursday, 29 October 2009 18:38:22
Does the interface name matter on Windows platforms?
Here is my aiccu.conf:
# AICCU Configuration
# Login information
#username MS19381-RIPE
#password **********
# Interface names to use
# ipv6_interface is the name of the interface that will be used as a tunnel interface.
# On *BSD the ipv6_interface should be set to gifX (eg gif0) for proto-41 tunnels
# or tunX (eg tun0) for AYIYA tunnels.
ipv6_interface sixxs
# The tunnel_id to use
# (only required when there are multiple tunnels in the list)
#tunnel_id Txxxx
# Be verbose?
verbose false
# Daemonize?
daemonize true
# Automatic Login and Tunnel activation?
automatic true
# Require TLS?
# When set to true, if TLS is not supported on the server
# the TIC transaction will fail.
# When set to false, it will try a starttls, when that is
# not supported it will continue.
# In any case if AICCU is build with TLS support it will
# try to do a 'starttls' to the TIC server to see if that
# is supported.
requiretls false
AICCU on Windows7 64 bit -> Works!
The interface name is used to lookup an interface with such a name, if it exists, it is used, otherwise it finds the first Tun/TAP interface and uses that after renaming that interface to the interface name given.
AICCU on Windows7 64 bit -> Works!
Carmen Sandiego on Thursday, 29 October 2009 18:40:55
I can force the tap interface to be "always connected" in advanced props. That shows the static IP i entered in the connection if i type ipconfig in cmd. I can ping my own ip6 but not the pop thru ip6 :(
And yes, AICCU is enabled.
AICCU on Windows7 64 bit -> Works!
Check/show the output of AICCU in verbose & non-deamon mode... that should show what is going on.
AICCU on Windows7 64 bit -> Works!
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Saturday, 07 February 2009 18:02:54
Windows 7 32bit works fine too, tap32 installed fine. Console version works fine too, although I haven't got the GUI version to work yet.
AICCU on Windows7 64 bit -> Works!
GUI version won't work as it does not support the new TAP driver (there is a comment about this on the AICCU page).
|
![[ch]](/s/countries/ch.gif)
on Thursday, 29 October 2009 19:09:19
Posting is only allowed when you are