Actions
Bug #14906
open
DHCPv4 server self-assigning address to own DHCP client-enabled interfaces
Status:
New
Priority:
High
Assignee:
-
Category:
DHCP (IPv4)
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.7.x
Affected Architecture:
All
Description
Assume three NICs: igc0, igc1, igc2
Assume a single bridge: bridge0 (OPT2, OPT3)
And a VLAN: igc0.1036
Interfaces assignment as follows:
WAN -> igc0.1036 -> IPv4 (DHCP): 1.2.3.4/30
LAN -> bridge0 -> IPv4 (static): 192.168.1.1/24
OPT1 -> igc0 -> IPv4 (static): 192.168.100.2/24
OPT2 -> igc1
OPT3 -> igc2
DHCP & RA enabled for LAN only.
The problem: switching OPT1 IPv4 settings from static to DHCP makes pfSense to assign itself an address from the LAN pool, also creating a wrong on-link route for its LAN subnet over the igc0 port, which is the underlying IF of WAN.
Of course this is easily noticeable when no other DHCP serve is active on that igc0 port broadcast domain.
No data to display
Actions