Project

General

Profile

Actions

Bug #16709

closed

Cannot disable IPsec Advanced Settings tab option for Strict Interface Binding

Added by Georgiy Tyutyunnik 23 days ago. Updated 21 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
IPsec
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
26.03
Release Notes:
Default
Affected Version:
2.7.2
Affected Architecture:

Description

Specific config can cause the parameter "strict interface binding" to be unchangeable.

Actions #1

Updated by Georgiy Tyutyunnik 23 days ago

  • File config-4slgb-mer-nfw20.4slgroup.local-20260213134553.xml added
Actions #3

Updated by Georgiy Tyutyunnik 23 days ago

  • Private changed from No to Yes
Actions #4

Updated by Jim Pingle 23 days ago

  • File deleted (config-4slgb-mer-nfw20.4slgroup.local-20260213134553.xml)
Actions #5

Updated by Jim Pingle 23 days ago

  • Subject changed from (IPSEC) STORNSWAN strict interface binding option will not disable to Cannot disable IPsec Advanced Settings tab option for Strict Interface Binding
  • Category changed from Web Interface to IPsec
  • Target version set to 2.9.0
  • Private changed from Yes to No
  • Plus Target Version set to 26.07

This came up not long ago and was discussed internally but I didn't see another Redmine for it. Steve found that:

You can disable strict interface binding as long as Enable bypass for LAN interface IP is enabled.
And once both those have been added and removed it works OK

Actions #6

Updated by Georgiy Tyutyunnik 22 days ago

it doesn't in my lab

Actions #7

Updated by Marcos M 22 days ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

Applied in changeset commit:a31b2cc5adb69a88e8402275702fa444803897cc.

Actions #8

Updated by Marcos M 22 days ago

  • Assignee set to Marcos M
  • Plus Target Version changed from 26.07 to 26.03
  • Affected Version set to 2.7.2
Actions #9

Updated by Georgiy Tyutyunnik 21 days ago

  • Status changed from Feedback to Resolved

tested, patch fixes the issue
tested on:
25.11.1-RELEASE (amd64)
built on Mon Jan 19 17:25:00 UTC 2026
FreeBSD 16.0-CURRENT

Actions

Also available in: Atom PDF