I have LEDE 17.01.02 running on a Buffalo router. The Buffalo is configured exclusively as a wireless access point. I have a pfSense gateway/firewall/router box that is providing dhcp service to my entire network. The wireless AP has two VLans configured, one private and one guest.
My network configuration to the access point looks like this:
Incoming WAN ---> pfSense Gateway / Firewall / Router ---> Managed Switch (Netgear) with 3 VLANs (1=home wired vlan, 20=private wireless vlan, 30=guest wireless vlan) ---> Buffalo AP
pfSense Router = 192.168.123.2
Netgear Managed Switch = 192.168.123.4
Wired LAN = 192.168.123.xxx
Private Wlan = 192.168.124.xxx
Guest Wlan = 192.168.133.xxx
Buffalo LAN interface = bridged to Wlan
Buffalo WAN interface = 192.168.123.5 (management interface)
I am seeing in my DHCP logs a DHCP Discovery query coming from the MAC address of the Buffalo LAN interface. My DHCP server replies with a DHCP Offer, but the DHCP handshake ends there. The logs show that this sequence happens continuously every three seconds. Since the Buffalo LAN interface is bridged to the Wlan it actually does not have an IP address itself, and the DHCP exchange appears to be unnecessary. I am wondering how to stop the continuous discovery/offer exchange.
The configuration of my LAN bridged interface is listed below.
config interface 'lan'
option type 'bridge'
option _orig_ifname 'eth0 radio0.network1 radio1.network1'
option _orig_bridge 'true'
option proto 'dhcp'
option ifname 'eth0.1'
option hostname 'buffaloap-lan'
I see that the protocol is listed as 'dhcp', which is probably what is initiating the DHCP Discovery. I have the DHCP service disable on startup, but I do see that the odhcpd service is still enabled. The protocol options in the GUI for the bridge include 'Static', 'Dhcp-Client', and 'Unmanaged', and a list of others that don't appear to be relevant.
I don't think that I want to set the protocol to Static, since the bridge does not use an IP address directly. So that leaves me with trying to understand whether disabling the odhcpd service or changing the protocol to unmanaged is what is needed here. The documentation that I have reviewed doesn't make it clear to me whether one of these changes would solve the problem, or produce an unwanted side effect. I don't find anything describing what the unmanaged protocol does. It could also be possible that there is something else creating this problem that I haven't considered.
Thanks.