Project

General

Profile

Bug #2518

Gateway in DHCP Server Doesn't Use Default Setting

Added by Steve Vigneau over 8 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
DHCP (IPv4)
Target version:
Start date:
06/22/2012
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.1
Affected Architecture:

Description

In the DHCP server settings the gateway option reads:

"The default is to use the IP on this interface of the firewall as the gateway. Specify an alternate gateway here if this is not the correct gateway for your network."

After updating from a mid-April beta to the 20-Jun beta this appears to no longer be the case. If this field is blank a gateway (Router) will not be sent with the DHCP response. If a gateway is specified in pfSense, things'll work as expected. See attached screenshots to see the two different DHCP offers (with and without gateway specified).

Version where issue was identified:
2.1-BETA0 (i386)
built on Wed Jun 20 18:13:24 EDT 2012
FreeBSD 8.3-RELEASE-p3

History

#2 Updated by Chris Buechler over 8 years ago

  • Target version set to 2.1
  • Affected Version set to 2.1

#3 Updated by Seth Mos over 8 years ago

  • Category set to DHCP (IPv4)

June 16th works for my mac here, both v6 and v4 has gateways.

Upgrading router to a june 22nd now, gateway field is not filled in for my v4 dhcp server config.

#4 Updated by Seth Mos over 8 years ago

OK, I still have my default gateway on June 22nd. I think I know what feature you are triggering.

Just to verify, does your install have a gateway at all? If your pfSense install has no gateway itself, as in, any at all it will not add a gateway to your config. If any gateway is dynamic, or static and there is a gateway it will add this field.

Are you using ospfd or bgp for your routing?

You can indeed manually override this by specifying a gateway.

To clarify, this is the same approach which is employed on IPv6, only advertise a gateway if the router actually has a route. This makes the client fail over fast between protocols instead of hitting a 30 second timeout before v6 is attempted.

#5 Updated by Jim Pingle over 8 years ago

As an extra data point, I also still have a default gateway in DHCP on a snap from today.

#6 Updated by Seth Mos over 8 years ago

  • Status changed from New to Feedback

#7 Updated by Chris Buechler almost 8 years ago

  • Status changed from Feedback to Resolved

#8 Updated by Darwin Mach over 7 years ago

This bug has re-appeared after updating to the 10 MAY 2013 build of 2.1-BETA0 (AMD64)

#9 Updated by Darwin Mach over 7 years ago

Darwin Mach wrote:

This bug has re-appeared after updating to the 10 MAY 2013 build of 2.1-BETA0 (AMD64)

Has something to do with tagging as an IPv4 router. Edit and re-apply updated DHCP Server settings to fix.
Source: http://forum.pfsense.org/index.php/topic,62027.0.html

#10 Updated by Darwin Mach over 7 years ago

Darwin Mach wrote:

Darwin Mach wrote:

This bug has re-appeared after updating to the 10 MAY 2013 build of 2.1-BETA0 (AMD64)

Has something to do with tagging as an IPv4 router. Edit and re-apply updated DHCP Server settings to fix.
Source: http://forum.pfsense.org/index.php/topic,62027.0.html

Err, rather follow the suggestion from here:
http://forum.pfsense.org/index.php/topic,61317.0.html

Also available in: Atom PDF