Project

General

Profile

Actions

Bug #9232

closed

pfSense cant connect to hosts on the internet using non-local gateway via interface specific route after reboot

Added by Tom Stultiens over 5 years ago. Updated over 4 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Gateways
Target version:
-
Start date:
12/27/2018
Due date:
% Done:

0%

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

Description

After upgrading to 2.4.4_p1, pfSense cannot connect to hosts on the internet anymore. Clients in the LAN behind the pfSense machine could still access the internet without.
My pfSense machine is a VM running on a physical host in an OVH datacentre. The gateway lies outside the subnet of the WAN IP. Ever since the option became available, I used the "Use non-local gateway through interface specific route" tickbox in the gateway configuration. This has worked perfectly until the 2.4.4_p1 update. There are no other settings applied in the gateway settings. The host has only a single WAN interface (and a single gateway out).
After removing the default gateway (route del default) and adding it again via the shell (route add default a.b.c.d), internet access on the pfSense machine itself was restored.

Forum thread for reference:
https://forum.netgate.com/topic/138932/non-local-default-gateway-via-interface-broken-after-updating-2-4-4-to-2-4-4_p1

I tried to be as concise as possible. Hope the issue is clear.

Actions #1

Updated by Jim Pingle over 4 years ago

  • Status changed from New to Duplicate

Duplicate of #7380

Actions

Also available in: Atom PDF