Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 1 subscriber
  • Views 816 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ipsec vpn problems, astaro stops responding

cpm
can't sort this one out, been dogging me for a couple of years. Longer maybe.

I'll get a ticket 'Can't connect to vpn' from my remote access users.
I go in, and turn off ipsec vpn, then turn it back on again. Then it's good
for a few days, a week, maybe longer, until it isn't again.

As more and more folks start using remote access, this becomes more and more
of a problem.

Currently running 6.314, but it's been a problem for a long time.

client side, OSX ipsec l2tp on versions 10.2,10.3,10.4,10.5 and windows XP SP2/SP3

that I can't easily determine who is logged in to the vpn is a headache,
that I can't easily determine the vpn access history is a headache.

Clues?


This thread was automatically locked due to age.
Parents
  • 0
    I'm using PSK. 

    I've no doubt that Bruce knows what he's talking about.
    However, it's a non-trivial task.
  • 0 in reply to cpm
    I would definitely be ready to reimage and go back to V6.314, but I think you can avoid making a weekend of it.  If you aren't quarantining email, then it should be really pretty straightforward to reimage with 7.4, import the 6.314 backup and set up the L2TP over IPSec.  What else on the upgrade checklist do you see that you will need to tickle after moving to V7?
Reply
  • 0 in reply to cpm
    I would definitely be ready to reimage and go back to V6.314, but I think you can avoid making a weekend of it.  If you aren't quarantining email, then it should be really pretty straightforward to reimage with 7.4, import the 6.314 backup and set up the L2TP over IPSec.  What else on the upgrade checklist do you see that you will need to tickle after moving to V7?
Children
No Data