Project

General

Profile

Bug #10264

Gateways created at the console do not apply the naming convention used in the GUI

Added by Steve Wheeler about 1 month ago. Updated about 1 month ago.

Status:
Feedback
Priority:
Normal
Category:
Console Menu
Target version:
Start date:
02/16/2020
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.4.x
Affected Architecture:
All

Description

When you create a gateway in the webgui by setting an interface as static and adding a new gateway it will, by default, create a gateway named 'WANGW' for example.

However if you do the same thing from the console menu the gateway created is named 'GW_WAN'.

That is not normally an issue if, for example, you are changing the WAN interface from DHCP to Static IP. If you are changing an existing static IP however you then create a second gateway.
If WANGW was set as default then the result is no default route as WANGW is now invalid.

Gateways created in the webgui and the console should use the same naming convention to avoid that.

Associated revisions

Revision b504ede5 (diff)
Added by Viktor Gurov about 1 month ago

Same gateway naming convention for the console and the WebGUI. Issue #10264

History

#1 Updated by Chris Linstruth about 1 month ago

  • Subject changed from Gatways created at the console do not apply the naming convention used in the GUI to Gateways created at the console do not apply the naming convention used in the GUI

#2 Updated by Viktor Gurov about 1 month ago

Fix (+ the same for IPv6 gateways):
https://github.com/pfsense/pfsense/pull/4196

#3 Updated by Renato Botelho about 1 month ago

  • Status changed from New to Feedback
  • Assignee set to Renato Botelho
  • % Done changed from 0 to 100

PR has been merged, thanks!

Also available in: Atom PDF