My rb133 ist associated to a wlan ap. With static assigned IP addresses everything is working fine. If I enable dhcp-client on wlan1 interface, it doesn’t work. Status is searching:
[admin@MikroTik] > /ip dhcp-client pr detail
Flags: X - disabled, I - invalid
0 interface=wlan1 host-name="mikrotik" add-default-route=yes
use-peer-dns=yes status=searching...
On the dhcp-server I’m getting the DHCP offer and it responds with a DHCP discover to FF:FF:FF:FF:FF:FF. So far so good. But the DHCP discovers obviously don’t make their way back to the rb133. The tcpdump output from the dhcp-server side:
Sep 10 21:40:56 abel dhcpd: DHCPDISCOVER from 00:05:3c:07:2b:2f (mikrotik) via eth0
Sep 10 21:40:56 abel dhcpd: DHCPOFFER on 192.168.200.24 to 00:05:3c:07:2b:2f (mikrotik) via eth0
Sep 10 21:40:59 abel dhcpd: DHCPDISCOVER from 00:05:3c:07:2b:2f (mikrotik) via eth0
Sep 10 21:40:59 abel dhcpd: DHCPOFFER on 192.168.200.24 to 00:05:3c:07:2b:2f (mikrotik) via eth0
Sep 10 21:41:04 abel dhcpd: DHCPDISCOVER from 00:05:3c:07:2b:2f (mikrotik) via eth0
Sep 10 21:41:04 abel dhcpd: DHCPOFFER on 192.168.200.24 to 00:05:3c:07:2b:2f (mikrotik) via eth0
Sep 10 21:41:10 abel dhcpd: DHCPDISCOVER from 00:05:3c:07:2b:2f (mikrotik) via eth0
Sep 10 21:41:10 abel dhcpd: DHCPOFFER on 192.168.200.24 to 00:05:3c:07:2b:2f (mikrotik) via eth0
Sep 10 21:41:16 abel dhcpd: DHCPDISCOVER from 00:05:3c:07:2b:2f (mikrotik) via eth0
Sep 10 21:41:16 abel dhcpd: DHCPOFFER on 192.168.200.24 to 00:05:3c:07:2b:2f (mikrotik) via eth0