Project

General

Profile

Actions
Copy link

Bug #8447

closed

Cannot change Gateway in Firewall > Rules

Added by Yajasi Support about 6 years ago. Updated almost 6 years ago.

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

100%

Estimated time:
Plus Target Version:
Release Notes:
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.

Actions
Copy link
 #1

Updated by Chris Linstruth about 6 years 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.

Actions
Copy link
 #2

Updated by Chris Linstruth about 6 years 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.

Actions
Copy link
 #3

Updated by Jim Pingle about 6 years ago

  • Category set to Rules / NAT
  • Status changed from New to Confirmed
  • Assignee set to Anonymous
  • Priority changed from Normal to Low
  • Target version set to 2.4.4
  • Affected Version set to All
  • Affected Architecture All added
  • Affected Architecture deleted ()

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.

Actions
Copy link
 #4

Updated by Anonymous about 6 years ago

  • Status changed from Confirmed to Feedback

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

Actions
Copy link
 #5

Updated by Anonymous about 6 years ago

  • % Done changed from 0 to 100
Actions
Copy link
 #6

Updated by Anonymous about 6 years 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.

Actions
Copy link
 #7

Updated by Jim Pingle about 6 years 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.

Actions
Copy link
 #8

Updated by Jim Pingle almost 6 years ago

  • Target version changed from 2.4.4 to 2.4.3-p1
Actions
Copy link

Also available in: Atom PDF