SixXS::Sunset 2017-06-06

Windows 7 x64 - running as a service - times out starting
[us] Shadow Hawkins on Friday, 30 July 2010 04:15:23
I successfully installed everything, and can run 'aiccu start' and be in ipV6-land. I installed aiccu as a service and set it to automatically start with Windows. And here is the problem - 'net start aiccu' starts to do its thing. If I watch Control Panel\Network and Internet\Network Connections, the sixxs adapter goes to Enabled for a second, and then Identifying..., which is where it stays for 30 seconds or so, when Windows gives up on it as taking too long. Of course the same thing happens in the Services control panel. Any suggestions would be most welcome! Thanks, Daniel
Windows 7 x64 - running as a service - times out starting
[ch] Jeroen Massar SixXS Staff on Friday, 30 July 2010 08:00:17
The 'enabled' and 'identifying' are because you have still enabled IPv4 on the tunnel interface. There is nothing to be identified, but that is about how long it takes for a DHCP request to go through. Most likely though you start aiccu too early, before there is a proper network connection and thus it fails to start up. Also, running it as a service (however you have configured that) most likely means that it is going to auto-restart, which will just mean that you will get ratelimited by the TIC server and thus it won't work then either.
Windows 7 x64 - running as a service - times out starting
[us] Shadow Hawkins on Friday, 30 July 2010 15:29:06
This is with starting aiccu after the machine has been up and running for quite a while. If I do it with 'aiccu start', it takes a few minutes but starts. So I see two possibilites: 1) can I disable IPv4 on the tunnel interface without any problems, or 2) can I increase the timeout value that the Windows service system uses before it decides a service isn't responding?
Windows 7 x64 - running as a service - times out starting
[ch] Jeroen Massar SixXS Staff on Friday, 30 July 2010 18:09:56
1) can I disable IPv4 on the tunnel interface without any problems
Absolutely, there is no need at all to have IPv4 on that interface. (It is very tricky to disable though, which is why AICCU does not do it...)
2) can I increase the timeout value that the Windows service system
uses before it decides a service isn't responding?
As AICCU does not have native service support (at least not in the public versions, the one in SVN which I still still still have to push out has), you most likely are using something like srvany and thus those timeouts have absolutely no effect. What you could do though is delay starting the srvany, either by putting a sleep in the script and is possible adding a dependency on a network ready signal, but I don't know if the latter is possible.
Windows 7 x64 - running as a service - times out starting
[us] Shadow Hawkins on Friday, 30 July 2010 21:18:00
Hmmm. I unchecked IPv4 in the sixxs adapter, but it still times out starting. Can I try out the SVN version of AICCU? Or is it not stable enough yet? I'd hate to think I'm at an impasse with IPv6 and Windows 7 already :( Thanks for your input and assistance. Daniel
Windows 7 x64 - running as a service - times out starting
[ch] Jeroen Massar SixXS Staff on Monday, 02 August 2010 11:00:47
We only release fully tested versions as it will otherwise affect too many people and we will be truly swamped by too much email. As for your Windows7 issue, just run the client from the console instead of from some kind of service, much better idea. Next to that, check your firewall software if you have any as that might also cause all kinds of strangeness, and lastly: wireshark + details details details.

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

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