Forum - Windows Console version broken? :: SixXS - IPv6 Deployment & Tunnel Broker

Windows Console version broken?

Carmen Sandiego on Tuesday, 23 January 2007 12:22:14

Hi, I experience strange problems with the Windows Console version of aiccu. It precisly send 1 heartbeat and stops. This happens after the update. Because the older version isn't allowed anymore: C:\Program Files\sixxs>aiccu-2006-07-23-windows-console.exe start aiccu.conf sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs .net)" sock_printf() : "client TIC/draft-00 AICCU/2006.07.23-console-win32 WinNT/5.1.2 600-SP2" sock_getline() : "200 Client Identity accepted" sock_printf() : "get unixtime" sock_getline() : "200 1169550694" sock_printf() : "username JR35-SIXXS" sock_getline() : "200 Choose your authentication challenge please" sock_printf() : "challenge md5" sock_getline() : "200 70d420b8aa1d15281664b99a6a6609e7" sock_printf() : "authenticate md5 19821c8f56e00cda5cc5d791561180b4" sock_getline() : "200 Succesfully logged in using md5 as JR35-SIXXS (Joshua Rubi ngh) from 212.178.112.58" sock_printf() : "tunnel show T8863" sock_getline() : "201 Showing tunnel information for T8863" sock_getline() : "TunnelId: T8863" sock_getline() : "Type: 6in4-heartbeat" sock_getline() : "IPv6 Endpoint: 2001:7b8:2ff:13e::2" sock_getline() : "IPv6 POP: 2001:7b8:2ff:13e::1" sock_getline() : "IPv6 PrefixLength: 64" sock_getline() : "Tunnel MTU: 1280" sock_getline() : "POP Id: nlede01" sock_getline() : "IPv4 Endpoint: heartbeat" sock_getline() : "IPv4 POP: 193.109.122.244" sock_getline() : "UserState: enabled" sock_getline() : "AdminState: enabled" sock_getline() : "Password: 2962242c2bbf52a688c6a2136c3952b3" sock_getline() : "Heartbeat_Interval: 60" sock_getline() : "202 Done" Succesfully retrieved tunnel information for T8863 sock_printf() : "QUIT Insomnia" Tunnel Information for T8863: POP Id : nlede01 IPv6 Local : 2001:7b8:2ff:13e::2/64 IPv6 Remote : 2001:7b8:2ff:13e::1/64 Tunnel Type : 6in4-heartbeat Adminstate : enabled Userstate : enabled heartbeat_socket() - IPv4 : 192.168.0.99 [HB] HEARTBEAT TUNNEL 2001:7b8:2ff:13e::2 sender 1169550710 150fc7182598056e427a b92aa357f561 It looks like that my internal ip is used? And I can't change that. When I use the GUI version, it is working. But you can't load the gui version automaticly because the settings aren't saved :( So I have to start manualy every day the heartbeat tunnel. And I have to fill in my login information. And choose the tunnel. That's why I used the console version. That is able to use a config file. The Gui isn't generating a new config file. That is also strange. So, if i missed something, please tell. I normaly work in Linux and that works much easer.... :P Best regards, Joshua Rubingh

Windows Console version broken?

Jeroen Massar SixXS Staff

on Tuesday, 23 January 2007 13:02:35

I experience strange problems with the Windows Console version of aiccu. It precisly send 1 heartbeat and stops. This happens after the update.

Which update? There hasn't been a new Windows version of AICCU since 2006-07-23. Can you be more precise? What is your configuration file? Also see the "Reporting Problems" list on the contact page.

Because the older version isn't allowed anymore:

If you where running anything before that you where still running a beta.

It looks like that my internal ip is used? And I can't change that.

And you don't need to change that as it gets NATted by your NAT.

When I use the GUI version, it is working.

There is no difference between the console version and the GUI version in code. Except for the UI.

But you can't load the gui version automaticly because

the settings aren't saved frown

Just use the menu option: AICCU Save Configuration and the first two hits in google(aiccu save configuration).

So I have to start manualy every day the heartbeat tunnel.

And I have to fill in my login information. And choose the tunnel.

I am very sure that I haven't entered any of my details for over 2 years now.

That's why I used the console version. That is able to use a config file.

As mentioned before, the GUI and the console version do exactly the same thing...

The Gui isn't generating a new config file. That is also strange.

See above. You need to hit the save button.

So, if i missed something, please tell. I normaly work in Linux and that

works much easer.... puh2

Then use Loenix ;)

Windows Console version broken?

Carmen Sandiego on Wednesday, 24 January 2007 22:57:42

Which update? There hasn't been a new Windows version of AICCU since 2006-07-23.

Can you be more precise? What is your configuration file? Also see the "Reporting Problems" list on the contact page.

Hmmm, now I am not so sure anymore about this.... O+ . It was always running. Probably a very old version. But let's forget it.

There is no difference between the console version and the GUI version in code.

Except for the UI.

Yes, as I also expected. But you never know for sure. That's why I found it strange. But it could have something to do with the older console version. So that's not the problem.

Just use the menu option: AICCU Save Configuration and the first two hits in google(aiccu save configuration).

Again... I am sorry. I should read more |:( |:( |:( I can't test right now, but will do tomorrow on my work. But this must be the solution.

Then use Loenix

At work we are developing on MS CMS and SQL Server etc. That doesn't work well on Linux :P I feel something lost..... at my desktop. But Jeroen thanks a lot for the eye opener!! Best regards, Joshua Rubingh

Windows Console version broken?

Shadow Hawkins on Saturday, 24 February 2007 15:53:50

> I experience strange problems with the Windows Console version of aiccu.

> It precisly send 1 heartbeat and stops. This happens after the update.

Which update? There hasn't been a new Windows version of AICCU since

2006-07-23. Can you be more precise? What is your configuration file? Also

see the "Reporting Problems" list on the contact page.

> Because the older version isn't allowed anymore:

If you where running anything before that you where still running a beta.

I have been running the AICCU client on a Windows XP box once in a while. When I tried again today, I got the message that I needed to upgrade. Download went smooth over IPv4 so no problems :-) Unfortunately the downloaded executable starts complaining as soon as I start it (something about a broken installation). Basicly I'll just blame windows, but the 'new' version isn't fail proof... (now I think of it, that's probably the reason why I have still been using the 'old' version). Regards, Bart

Windows Console version broken?

Jeroen Massar SixXS Staff

on Saturday, 24 February 2007 16:47:06

If something is not working as it is supposed to: Report a problem We can't fix what we don't know is broken. And yes, we do like to have a REAL problem report explaining what exactly the problem is etc. Otherwise we can't help fixing it. See Reporting Problems for more details.

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