Bug #2949
closeddhcp on embedded doesn't provide router in lease information
0%
Description
Early Saturday morning I updated 2 pfsense devices to the latest snapshot (2.1-BETA1 built on Fri Apr 12 16:46:36 EDT 2013). Both were on existing 2.1 builds, one is a physical server with full processor, the other is a netgate alix board. The full server had no issues with clients or connectivity in the days following. The netgate had problems with client connectivity just a few hours later. After investigation, it turned out the netgate DHCP was not providing a router in DHCP leases. The netgate DHCP server did not have a router/gateway defined for the LAN interface as it should have been handing out its own interface IP for the router, but ipconfig output and packet captures confirm that no router was provided in DHCP responses. After configuring a router/gateway on the LAN interface DHCP server on the netgate, it began to correctly hand out router information again. I have copies of config files and packet captures, but sure which would be preferred or needed but this was somewhat of a breaking problem as client's dhcp leases timed out, connectivity was lost.
Updated by Phillip Davis over 11 years ago
I am having no trouble with this on multiple Alix nanoBSD systems - builds Fri Apr 5 00:57:50 EDT 2013 and Sun May 5 07:29:11 EDT 2013 for example. I get my LAN/WiFi/whatever interface IP provided by DHCP as the gateway.
If this is still a problem you will need to provide some more ideas about how to reproduce it.
Updated by Chris Buechler over 11 years ago
- Status changed from New to Closed
pretty sure this is a problem that only existed for a short period of time, definitely not currently an issue.