no DHCPREQUEST from the client on vlan bridged interface.

david_moo

I recently bridged my LAN (default VLAN or VLAN 1) and VLAN 200 interfaces and set there IPV4 settings to none and moved the dhcp server to the bridge interface. I set system tunable for bidge interface and allowed all IPV4 traffic on it. After I did this the previous clients on the LAN interface get IP's from the DHCP server, but the clients on the VLAN interface don't. Note the VLAN clients are 3 switches away. I have another parallel VLAN with it's own subnet that takes the same switch path and works fine. So I think the switches are all configured correctly.

The DHCP handshake is:

CLIENT -> DHCPDISCOVER
SERVER -> DHCPOFFER
CLIENT -> DHCPREQUEST
SERVER -> DHCPACK

I'm getting the DHCPDISCOVER and DHCPOFFER, but no DHCPREQUEST from the client. Why is this?
Here suggests that the DHCP-client is NOT receiving the DHCP-OFFER.

Is there a pfSense firewall setting somewhere that is blocking this traffic?

DHCP server Log:

Aug 31 23:54:03	dhcpd	58357	DHCPDISCOVER from 78:45:58:a6:cd:66 (LiteBeam 307 Bann) via bridge0
Aug 31 23:54:03	dhcpd	58357	DHCPOFFER on 192.168.8.36 to 78:45:58:a6:cd:66 (LiteBeam 307 Bann) via bridge0
Aug 31 23:54:04	dhcpd	58357	reuse_lease: lease age 476 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.8.31
Aug 31 23:54:04	dhcpd	58357	DHCPDISCOVER from 18:e8:29:cc:5d:12 (5005RedBarn) via bridge0
Aug 31 23:54:04	dhcpd	58357	DHCPOFFER on 192.168.8.31 to 18:e8:29:cc:5d:12 (5005RedBarn) via bridge0
Aug 31 23:54:05	dhcpd	58357	DHCPDISCOVER from a8:40:41:1d:b8:e2 via igc0.1010: network 10.10.10.0/24: no free leases
Aug 31 23:54:06	dhcpd	58357	DHCPDISCOVER from 78:45:58:a6:c8:40 (LiteBeam Red Barn) via bridge0
Aug 31 23:54:06	dhcpd	58357	DHCPOFFER on 192.168.8.33 to 78:45:58:a6:c8:40 (LiteBeam Red Barn) via bridge0
Aug 31 23:54:06	dhcpd	58357	DHCPDISCOVER from ac:cc:8e:69:53:6c (axis-accc8e69536c) via bridge0
Aug 31 23:54:06	dhcpd	58357	DHCPOFFER on 192.168.9.94 to ac:cc:8e:69:53:6c (axis-accc8e69536c) via bridge0
Aug 31 23:54:06	dhcpd	58357	DHCPDISCOVER from 78:45:58:a6:cd:66 (LiteBeam 307 Bann) via bridge0
Aug 31 23:54:06	dhcpd	58357	DHCPOFFER on 192.168.8.36 to 78:45:58:a6:cd:66 (LiteBeam 307 Bann) via bridge0
Aug 31 23:54:07	dhcpd	58357	reuse_lease: lease age 479 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.8.31
Aug 31 23:54:07	dhcpd	58357	DHCPDISCOVER from 18:e8:29:cc:5d:12 (5005RedBarn) via bridge0
Aug 31 23:54:07	dhcpd	58357	DHCPOFFER on 192.168.8.31 to 18:e8:29:cc:5d:12 (5005RedBarn) via bridge0
Aug 31 23:54:08	dhcpd	58357	DHCPDISCOVER from a8:40:41:1d:b8:e2 via igc0.1010: network 10.10.10.0/24: no free leases
Aug 31 23:54:08	dhcpd	58357	DHCPREQUEST for 192.168.1.20 from d0:21:f9:bb:b1:db via igc0.1010: unknown lease 192.168.1.20.
Aug 31 23:54:09	dhcpd	58357	DHCPDISCOVER from 78:45:58:a6:c8:40 (LiteBeam Red Barn) via bridge0
Aug 31 23:54:09	dhcpd	58357	DHCPOFFER on 192.168.8.33 to 78:45:58:a6:c8:40 (LiteBeam Red Barn) via bridge0
Aug 31 23:54:09	dhcpd	58357	DHCPDISCOVER from ac:cc:8e:69:53:6c (axis-accc8e69536c) via bridge0

david_moo

Problem solved.
Netgear switches have a bug. If you add a new VLAN they block (maybe broadcast traffic??) DHCP on the VLAN until a reboot. Rebooted both switched and it immediately worked.
I remember running into this 2 years ago now on another VLAN setup. This is a long running bug (or undocumented safety feature???).