cancel
Showing results for 
Search instead for 
Did you mean: 

Standalone R700 AP with DHCP issue

bar_chiu
New Contributor II
Hi everyone,

I'm done configuring an R700 AP as a standalone AP but I always get a different address - 169.254.27.89 with subnet mask of 255.255.0.0 - on my test phone from the configured pool of addresses.

The attached photos are the configurations on the concerned AP:

Image_ images_messages_5f91c3e4135b77e2478ce679_36289774e41059e20c8d66764e862561_RackMultipart2016011323881bk0s-43067051-5a40-497a-81dc-2c076b70cc69-245146848.png1452661773

Any help will be greatly appreciated.

Cheers
9 REPLIES 9

john_d
Valued Contributor II
169.254 is a link local address. It is common practice that devices will assign themselves a 169.254.0.0/16 address if they are configured for DHCP but no DHCP server responds.

bar_chiu
New Contributor II
I see.

I shifted my test device on a laptop. It brought some good results. Resolved IP address was within the configured range. Changed the Local IP Address (1st picture) as it pertains to the gateway of a subnet.

However, it caught a snag as it looks for a DHCP server. Isn't that the AP was configured as the DHCP server?

john_d
Valued Contributor II
To confirm, did you try changing the Packet Forward option as suggested by me and Anusha? Without it set to Local Subnet NAT, the DHCP server won't be listening. Ruckus's DHCP server does not listen on the WAN interface, it only listens on local subnets. If you select Bridge to WAN, you won't get the local DHCP server assigning IP's.

bar_chiu
New Contributor II
Image_ images_messages_5f91c46c135b77e247a79136_88994cfdc589227778a43ddbc574c4fb_RackMultipart20160114254139kf6-59dd7e5a-8a9a-4002-82e3-c2ffb447c3b3-228239157.png1452750333
As attached... I noticed the effect when Bridge to WAN is selected.

bar_chiu
New Contributor II
Case Closed.

Solution: Local subnet is configured with the same subnet where the AP ip is configured.