Project

General

Profile

Actions

Bug #9004

closed

Default gateway IPv4 set to a group fails after restart on 2.4.4

Added by Daniel Williams about 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
High
Category:
Routing
Target version:
Start date:
10/04/2018
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.4
Affected Architecture:
amd64

Description

We set the default gateway IPv4 to be a group, called WAN_Failover. That group consists of WAN1 Fiber at tier 1 and WAN2 Cable at Tier 2.

After a reboot of the PFSense hardware, the PFSense can see no default gateway by which traffic can be routed, no client have any internet access. We locally can get to the PFSense box and log in without issue. We went to the Diagnostic | Ping page; the PFSense can ping out by WAN1 or by WAN2, but if you set the source address to be Automatically selected (default), PFSense cannot perform a ping test, stating that no route is available. We then go back to System | Routing and change the Default Gateway IPv4 to the WAN1 (fiber circuit), go back to ping out, and can ping via automatic (as WAN is the default). Now the odd part starts, we change the Default Gateway IPv4 back to WAN_Failover and everything works fine - clients get to the internet, ping out automatic works fine - all is fine. After a firewall reboot, no outbound traffic will be passed until we change the Default Gateway IPv4 to WAN and apply - after this traffic is then passed without issue. We now can change the Default Gateway IPv4 back to the gateway group WAN_Failover and all will still work fine.

This is repeatable.


Files

Gateway group.JPG (40.7 KB) Gateway group.JPG Daniel Williams, 10/04/2018 08:49 AM
Default routing changed to WAN1.JPG (79.5 KB) Default routing changed to WAN1.JPG Daniel Williams, 10/04/2018 08:49 AM
Actions

Also available in: Atom PDF