Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 1 subscriber
  • Views 2177 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

[6.306] IPSec stops working after pppoe reconnect

Duke_01
The release notes 6.305 say that such a problem has been fixed, but in fact, while there have only been very few problems before 6.305, now IPSec stops working every second day on a DSL line that reconnects every 24 hours.

When attempting to establish a connection (with the Win XP native IPSec support), I don't even see any log entries in the Astaro's IPSec log. Pinging the DSL interface's (static!) IP-Address works fine though.

This is kind of a show-stopper. Please advise.

Thanks.


This thread was automatically locked due to age.
Parents
  • 0
    Any reason that you haven't up2dated to 6.311?  Maybe that problem is fixed in the latest version.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • 0 in reply to BrucekConvergent
    Wow, what a surprise, it still doesn't work correctly with 6.311. IPSec fails at least once per week for 24 hours (the DSL's connection timeout) and even an IPSec connection on a non-pppoe interface is not available then.
  • 0 in reply to Duke_01
    If you have support (can't tell if you are running a home user license or not), try starting a case with Astaro Support.  This was also an issue in Version 7, but it was recently fixed in an up2date.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • 0 in reply to BrucekConvergent
    Well, the support was indeed able to provide a fix/workaround for the issue which seems to be some kind of conflict or race condition between the self-monitoring and the ipsec start script. 

    Actually, it seems to be a well-known issue, but I couldn't find it listed anywhere. And honestly, I'd expect that such a serious bug which must have been introduced months ago in 6.305 or 6.306 should warrant a rather quick update with a fix.
  • 0 in reply to Duke_01
    Can you tell me what the fix/workaround is?

    Well, the bug ist listed. You can find it here: 

    Known_Issues-ASL-V6.txt

    Scroll down to ID3840. But the suggested workaround isn't suitable for me. Strictly speaking, it isn't suitable for anyone just to wait for the next failed reconnect and then start the tunnel manually.
  • 0 in reply to MaraDE
    Indeed it's listed in the Known Issues List. I guess I missed it because it is listed for 6.202 but I never had the problem before I've updated to 6.306. There were some sporadic problems like once a month or so, but since the update it has become unusable.

    > Can you tell me what the fix/workaround is?

    Check your PMs.
Reply
  • 0 in reply to MaraDE
    Indeed it's listed in the Known Issues List. I guess I missed it because it is listed for 6.202 but I never had the problem before I've updated to 6.306. There were some sporadic problems like once a month or so, but since the update it has become unusable.

    > Can you tell me what the fix/workaround is?

    Check your PMs.
Children
No Data
Cookie Information Banner