I have an old d-link router that i have setup as an access point. I have assigned it a static IP of 192.168.88.3 and have set its DNS to that of the mikrotik (192.168.88.1). I have also switched the DHCP server off on the d-link router. I have then connected it to the mikrotik via ethernet.
Problem:
When connecting to the AP it takes about 3-4 min to connect and to gain internet access. Im not sure why this would be happening. It seems that the MikroTik being the DHCP server takes forever to auth and assign an IP?
If anyone has had this problem and knows how to fix it would be greatly appreciated.
I got home and plugged another laptop into the AP router and it assigned an IP straight away and it was able to access the net. I unplugged and plugged the network cable in and out and it was fast in assigning an IP.
I then disabled the Wifi on the MikroTik router and just had the AP running. I was then able to join and unjoin the AP just like i could via ethernet which is great.
What ive noticed:
Ive noticed that when joining the MK wireless first and then joining the AP wireless straight after it takes forever to assign an IP on the AP wireless. This is obviously the problem and im not sure what it might be.
Its almost like its slow to release the first connection and then to reconnect via the AP.
For this setup to work, the Dlink should transparently bridge its wlan interface to its ether ports (in the same way you bridged the mikrotik ether master port + wlan interface), and it seems this is not the case, or at least isn’t that transparent. That’s why wired connections on the dlink don’t have problems getting DHCP from the mikrotik, while wireless do.
Try investigating that d-link specific issue.
Are the dlink AP and mikrotik AP providing wireless on different seperate areas, far from each other? What’s the routerboard model?
You have another option if you’re feeling brave and want to keep the old dlink by all means: flash it to openwrt or gargoyle, then config wireless, and create a true L2 bridge with wireless interface + ethernet interface; that’s all needed.
I personally wouldn’t bother if the dlink is sporting an atheros wireless N chip, as the wireless will lock now and then while using third party firmware no matter what (opensource driver, closed source HAL driver portion issue); instead of that would get another RB, dlink with stock firmware wireless doesn’t hold a candle near Routerboards anyway, and you could manage all wireless from one of tthe routerboards by using CAPsMAN.
