add name=hs-pool-14 ranges=192.168.10.2-192.168.15.254
add name=dhcp_pool1 ranges=10.10.10.50-10.10.11.200
/ip dhcp-server network
add address=10.10.10.0/24 dns-server=18.104.22.168,22.214.171.124 gateway=10.10.10.1
add address=192.168.0.0/24 dns-server=126.96.36.199,188.8.131.52 gateway=192.168.0.1
add address=192.168.8.0/21 comment="hotspot network" dns-server=184.108.40.206,220.127.116.11,18.104.22.168 gateway=192.168.10.1
Well, either your pool or DHCP Server Networks statement for the FD Bridge server is not correct. Your pool is assigning out of 10.10.10.0/23, but the network statement is for a /24, so if you assign an address from 10.10.11.1-10.10.11.200, it won't assign any subnet mask, gateway, or DNS servers. Judging by the 10.10.10.1/24 address on the bridge, I would guess the pool is incorrect?
From your original post, I assume your primary issue is on the Guest Bridge network. Nothing really jumps out at me about the config for that DHCP Server. Can you try to capture DHCP traffic on that interface (preferably during a low traffic time, so there's not a lot of other clutter in the pcap file)?
- Go to Tools > Packet Sniffer
- Set up a file name so it will save the capture to disk (I recommend adding a .pcap file, so that it will open in WireShark once you download it to your computer)
- Increase the file limit to 10000 KB
- On the Filter tab, choose the "Guest Bridge" interface
- Click Apply, then click Start to start capturing
- Send DHCP requests from at least one working and at least one not working computer
- Click Stop to stop the capture
- Open the Files dialog, and download the capture to your computer so you can open it in WireShark
A working DHCP client should show all four DHCP packets in this capture (DISCOVER, OFFER, REQUEST, ACK). I would expect the non-working will show only DISCOVER and OFFER. If that is the case, I would then try to get a WireShark capture on the non-working client, to see if that client is receiving the OFFER.