Closed Hecatron closed 3 years ago
I've put some config below, although I tried to mask out any private data like passwords etc
200
200
This issue has been automatically timed-out (after 180 days of inactivity).
For more information about the policies for this repository, please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.
If someone wants to step up and work on this issue, just let us know, so we can reopen the issue and assign an owner to it.
Important notices Before you add a new report, we ask you kindly to acknowledge the following:
[X] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[X] I have searched the existing issues and I'm convinced that mine is new.
I think I've discovered a bug associated with VPN site to Site tunnels when the box is rebooted and there are several Phase 2 entries in the tunnel for multiple subnets
So I have a VPN Tunnel setup with a Cisco ASA Firewall on one end. And a AWS OpnSense Image on the other
With multiple subnets routed over (multiple Phase 2 entries) (Cisco side) 192.168.21.0/24 -> (OpnSense Side) 10.26.0.0/16 (Cisco side) 192.168.21.0/24 -> (OpnSense Side) 10.22.0.0/16
So If I reboot the opnsense box then try and access something from the cisco side, the opnsense logs tend to show something along the lines of
If I then go into VPN -> IPSec -> Status Overview Then click on the circle symbol at the top (which I think restarts the vpn service) Everything then works fine
I'm guessing the VPN Service is starting too soon after a reboot which is why it may manually need a restart of the vpn service just to get things going properly
I'm planning on moving across to routed IPSec so I'm hoping that will fix it.
Environment
OPNsense 20.7.2-amd64 AMD EPYC 7571 (2 cores) (AWS Image)