Project

General

Profile

Actions

Bug #1137

closed

Global reply-to disable checkbox missing from 2.0

Added by Jim Pingle almost 11 years ago. Updated almost 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Rules / NAT
Target version:
Start date:
12/27/2010
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:
All

Description

In 1.2.3 there is a checkbox to disable reply-to on WAN rules under System > Advanced. The same option and functionality are not present on 2.0, which could lead to a regression on upgrade for users of this feature. We do have the option to disable this one a per-rule basis, but not a master switch.

We should either add this option, or detect the option in the upgrade code and set the per-rule reply-to option on all WAN-type interface rules.

Actions #1

Updated by Chris Buechler almost 11 years ago

  • Status changed from New to Feedback
Actions #2

Updated by Alex Kennedy almost 11 years ago

Feedback: Fixed or Works-for-me
Recommendation: Close ticket or request details

Findings:
Running RC1 build "Sat Feb 26 16:00:14 EST 2011" (i386 arch).

The "Reply-To" option exists under System (menu) > Advanced (menu) > Firewall / NAT (tab) > Network Address Translation (heading) > Disable reply-to (heading) as "Disable reply-to on WAN rules". I am not sure if this was an oversight by end user or recently implemented. The discription is written under the option as follows:

With Multi-WAN you generally want to ensure traffic leaves the same interface it arrives on, hence reply-to is added automatically by default.When using bridging, you must disable this behavior if the WAN gateway IP is different from the gateway IP of the hosts behind the bridged interface.

Let me know if you have any questions or need further information.

Actions #3

Updated by Chris Buechler almost 11 years ago

  • Status changed from Feedback to Resolved

confirmed works, thanks

Actions

Also available in: Atom PDF