| Date: Fri, 13 May 2011 16:14:16 -0400
| From: Jim Pingle
|
| > In my case using the other gateway as a default route is of
| > no use, and even if the primary was not happy. I don't see
| > a way in the "Edit gateway" page to disable the upstream
| > check, though I suspect I could put a local
> > In my case using the other gateway as a default route is of no use,
> > and even if the primary was not happy. I don't see a way in the "Edit
> > gateway" page to disable the upstream check, though I suspect I could
> > put a local interface in the Alternative Monitor IP field.
>
> That is cur
On 5/13/2011 4:06 PM, John Sellens wrote:
> | > Anyone seen anything similar, or is this a known issue, or is it
> | > fixed in a more recent build?
> |
> | Check the system log and Status > Gateways, was the primary gateway
> | marked as being down?
> |
> | The default will switch to a secondary
| > Anyone seen anything similar, or is this a known issue, or is it
| > fixed in a more recent build?
|
| Check the system log and Status > Gateways, was the primary gateway
| marked as being down?
|
| The default will switch to a secondary gateway if the primary has failed.
When I connected, t
On 5/13/2011 2:38 PM, John Sellens wrote:
> Anyone seen anything similar, or is this a known issue, or is it
> fixed in a more recent build?
Check the system log and Status > Gateways, was the primary gateway
marked as being down?
The default will switch to a secondary gateway if the primary has
I added a second, non-default gateway to my pfsense box, and on
reboot, the supposed-to-be non-default gateway ended up as the
default gateway.
I'm running 2.0-RC1 (i386) built on Sat Apr 23 22:59:02 EDT 2011.
The gateways section of my config file looked like this:
wan
