Project

General

Profile

Actions

Bug #217

closed

Can't change pfSense default gateway

Added by Steve McGrath almost 15 years ago. Updated over 14 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Gateways
Target version:
Start date:
12/13/2009
Due date:
% Done:

100%

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

Description

Using the snapshot released 12/13/09, I cannot change the pfSense default gateway. The automatically created WAN interface gateway is the system default, though the UI doesn't show it marked default. It can't be deleted.

Adding a new gateway applying to the LAN interface, marked as default, does not actually change the routing table. The auto-created WAN gateway remains the default.

I've run into this because I don't have a WAN connection on my pfSense testing box, so I need it to route through a gateway on the LAN subnet for things like auto-updates.

Actions #1

Updated by Chris Buechler almost 15 years ago

  • Category set to Gateways
  • Target version set to 2.0
Actions #2

Updated by Ermal Luçi almost 15 years ago

  • Status changed from New to Feedback
Actions #3

Updated by Seth Mos almost 15 years ago

  • % Done changed from 0 to 100

I just rewrote a few parts of the gateway code on the backend and frontend. It should properly set the route now upon change. Not tested with dynamic gateways. I've only verified this with static gateways atm. since that is the only thing I have at hand.

Actions #4

Updated by Perry Mason almost 15 years ago

Sorry if it's a bit of topic but I tried to edit 2 dynamic gateways. It was not indicate witch one was the default and when i saved my changes to the monitor ip it didn't change it. I also notice after setting both wans to static ip and when back to gateways a apply button was shown.

Actions #5

Updated by Chris Buechler almost 15 years ago

  • Status changed from Feedback to Resolved

This particular issue looks to be resolved. There are different issues with dynamic gateways that need to be addressed, will open a new ticket on those later.

Actions #6

Updated by Chris Buechler over 14 years ago

  • Status changed from Resolved to New

This has regressed recently. Changing default from one statically configured gateway to another does not update the default gateway. No messages in the logs at all.

Actions #7

Updated by Chris Buechler over 14 years ago

  • Status changed from New to Resolved

false alarm actually, different problem

Actions

Also available in: Atom PDF