problems reconnecting with avpn

[Ezz]

Hi,
Since this week I have troubles connecting to my ssh server using
almost VPN. I can connect once but after a disconnect I have to
reboot
before I am able to reconnect again.
I use a token pass to connect to my ssh server and I have configured
AVPN to ask for a password. It seems it goes wrong there. It tries to
authenticate but does not prompt me for a password. But when I enter
a
token from my tokengenerator in the password field and disable the
'ask' option it doesn't work either. Stopping / starting avpn server
does not fix the problem.
I did not have these problems before... AVPN sometimes did not want
to
reconnect but stopping / starting the server a couple of times would
always fix the problem untill now.
I added the logging below.
Any thoughts? I am using the lastest 1.6pre build on OS X 10.5.2
Thanks,
Eelco
---
LOG:02/29 11:57:25|SEVERE|
com.leapingbytes.almostvpn.server.ToolServer$1|Fail to start
profile :
TNO
STATE:02/29 11:57:25|fail|XXXX|Fail to authenticate
LOG:02/29 11:57:25|INFO|
com.leapingbytes.almostvpn.util.ssh.GanimedSSHSSession|Trying to
authenticate using password
LOG:02/29 11:57:25|INFO|
com.leapingbytes.almostvpn.util.ssh.GanimedSSHSSession|Starting
connection : xx...@XXX.XXX.XXX.XXX:22
STATE:02/29 11:57:25|starting|XXX|Connecting to
xxx...@xxx.xxxx.xxx.xxx:22
LOG:02/29 11:57:25|INFO|
com.leapingbytes.almostvpn.server.profile.item.BaseProfileItem|
setState : xxx...@xxx.xxxx.xxx.xxx:22(init) state = running
STATE:02/29 11:57:24|starting|XXX|addMachine d6371.ict.tno.nl
127.13.0.2 YES ->
LOG:02/29 11:57:24|INFO|
com.leapingbytes.almostvpn.server.profile.item.BaseProfileItem|
setState : ]addMachine xxx.xxx.xxx.xxx 127.13.0.2 YES[]deleteMachine
xxx.xxx.xxx.xxx[(init) state = running
LOG:02/29 11:57:24|INFO|
com.leapingbytes.almostvpn.util.ScriptRunner|
Script : addMachine xxx.xxx.xxx.xxx 127.13.0.2 YES
STATE:02/29 11:57:24|starting|XXXX|Creating Alias Host Name
xxx.xxx.xxx.xxx/127.13.0.2
LOG:02/29 11:57:24|INFO|
com.leapingbytes.almostvpn.server.profile.item.BaseProfileItem|
setState : xxx.xxx.xxx.xxx/127.13.0.2(init) state = running
LOG:02/29 11:57:24|INFO|
com.leapingbytes.almostvpn.server.profile.item.BaseProfileItem|
setState : ]fixLookupOrder[]restoreLookupOrder &&
deleteAllMachines[(stopped) state = running
LOG:02/29 11:57:24|INFO|
com.leapingbytes.almostvpn.util.ScriptRunner|
Script : fixLookupOrder
STATE:02/29 11:57:24|starting|XXX|User action
LOG:02/29 11:57:24|INFO|
com.leapingbytes.almostvpn.server.ToolServer|
Profile name : TNO
LOG:02/29 11:57:24|INFO|
com.leapingbytes.almostvpn.path.PathLocator|
resetEnv :

[Leaping Bytes, LLC]

Hi Eelco,
Could you please e-mail me almostvpn.log file. This file could be
found (depending on the way you have installed if) in
~/Library/Application Support/AlmostVPNPRO
or
/Library/Application Support/AlmostVPNPRO
NOTE: This file does not contain any passwords, but it does contain
real user names/host names/ip addresses. If you want, you can replace
this somewhat sensitive information with placebo.

Andrei Tchijov
Leaping Bytes, LLC

web: www.leapingbytes.com
email: and...@leapingbytes.com
AIM: leapingbytes
Google: leapin...@gmail.com
ICQ: 151229319

[Eelco Cramer]

Hi,

Thanks for you response. I attached the log file. This is the log from
starting avpn server, connecting to our ssh server (which fails) and
then stopping the server.

Thanks,
Eelco

[Eelco Cramer]

And now, after the connection failed (icon turns red) I am not able to
start the profile once more. Neither after stopping the profile or
after stopping avpn server. The icon turn orange and then red within a
second...

Regards,
Eelco

[Leaping Bytes, LLC]

Sorry for delay. Could you please e-mail me almostvpn.log once
again. I want to see what kind of problems you are getting with your
other profile.

[Eelco Cramer]

I'm not sure that I understand what you need. I have only 1 profile that I use for which I have send you the logfile.

Best regards,

Eelco

[Leaping Bytes, LLC]

Sorry I completely miss-read your previous reply. I still would like
to see almostvpn.log. From your description it looks like you got some
new kind of problem and I hope to see evidence of it in the log file.