Project

General

Profile

Actions

Bug #1410

closed

pfSense remains without default route

Added by Ermal Luçi over 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Multi-WAN
Target version:
Start date:
04/04/2011
Due date:
% Done:

0%

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

Description

A setup with multiple WANs can losse its default route when its gateway is marked as down from apinger.
This results in a system non-functional for some services running on pfSense itself and that are not handled by a PBR.

A fix was committed https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/1d60ed9bb4901c5b85813d0dab32630e8a135d41
to provision this as a workaround for 2.0

Actions #1

Updated by Andrea Gambacorta over 10 years ago

Ermal Luçi wrote:

A setup with multiple WANs can losse its default route when its gateway is marked as down from apinger.
This results in a system non-functional for some services running on pfSense itself and that are not handled by a PBR.

A fix was committed https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/1d60ed9bb4901c5b85813d0dab32630e8a135d41
to provision this as a workaround for 2.0

I've insert this issue as feature(http://redmine.pfsense.org/issues/1411) but i think can be correlated at your post.

Actions #2

Updated by Ermal Luçi over 10 years ago

Another improvement was committed related to this.
It now considers gateways that are not marked as default in the GUI.

Actions #3

Updated by Ermal Luçi over 10 years ago

  • Target version changed from 2.0 to 2.1

I am moving this to 2.1 for improving.
For 2.0 the option under system->advanced should be enough.

Actions #4

Updated by Chris Buechler over 9 years ago

  • Status changed from Feedback to Resolved

this particular issue is resolved. there are still issues with default gateway switching in general that need to be quantified and have their own ticket(s)

Actions

Also available in: Atom PDF