Bug #7380


WAN DHCP Gateway Outside of Subnet Causing Route Issues

Added by Doran Smestad about 5 years ago. Updated about 2 years ago.

Target version:
Start date:
Due date:
% Done:


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


When deploying PFSense in OVH's public cloud, they assign a IPv4 address via DHCP in a /32 subnet. Naturally, with such a captive subnet, the default gateway will reside outside of the subnet. This causes problems with the /usr/local/sbin/pfSense-dhclient-script.

As it is currently written, the script will attempt to add the default route via: $ROUTE add default $router (see Since the gateway is outside of the subnet, there is no route to reach said gateway, causing the route assignment to fail and thus no connectivity.

I fixed this in my copy of the 2.4 PFSense March 11 nightly build by adding a line to add a host route to the gateway on the particular interface. See my branch here:

I opened this bug on Redmine to provide some tracking of the issue, and this being my first experience contributing to PFSense, I wasn't sure if you all would be receptive to a pull request out of nowhere. Please let me know how you would like me to proceed.


Actions #1

Updated by Jim Thompson about 5 years ago

  • Category set to Gateways
  • Assignee set to Renato Botelho

Assigned to Renato for evaluation.

Actual diff is here:

Seems like potential large impact(s) on 2.4.0 Will need a PR and signed CLA prior to integration

Actions #2

Updated by Doran Smestad about 5 years ago

Thanks Jim. Apologies for not linking the diff the first time around.

I've signed the CLA and submitted a pull request:


Actions #3

Updated by Jim Pingle over 2 years ago

PR was closed due to timeout, requested changes were not made in a timely manner.

Actions #5

Updated by Jim Pingle about 2 years ago

  • Status changed from New to Pull Request Review
Actions #6

Updated by Renato Botelho about 2 years ago

  • Status changed from Pull Request Review to Feedback
  • Target version set to 2.5.0
  • % Done changed from 0 to 100

PR has been merged. Thanks!

Actions #7

Updated by Viktor Gurov about 2 years ago

  • Status changed from Feedback to Resolved

works as expected on 2.5.0.a.20200426.2333

I can see local route to the router ip address, like:

default             UGS      vtnet1           0c:dd:ae:ed:96:01  UHS      vtnet1


Also available in: Atom PDF