Bug #5495


System->Routing goes to System/ Gateways

Added by Jim Thompson over 8 years ago. Updated over 8 years ago.

Web Interface
Target version:
Start date:
Due date:
% Done:


Estimated time:
0.01 h
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:


remove extraneous space before 'G' in ' Gateways'

System->Routing should be renamed "Gateways"

Actions #1

Updated by Phillip Davis over 8 years ago

I have always wondered why the menu entry was called System->Routing but the destination page is System:Gateways and the tabs are "Gateways", "Routes", "Groups" (in all old versions of pfSense). The "Routes" tab is about routing. The other 2 are about gateways.

Actions #2

Updated by Jim Thompson over 8 years ago

  • Project changed from pfSense to Bootstrap
  • Category deleted (Gateways)
Actions #3

Updated by Chris Buechler over 8 years ago

It's not just gateways (though that's the first page it takes you to, and 2 of the 3), static routes is there as well. It's still all routing-related things, and there are tons of references to System>Routing all over the Internet and in our documentation that would break if it's renamed. 2290 Google results for "system > routing" alone, most of which are referencing the menu. Don't think it's a good idea to rename for reasons of breaking many, many references to it.

Ages ago, and in m0n0wall, it was System>Static Routes. The gateways and groups were combined into that, and renamed Routing, when the current gateways functionality was added in 2.0.

Actions #4

Updated by Anonymous over 8 years ago

  • Status changed from New to Assigned
  • Assignee changed from Anonymous to Jared Dillard

Menu has been changed to read "Gateways", but the spacing issue is a part of the lay ordered lists are styled.

Passing that over to JDillard.

Actions #5

Updated by Renato Botelho over 8 years ago

  • Project changed from Bootstrap to pfSense
  • Category set to Web Interface
Actions #6

Updated by Jim Pingle over 8 years ago

Gateways and routing are entwined -- you can't route without gateways and you must define gateways before routes. Gateways and gateway groups are used for static and policy routing. It lands on the gateways tab because that's the most commonly used function in the routing area. If someone was dropped right into the routing page they may miss adding a gateway, but calling it "Gateways" is equally confusing for someone looking for static routes.

I'd rather not rename it since calling it "Gateways" might make it seem like routing isn't under there either -- either way you're going to confuse somebody and at least keeping it as "Routing" would confuse a smaller set of people and also doesn't involve updating tons of documentation to follow the change.

Actions #7

Updated by Anonymous over 8 years ago

I understand. Perhaps you guys could debate this and give me a definitive answer :)

Actions #8

Updated by Chris Buechler over 8 years ago

  • Status changed from Assigned to Resolved
  • Assignee deleted (Jared Dillard)

this is good now, the thing jimt noted as wanting consistent was the breadcrumbs, which now match what they should.


Also available in: Atom PDF