Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[rjesse]

I have 2 1522's hooked up in AP mode (ie hardwired to a DIR655 router).  I have the local DHCP server turned off as I want to manage all IP's centrally on my DIR655 Router

Any device connected into the switch ports of the 1522 via a wired connected can get DHCP addresses from my Dlink Router without a problem, however wireless connections to the DAP1522 can not get a DHCP.  If I turn on the DHCP server locally it works, but that defeats the purpose of having the DHCP server on my central router.

I have upgrade to the lastest firmware 1.40.  Is there something I'm missing?   BTW my wireless devices connect via WPA/Personal (no WPS).

Rick

[snipepod]

I have this exact same problem.  DIR-655 with DHCP turned on. DAP-1522 with DHCP off.  Wired devices on the DAP-1522 get their IP address from the Dir-655, but the wireless devices do not.  If I turn on DHCP in the DAP-1522, then the wireless devices do get DHCP dealt address from the DAP-1522, but other wireless devices that try and connect to the DIR-655 get service from both or either DHCP server and chaos results. Does anyone know how to tell the DAP-1522 to pass DHCP request along to the DIR-655 for both wired and wireless clients?

[FurryNutz]

IF your running the DAP in AP mode then I think DHCP needs to be ON. If it's running in Bridge mode, then the DAP should relay and pass thru any DHCP requests from the host router to the clients.

[snipepod]

I'm running in AP mode.

Bridge mode disables the wireless functionality in the DAP-1522, hence a no-go.

If I turn on DHCP in DAP-1522, then both DHCP servers (Dir-655 and DAP-1522) try and service any DHCP requests for wireless clients attempting to connect to the SSID under the control of the DIR-655.    Funny thing, if both DHCP servers are turned on, a wireless client that connects to the SSID on the DIR-655 typically reports that its IP address (ipconfig /all) is an address from the Dap-1522, yet if you look at the network status on the DIR-655, it shows a lease for that client with an IP number in its defined range (different range than the DAP-1522).  Hence Client has wrong IP address for getting out to the internet and doing NAT.  Turning off DHCP in the DAP-1522 fixes that problem, but gets me my problem as reported at the top of this thread, and that is the wireless client connecting to the SSID under the DAP-1522 is not given an IP address from the DHCP server on the DIR-655 like I expect.

[FurryNutz]

Can you use the same SSID on the DAP and just manually assign the DAP a different WiFi channel to use? You can use the same SSID and password however the channel needs to be different.

[piyopiyo81]

If your DAP-1522 are running firmware 1.40 and hardware reversion A1 and will only support 802.11 draft n instead of 802.11 n. You need to contact D-Link if still under warranty then request unit replacement for hardware reversion B1 and will fix your problem.
My situation was DAP-1522 A1 set to 802.11n 5GHz and connect to DIR815 wireless router. DAP-1522 A1 will disconnected randomly and need to reboot DAP-1522 multiple times. Then I realized this A1 version are using Ralink RT2880+RT2850 which only support 802.11 draft n. I have D-Link replaced A1 to B1 which fixed problem.
A1 - RT2880+RT2850 support 802.11 draft n
B1 & DIR815 - RT3662 support 802.11 n

[FurryNutz]

Great information, didn't know there was a compatibility issue. Thank you for sharing.