Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 39 replies
  • Subscribers 8 subscribers
  • Views 64470 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 keeps down after DSL lines reconnects...

zaphod

i run several ipsec tunnel for years without any problems... all runs fine with 9.355-1


since the update to 9.402-7 all ipsec tunnels are down every morning.


i checked the ipsec-logs and found out that after my dsl-lines reconnect the tunnels will not come up again.

i have to turn them off and on and then all works....


anyone can help?



This thread was automatically locked due to age.
Parents
  • 0

    I spend several hours to the same problem

    Site 1: SG135 Appliance 9.402-7 (initiate connection)

    Site 2: UTM120 Appliance 9.402-7 (listen)

    Same Problem, Site-to-Site IPSec works with 9.355-1 and is broken every morning after DSL reconnect since update to 9.402-7

    Update to 9.402-7 was scheduled to night of 2016/05/11 to both appliances, one on 3:00 the second on 4:00 and since this update the VPN tunnel fails to come up again after reconnect  DSL line.

    It's not 100% possible to bring up the tunnel again with manunal switch off and on again the IPSec connection.

    Sometimes it helps to stop/start the IPSec connection, but sometimes it works, somtimes I have to reconnect 1-5 times and sometimes the connection doesn't come up again after 10 tries

    My way to bring back the tunnel: restart UTM every morning before working hours ...

    You can force the problem if you do a "reconnect" on the Interface (for me: ETH1 ADSL with static IP) which uses the IPSec Site-to-Site connection. After a reconnect the VPN tunnel stays down

    Workaround for me since serveral debug tries with the log file entries show no solutions for me:

    Site 1: go back to 9.355-1 (download 9.355-1 ISO , new install and use a  backup .abf to get to the former state)

    Since this rollback to 9.355-1 the IPSec Site-to-Site VPN tunnel works with no problems like the years before

    any help? 

Reply
  • 0

    I spend several hours to the same problem

    Site 1: SG135 Appliance 9.402-7 (initiate connection)

    Site 2: UTM120 Appliance 9.402-7 (listen)

    Same Problem, Site-to-Site IPSec works with 9.355-1 and is broken every morning after DSL reconnect since update to 9.402-7

    Update to 9.402-7 was scheduled to night of 2016/05/11 to both appliances, one on 3:00 the second on 4:00 and since this update the VPN tunnel fails to come up again after reconnect  DSL line.

    It's not 100% possible to bring up the tunnel again with manunal switch off and on again the IPSec connection.

    Sometimes it helps to stop/start the IPSec connection, but sometimes it works, somtimes I have to reconnect 1-5 times and sometimes the connection doesn't come up again after 10 tries

    My way to bring back the tunnel: restart UTM every morning before working hours ...

    You can force the problem if you do a "reconnect" on the Interface (for me: ETH1 ADSL with static IP) which uses the IPSec Site-to-Site connection. After a reconnect the VPN tunnel stays down

    Workaround for me since serveral debug tries with the log file entries show no solutions for me:

    Site 1: go back to 9.355-1 (download 9.355-1 ISO , new install and use a  backup .abf to get to the former state)

    Since this rollback to 9.355-1 the IPSec Site-to-Site VPN tunnel works with no problems like the years before

    any help? 

Children
No Data
Unfiltered HTML