DHCP server no longer handing out default gateway

tenortim · May 6, 2013, 7:01 PM

Hi folks,
I just updated to the 5/5 snapshot (previous version was a March 2013 snapshot), and things were not happy.

After a bit of head-scratching, it seems that the DHCP server is no longer handing out the default route unless you explicitly enter the default gateway in the configuration. Previously, it just handed out the LAN IP address. Explicitly setting the gateway in the DHCP server configuration worked around the problem, but has anybody else seen this?

My configuration is using a 6to4 tunnel to play with IPv6 (since Comcast don't have a real DHCPv6 service in my area), but I disabled IPv6 entirely and the problem persisted.

Thanks.

Beerman · May 8, 2013, 3:23 PM

Hi,

same problem here…

http://forum.pfsense.org/index.php/topic,61317.0.html

But unfortunately no solution for this, until now… :(

jimp · May 8, 2013, 7:13 PM

Read and follow my suggestion in the other thread.

Beerman · May 8, 2013, 8:00 PM

OK, thx! Works now!

Sorry, but I was / am confused…

I Do not understand the relation between the standard GW on the WAN IF and the "missing" GW on the LAN IF... ??? In fact the Standard GW for the WAN IF was configured as IPv4 and "dynamic".

But by saving the configuration, without changing it, seems to be working and the dhcpd on LAN IF is handing out the IF Adress as Standard-GW again.

Thx! :)

jimp · May 8, 2013, 8:15 PM

If there is no IPv4 gateway defined, the firewall does not believe it is an IPv4 router, and thus will not hand out its own IP as a gateway for DHCPv4.

If the detection broke, it was because the gateway was missing a tag internally that classified it as actually being an IPv4 gateway. Editing and saving added the tag.

Beerman · May 8, 2013, 8:33 PM

OK, thank's alot for your support and explanation! :)

tenortim · May 9, 2013, 11:49 PM

@jimp:

If there is no IPv4 gateway defined, the firewall does not believe it is an IPv4 router, and thus will not hand out its own IP as a gateway for DHCPv4.

If the detection broke, it was because the gateway was missing a tag internally that classified it as actually being an IPv4 gateway. Editing and saving added the tag.

Tyvm jimp!
I did so, and yes, it worked - I was able to remove the static gateway definition in the DHCP server and it picked up the default WAN gateway again. I can understand that this might break within beta snapshots. Hopefully, it won't break upgrading from 2.0 to 2.1-final when we get there.

jimp · May 10, 2013, 3:03 PM

On upgrade from 2.0.x to 2.1, existing gateways are tagged as IPv4 automatically.