You are here

hap ac lite dhcp server on port 5

5 posts / 0 new
Last post
DF2SI
hap ac lite dhcp server on port 5
I plan to use multiple mesh nodes connected to port 5 of an hap ac lite, through a switch. It is clear that there can be only one dhcp server. In order to be able to play with different mesh node configurations it would be most convenient to run the dhcp server on port 5 of the hap and configure all the mesh nodes as dhcp clients.
I did not find a way to enable a dhcp server on the hap's port 5. Did I miss anything?

Wolfgang DF2SI
K6CCC
K6CCC's picture
No DHCP on the DtD port.
No DHCP on the DtD port.  Each node self assigns an address that is related to the mesh IP address.  You do not need to do anything related to IP addresses on the DtD port.
For example, one of my nodes has a mesh IP of 10.36.197.198 and a DtD port IP of 10.37.197.198 (2nd octet is one number higher).
 
DF2SI
Confusion...
Thanks for the quick response.
I had found a discussion on the topic in this forum: https://www.arednmesh.org/content/documentation-connect-multiple-local-n.... There it was stated that DHCP server needs to be disabled on all but one node.
For me both scenarios look plausible.
Either, as implied in this other discussion, there is a /29 subnet on the DtD port with a DHCP server on exactly one of the mesh nodes, or, as you imply, each of the mesh nodes has its own IP address, and, consequently, the DtD port uses the entire 10.0.0.0/8 net. In the latter case it would not matter whether a DHCP server is enabled on any of the nodes in the DtD domain as no DHCP client is active.
K6CCC
K6CCC's picture
You're mixing up the local
You're mixing up the local LAN and the DtD connections.  What you describe with multiple nodes connected and needing to make sure only one device has DHCP enabled is for the local LAN (ports 2 - 4 on a hAP ac lite).  Port 5 on your hAP is exclusively used for DtD and you either directly connect that to another node or to multiple additional nodes via a switch.  You do not need to make ANY configuration for it to just work.  Note that the DtD connection will be VLAN tagged with VLAN 2.  This is done so that devices that only have a single port (a Ubiquiti Rocket for example)  can have local lan (untagged), WAN (tagged VLAN 1) and DtD (tagged VLAN 2) on that single Ethernet port.

The DHCP server applies to the local LAN port or ports.  There is no DHCP (client or server) on the DtD port.  Everything on the DtD is static IP and normally not assigned by you - but rather assigned when the node is configured with an algorithym based on the MAC (same concept as the mesh IP address).

 
DF2SI
Thanks!
Thanks a lot for the explanation. This is great news!

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer