|
AICCU not running window setupscript
![[sg]](/s/countries/sg.gif) Shadow Hawkins on Tuesday, 17 April 2012 08:51:25
I run window
**aiccu-2012-02-02-windows-console.exe **
but have below syntax error,please advise how to solve it ? or how to modify above script to correct this error?
syntax error is **aiccu_os_exec("netsh firewall set icmpsetting aiccu enable all")**
see below quote for detail
**quote**
Ok.
Trying to connect to TIC server tic.sixxs.net
sock_getline() : "200 SixXS TIC Service on nlams04.sixxs.net ready (http://www.s
ixxs.net)"
sock_printf() : "client TIC/draft-00 AICCU/2012.02.02-win32 - WinNT/5.1.2600-SP
3"
sock_getline() : "200 Client Identity accepted"
sock_printf() : "get unixtime"
sock_getline() : "200 1334626082"
sock_printf() : "username syx3-SIXXS"
sock_getline() : "200 syx3-SIXXS choose your authentication challenge please"
sock_printf() : "challenge md5"
sock_getline() : "200 6db214aa23f362cc3a9a67b6f477d319"
sock_printf() : "authenticate md5 8c1b0c81760a8f30652d6a23f26a012b"
sock_getline() : "200 Successfully logged in using md5 as SYX3-SIXXS (Sapphire Y
U)"
sock_printf() : "tunnel show T91542"
sock_getline() : "201 Showing tunnel information for T91542"
sock_getline() : "TunnelId: T91542"
sock_getline() : "Type: ayiya"
sock_getline() : "IPv6 Endpoint: 2604:8800:100:150::2"
sock_getline() : "IPv6 POP: 2604:8800:100:150::1"
sock_getline() : "IPv6 PrefixLength: 64"
sock_getline() : "Tunnel MTU: 1280"
sock_getline() : "Tunnel Name: My First Tunnel"
sock_getline() : "POP Id: uschi03"
sock_getline() : "IPv4 Endpoint: ayiya"
sock_getline() : "IPv4 POP: 38.229.76.3"
sock_getline() : "UserState: enabled"
sock_getline() : "AdminState: enabled"
sock_getline() : "Password: xxxxxx"
sock_getline() : "Heartbeat_Interval: 60"
sock_getline() : "202 Done"
Successfully retrieved tunnel information for T91542
sock_printf() : "QUIT Running Down That Hill"
Tunnel Information for T91542:
PoP Id : uschi03
IPv6 Local : 2604:8800:100:150::2/64
IPv6 Remote : 2604:8800:100:150::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
aiccu_setup(2604:8800:100:150::2, first)
Flag: HAS_IFHEAD not present
Flag: NEED_IFHEAD not present
Error opening registry key: SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E32
5-11CE-BFC1-08002BE10318}\0000\ComponentId (t3)
Using configured interface aiccu
[tun-start] Trying \\.\Global\{119E4CCE-2FAD-4F60-AF84-3654A578D0D1}.tap
[tun-start] This is Wireless Network Connection 2, not the one we want
[tun-start] Trying \\.\Global\{1756C305-B297-4449-A6C7-DBFE9083F8EA}.tap
[tun-start] This is aiccu, the one we want
[tun-start] Trying \\.\Global\{1E819B00-6195-4109-955F-47AAD1700050}.tap
[tun-start] This is Wireless Network Connection 3, not the one we want
[tun-start] Trying \\.\Global\{24CA7B3C-2033-4F3B-AA47-1B0525A30222}.tap
[tun-start] This is Wireless Network Connection, not the one we want
[tun-start] Trying \\.\Global\{5170E58B-FEB8-48D5-913D-82F5E8778C8C}.tap
[tun-start] This is aiccu, the one we want
[tun-start] TAP-Win32 Driver Version 9.6
aiccu_setup(2604:8800:100:150::2, other)
Flag: HAS_IFHEAD not present
Flag: NEED_IFHEAD not present
aiccu_os_exec("netsh int ipv6 6to4 set state disabled")
Ok.
aiccu_os_exec("netsh int ipv6 set teredo disable")
Ok.
aiccu_os_exec("netsh int ipv6 isatap set state state=disabled")
Ok.
aiccu_os_exec("netsh set interface "aiccu" mtu=1280")
The following command was not found: set interface aiccu mtu=1280.
aiccu_os_exec("netsh int ipv6 add address "aiccu" 2604:8800:100:150::2")
Ok.
aiccu_os_exec("netsh int ipv6 add route 2604:8800:100:150::2/64 aiccu")
Ok.
aiccu_os_exec("netsh int ipv6 add route 0::/0 aiccu 2604:8800:100:150::1 publish
=yes")
Ok.
aiccu_os_exec("netsh firewall set icmpsetting aiccu enable all")
The syntax supplied for this command is not valid. Check help for the correct sy
ntax.
set icmpsetting
[ type = ] 2-5|8-9|11-13|17|ALL
[ [ mode = ] ENABLE|DISABLE
[ profile = ] CURRENT|DOMAIN|STANDARD|ALL
[ interface = ] name ]
Sets firewall ICMP configuration.
Parameters:
type - ICMP type.
2 - Allow outbound packet too big.
3 - Allow outbound destination unreachable.
4 - Allow outbound source quench.
5 - Allow redirect.
8 - Allow inbound echo request.
9 - Allow inbound router request.
11 - Allow outbound time exceeded.
12 - Allow outbound parameter problem.
13 - Allow inbound timestamp request.
17 - Allow inbound mask request.
ALL - All types.
mode - ICMP mode (optional).
ENABLE - Allow through firewall (default).
DISABLE - Do not allow through firewall.
profile - Configuration profile (optional).
CURRENT - Current profile (default).
DOMAIN - Domain profile.
STANDARD - Standard profile.
ALL - All profiles.
interface - Interface name (optional).
Remarks: 'profile' and 'interface' may not be specified together.
'type' 2 and 'interface' may not be specified together.
Examples:
set icmpsetting 8
set icmpsetting 8 ENABLE
set icmpsetting ALL DISABLE
set icmpsetting type = 8
set icmpsetting type = 8 mode = ENABLE
set icmpsetting type = ALL mode = DISABLE
[AYIYA-start] : Anything in Anything (draft-02)
[AYIYA-tun->tundev] : (Socket to TUN) started
**quote***
AICCU not running window setupscript
Shadow Hawkins on Thursday, 10 May 2012 05:31:06
waiting..... but no answer, too difficult, now change my question.
Because I face above problem, I cannot connect Aiccu with Windows vista software.
May I ask, now Windows Vista users( members), How you set up your computers to connect your Aiccu. Because follow aiccu way, I face above problem and cannot work.
Need your comments.
AICCU not running window setupscript
Because I face above problem, I cannot connect Aiccu with Windows vista software.
The version you ran the above on (5.1.2600-SP3) is Windows XP SP3, not Windows Vista.
If the tun/tap driver is properly installed (which it seems to be) it should just work.
Unless local firewalls or policies do not allow it to work of course.
AICCU not running window setupscript
Shadow Hawkins on Thursday, 24 May 2012 09:11:59
Thanks your comments,
Actually, I run it in Window Vista, but how come the software's result is ""windows XP SP3"". I also do not know??
I will try to re-install window Vista then see what is the new result.
AICCU not running window setupscript
Did you maybe enable compatibility mode?
http://en.wikipedia.org/wiki/List_of_Microsoft_Windows_versions
Windows XP Professional, for business and power users (Version number: NT 5.1.2600)
Windows Vista Enterprise (Microsoft Windows NT 6.0.6000.0)
So it clearly is a XP that it is acting as, XP compatibility mode would explain that. One can enable/disable that per program.
AICCU not running window setupscript
sock_printf() : "client TIC/draft-00 AICCU/2012.02.02-win32 - WinNT/5.1.2600-SP 3"
This indicates a Windows XP SP3.
aiccu_os_exec("netsh set interface "aiccu" mtu=1280") The following command was not found: set interface aiccu mtu=1280.
This command does exist on Windows XP SP3, at least according to documentation and what I verified on my installation. Thus that is odd.
aiccu_os_exec("netsh firewall set icmpsetting aiccu enable all")
This should also exist on SP3 as that is the format used between XP SP2 and Windows 7 (inclusive).
AICCU not running window setupscript
![[ee]](/s/countries/ee.gif) Shadow Hawkins on Thursday, 18 October 2012 07:21:59This should also exist on SP3 as that is the format used between XP SP2 and Windows 7 (inclusive).
Running WinNT/6.0.6002-SP2 over here and that same error is present for me. No compatility mode involved. Shouldn't it be
netsh firewall set icmpsetting type=ALL mode=ENABLE
AICCU not running window setupscript
![[se]](/s/countries/se.gif) Shadow Hawkins on Thursday, 08 November 2012 16:33:09
Yes indeed Henrik, that's one command that netsh will accept. But none of the two versions suggested in the FAQ are.
I can understand the frustration that the hard working SixXS team is facing when Microsoft changes the netsh commands from one SP to another, but will your suggested command really open up the *IPv6* channel for pings?
I've spent almost a week trying to get IPv6 pings accepted by my old XP/SP2 to no avail. IPv4 pings worked immediately.
Finally I tested 'netsh firewall reset' and then I ran the autogenerated script for WinXP/SP2 and all went well until the firewall command, that obviously wasn't recognised. I then ran the simple command that you suggested (without the last part that is default).
Suddenly it all worked again. I've had my tunnel working for almost four years, but suddenly had to change IPv4, and that's when my problems started.
AICCU not running window setupscript
Shadow Hawkins on Thursday, 08 November 2012 16:52:45
Oh, and BTW, anyone trying to navigate through the labyrints of 'netsh' might want to test 'netsh dump > netsh.dump' and then edit the resulting file. You'll most certainly find a lot of old crap there that you haven't used for years. Windows is notorious for not cleaning up after you've uninstalled stuff.
After you've edited the file to your liking, simply run 'netsh exec netsh.dump' and your setting will be clear and nice.
You might want to keep the original netsh.dump though, in case you edit out to much from the file. That way you can always restore your computer to its original state.
AICCU not running window setupscript
MSDN is the best resource for this, that combined with a google(<search terms> site:msdn.microsoft.com) that is.
Next to that, actual testing and hoping that the commands do not change from under you.
AICCU not running window setupscript
Shouldn't it be netsh firewall set icmpsetting type=ALL mode=ENABLE
No, as that enables IPv4 ICMP on all interfaces. AICCU only enables ICMPv6 on the tunnel interface.
AICCU not running window setupscript
Shadow Hawkins on Thursday, 08 November 2012 16:57:15
As I suspected then. It seems like it's impossible to open up IPv6 pinging via netsh on XP/SP2. I've tried all different commands I can think of, but can not get any to be accepted.
And yes, I know I should upgrade to a more modern version of Windows, but this old XP/SP2 has served me well for more than a decade now, and I fear the time when I have to replace it... :(
AICCU not running window setupscript
Nothing wrong with XP, the only thing though is that "production quality IPv6" was only enabled as per SP3, and that is just a download away, and when you are there you will also want to pick up the hundreds of other hotfixes that have been released since then to add a bit of security to your machine.
netsh firewall set icmpsetting interface=aiccu type=all mode=enable
should definitely do the trick btw.
AICCU not running window setupscript
Shadow Hawkins on Thursday, 08 November 2012 19:28:03
I'm sure that SP3 would add a lot of features, but ir also forces me to install Windows Genuine Advantage. A "feature" that I can do without.
As the saying goes: "if it ain't broke don't try to fix it". And, as I said earlier, my XP/SP2 box has been running flawlessly for more than a decade now.
Surely there must be *some* way to enable pings via ipv6 even on an XP/SP2 box?
AICCU not running window setupscript
I'm sure that SP3 would add a lot of features, but ir also forces me to install Windows Genuine Advantage. A "feature" that I can do without.
I really do hope that you are not admitting that you are using an illegal version of Windows.....
As the saying goes: "if it ain't broke don't try to fix it".
If you are running XP SP2, your machine is very broken, hence the existence of SP3 and all the hotfixes following that, mostly security related.
Surely there must be *some* way to enable pings via ipv6 even on an XP/SP2 box?
As IPv6 is only feature complete and production ready in SP3, upgrading it to SP3 will do it.
AICCU not running window setupscript
Shadow Hawkins on Friday, 09 November 2012 04:08:25
Of course I'm not running an illegal version of Windows. It came with the computer. But that doesn't mean I like having a spy program from MS installed.
Well, I did install SP3, and now my machine is really broken. I lost all my network settings, and all the firewall settings. And 'netsh exec' doesn't work with a dump file from the SP2 intallation -- as usual a lot of commands seem to have changed.
And no, the netsh firewall command still doesn't work. Now it reports that it can't find the interface -- even though I can see that it gets installed (via the autogenerated script). But that might have something to do with all the other errors I got after "upgrading" to SP3. :(
AICCU not running window setupscript
But that doesn't mean I like having a spy program from MS installed.
WGA only runs when you install new components and/or update and it only transfers a hash of the components installed in your host, nothing else.
There is nothing 'spy' about this. If you do consider it 'spy' then you might want to disable all programs that access the Internet as most applications will do some magic "update" every once in a while and transfer a lot more details than you would care, and of course don't forget to not use any social network, have adblockers, disconnect.me and fully disable javascript, otherwise you'll freak out about what kind of information is being collected about you, your computer and your behaviour.
Using the Internet makes you the product, not what you are using....
Well, I did install SP3, and now my machine is really broken. I lost all my network settings, and all the firewall settings. And 'netsh exec' doesn't work with a dump file from the SP2 intallation -- as usual a lot of commands seem to have changed.
I am really wondering why you even are messing around with trying to restore settings from a previous version of Windows, that is just asking for problems.
And no, the netsh firewall command still doesn't work. Now it reports that it can't find the interface
Likely because you have messed up the system by trying to run old commands, which most very likely have destroyed a lot of settings that one should not be touching and/or causing incompatibilities.
even though I can see that it gets installed (via the autogenerated script)
Which script?
But that might have something to do with all the other errors I got after "upgrading" to SP3.
If you do all kind of customisations and try to modify things that you are not supposed to touch then yes, expect lots of problems...
AICCU not running window setupscript
Shadow Hawkins on Friday, 09 November 2012 16:24:30
Well, you have your opinion about WGA -- I and a lot of others have another. Let's just leave it with that.
The reason I desperately needed to get all my settings back was that this is my main router, and for ten years now I've fine tuned it to forward ports to various servers, sharing folders, connecting my VOiP router, and so on on my network. But let's leave that too for now.
The script I've been talking about all the time is the one I get when clicking "You can also download scripts for: Windows 2000, Windows XP/2003(.Net), Solaris" on my tunnel page.
But the bottom line is: none of the netsh firewall suggestions found all over this place does work. The only one that works is Henrik's suggestion above.
And, BTW, if someone wants to enter it manually it can be shortened to:
netsh f s i t=a
Obviously it does enable pings even for IPv6. At least it seems to do so on my installation. YMMV...
AICCU not running window setupscript
Shadow Hawkins on Thursday, 08 November 2012 19:31:09
And no, 'netsh firewall set icmpsetting interface=aiccu type=all mode=enable' gives the same responce as all the other suggestions here -- i.e. it displays a screenful of options that it accepts.
AICCU not running window setupscript
What is the output that it gives? As that is the syntax for SP2 + SP3.
For XP < SP2 it would be:
netsh firewall set adapter aiccu icmp all=enable
AICCU not running window setupscript
Shadow Hawkins on Friday, 09 November 2012 17:17:37
Sorry if I haven't been clear enough about this (I thought that my having to change IP would be a give-away), but I have a 6in4 static tunnel (T19721).
The output from this command:
netsh i ipv6 sh i > ipv6.shw
...gives this result (sorry for the Swedish):
Aktivt tillstnd lses...
Idx Mtt MTU Tillstnd Namn
--- ---- ----- ------------ -----
10 1 1280 Ansluten SixXS
6 2 1280 Frnkopplad Teredo Tunneling Pseudo-Interface
5 0 1500 Ansluten ADSL
4 0 1500 Ansluten Kllaren
3 1 1280 Ansluten 6to4 Tunneling Pseudo-Interface
2 1 1280 Ansluten Automatic Tunneling Pseudo-Interface
1 0 1500 Ansluten Loopback Pseudo-Interface
As you can see I don't have an 'aiccu' interface, only a SixXS ditto.
Well, for the moment all my three tunnels seem to be working properly (and I'm really, really grateful for the service that you guys provide for free, make no mistake about it!), so I will stop pestering you with comments that you seem to think are stupid. :(
After all it's not your fault that MS still hasn't managed to create a proper GUI for 'netsh'...
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 22 May 2012 17:36:12
Posting is only allowed when you are