DHCP crossing interfaces
-
Ok, I just configured a LAN segment with dhcpd address pool:
10.0.0.50 - 10.0.0.59
works fine.
Then I added an atheros wireless card as OPT1, turned on dhcpd for that interface, and assigned this address pool:
10.0.0.70 - 10.0.0.79
… and shortly after that, a fixed workstation, with NO wireless card in it, and attached to the LAN segment, picked up this dhcp lease:
10.0.0.71
.... so it would appear that two different lease ranges, on different interfaces, get mixed up between them. AGAIN, the host that got the wrong address has NO wireless NIC in it, so it definitely got the lease from the wrong interface.
EDIT: I am running 2013-05-02, so if you know of this bug and it's been fixed, perhaps this is just noise...
-
I split this from the other thread since it was not related.
It sounds like maybe you have those interfaces bridged. If they are bridged, then you really only want one interface to have an IP address, and only one of them should have DHCP configured.
-
Thanks for your response.
I am running a normal pfsense config (default, nothing interesting) between LAN <–> WAN
... but OPT1 is configured as an access point.
I don't think I have any bridged interfaces, nor do I want any ...
However, you are saying that I should only run dhcpd on the LAN interface? Will wireless clients of the OPT1 interface still get the dhcp lease from LAN ? That never occurred to me...
-
You can't have the same subnet on two interfaces without bridging, so there is some other misconfiguration happening there (Unless you really are using /27 or smaller on each…)
-
Thanks. Yes, I had both NICs on the same subnet, so that was probably the trouble.
