I’m having some trouble with MT dhcp relay.
First of all I have to explain the topology and addresses of my network.
|…|
|MT (as client)| >-wireless-< Central AP (Wavion WS410) >-ethernet-< server (IBM PC running debian-DHCP server)
|…|(172.x.x.x)_(172.x.x.x - 10.x.x.x)
|…|
| MT (as AP) | >-wireless-< clients (10.x.x.x)
||
(172.x.x.x)
I have two networks: one for the clients and one for management. The management network has fixed IP addresses (172.x.x.x) while the clients network uses DHCP from the IBM server (10.x.x.x).
The problem is that I can’t do WDS between MT and Wavion, so I defined a DHCP relay in the MT in order to let clients get their IP address from the server.
This didn’t work and I capture some packets at the client to see the DHCP negotiation and I saw that everything was ok with the server, packets were sent and received ok, and the IP was asigned properly but inmediatly after that one packet from the MT was received (DHCP NACK) which screws up everything.
The only one way I’ve found to make this work is to set another IP address in the MT in the clients range (10.x.x.x) and this address must be the first one in the IP adresses list. This fact oblies me to fix this IP (10.x.x.x) because if I configure a DHCP client, when the MT restarts, the other IP (172.x.x.x) becomes the first one and things doesn’t work.
I want to know if this is a RouterOS bug or maybe it’s ok that works like that (i’m not a dhcp expert).
Maybe there is a way to define the order in the IP addresses list in order to avoid setting the IP in the clients range (10.x.x.x) as a fixed IP and be able to use the same dhcp server as the clients for getting this address. I want to avoid changes in the server and with the solution I’ve found I have to change the dhcp IP clients range, taking some address to use as fixed for the MTs.
Thanks for your help.