Project

General

Profile

Bug #8447

Cannot change Gateway in Firewall > Rules

Added by Yajasi Support about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Rules/NAT
Target version:
Start date:
04/08/2018
Due date:
% Done:

100%

Estimated time:
Affected Version:
All
Affected Architecture:
All

Description

Open any rule or create a new rule. In the Advanced options, the Gateway cannot be selected. This was working in 2.4.1.

Associated revisions

Revision ca0ca1c5 (diff)
Added by Steve Beaver about 1 year ago

Fixed #8447

(cherry picked from commit 1d523d1e4e7b16519ed3fd9dfb9e6b4dd84b4285)

Revision e3dfbd9c (diff)
Added by Steve Beaver about 1 year ago

Fixed #8447

(cherry picked from commit 1d523d1e4e7b16519ed3fd9dfb9e6b4dd84b4285)

History

#1 Updated by Chris Linstruth about 1 year ago

Are you sure you are not creating an IPv4+IPv6 rule? You cannot (and have never been able to) set a gateway on those. This is working fine for me on 2.4.3 so you should probably take this to the forum to hash out the details.

#2 Updated by Chris Linstruth about 1 year ago

Looking at it more there is something here, but it takes more steps to duplicate than you provided.

It works if you select IPv4 or IPv6 but as soon as you select IPv4+IPv6 and the field is grayed out, the gateway field is no longer selectable until you reload the page, even after setting it back to IPv4 or IPv6 only.

A workaround would be set everything except the gateway, save the rule, edit the rule again, edit the gateway, save, then apply.

Tested on current Firefox for Mac.

#3 Updated by Jim Pingle about 1 year ago

  • Category set to Rules/NAT
  • Status changed from New to Confirmed
  • Assignee set to Steve Beaver
  • Priority changed from Normal to Low
  • Target version set to 2.4.4
  • Affected Version set to All
  • Affected Architecture set to All

Confirmed here, too. Create a new rule, Gateway is changeable. Set Address Family to IPv4+IPv6, Gateway field is disabled. Change Address Family back to IPv4, Gateway field still disabled.

#4 Updated by Steve Beaver about 1 year ago

  • Status changed from Confirmed to Feedback

Should be fixed in the next snapshot. Please confirm here.

#5 Updated by Steve Beaver about 1 year ago

  • % Done changed from 0 to 100

#6 Updated by James Dekker about 1 year ago

Tested on latest CE snapshot gitsynced to master, works as expected. Editing an IPv4+IPv6 rule's gateway is possible now, it is not grayed out like it was before.

#7 Updated by Jim Pingle about 1 year ago

  • Status changed from Feedback to Resolved

Confirmed here as well. It works as it should now. Switching to IPv4+IPv6 disables the gateway edit control, then switching to either IPv4 or IPv6 enables and populates the gateway list again as expected. Switching back and forth between all the options yields the expected behavior.

#8 Updated by Jim Pingle about 1 year ago

  • Target version changed from 2.4.4 to 2.4.3-p1

Also available in: Atom PDF