Hello,

When I try to enable one of my IPSec policies, it say's "peer not set" and won't allow it.

If I click "add" button to make a new policy, Winbox crashes.

Ive looked at next stable release info and there's nothing that looks like it would address this.

I only have one peer, and this is just site-site VPN from RB at my home to RB router at WISP site.

I use these policies to allow me LAN access to all the VLANs on my WISP network from home, on a certain SSID/VLAN on my home network. It works great and is super handy.

The screenshot shows the message I get when I try to enable one of the existing policies that has been off for ages.

Thank you in advance,

Jimmy

Make sure you have latest WinBox, perhaps RouterOS version may have something to do with it as well, but you didn't tell us either.

Oh sure, sorry. I'm on a mac using Winbox 3.16 and ROS is 6.48.5

I though if it was a Winbox error i'd not have got the error message, as this looks to be a legit error. The Winbox locking up could be of course - I assumed it was ROS issue seeing as enabling one of the existing rules gets an error.

Please help me, experts. I need to enable this rule so I don't need any port forwards to access radios on this VLAN : )

Thank you from New Zealand. The land of sheep and pies.

Jimmy

I don't know about Mac, we're not exactly friends, but latest regular WinBox is 3.37. If you're able to update to that, it could probably help with crashing.

As for the error, don't just enable the policy, open it first and see if there's peer set. I assume it's not, so fix it first and then it should be better.