Controllerless Networks

I've spent a few hours trying to solve what I think is a very easy problem and have finally given in and created a topic so thanks for reading.

 

I'm using an iAP-105 on my home network. My cable modem is the wired network DHCP server (192.168.1.1). Wireless clients connecting to the iAP are being assignied IPs something like 10.166.129.171 rather than the subnet of the wired side of the iAP. Clients are able to access the internet but I can't access my local servers. 

 

The iAP is configured with a static address of 192.168.1.4 and I configured the iAP with a network as follows:

 

- Employee

- Client IP is Network Assigned, Default VLAN

- Security Open

- Access Unrestricted

 

I've tried enabling DHCP relay and have tried setting up DHCP server scopes though I clearly don't quite understand what some of the options mean.

 

Any help is greatly appreciated.

If the client is using Network Assigned, you should make it static and VLAN 1, which is what would be considered the IAP's management VLAN, unless you changed it (by changing the uplink VLAN).  Also on the security tab on the SSID configuration, make sure the firewall policy is "unrestricted".

Thanks for the reply. I did a factory reset via the button on the back to make sure I had a clean start, then set it up again as I described in my original post. Access is unrestricted (firewall).

 

Two changes I made based on your comments:

- Client IP Assignemnt to Static, VLAN=1

- Access Point Uplink Management VLAN was 0, I changed that to 1. - Eth0 bridging is disabled (default setting)

 

"show clients" in the CLI shows my client with an IP address of 0.0.0.0.

 

My configuration can be seen here, if that helps:

http://teamhokies.com/misc/ap-config.txt

 

Thanks again!

I would start by upgrading your IAP-105 to the version of Instant here:  http://support.arubanetworks.com/LifetimeWarrantySoftware/tabid/121/DMXModule/661/Default.aspx?EntryId=24665

Thanks, I just upgraded the firmware and rebooted.

 

Testing with the same mobile phone as in myi OP I'm now being assigned an IP address that looks good: 192.168.1.11 however for some reason I don't get internet or local network access. I also can't ping the phone from other devices on the local wired network.

 

My Windows desktop PC is not being assigned an IP address when it connects (it is showing 169.254.*.*)

 

I updated the capture of my config log and dumped the AP-Tech-Support and AP-Tech-Support-Supplemental logs here, if that helps:

 

http://teamhokies.com/misc/ap-config.txt

http://teamhokies.com/misc/AP-Tech-Support-Dump.txt

http://teamhokies.com/misc/AP-Tech-Support-Supplemental.txt

 

Let the instant AP get an IP address via DHCP. You can assign a virtual IP address in addition that it will answer to as well. I say that because your logs say 1970, which means it is not finding an NTP server with your current setup, which can affect functionality. Try that first.

I made a few more changes:

 

System->NTP Server  = 0.pool.ntp.org

DNS server = 75.75.75.75 (from my ISP)

Virtual IP Address = 192.168.1.5

Obtain IP Address via DHCP server

 

The current time is now correct, progress. However, the AP doesn't get an IP address via DHCP, the clients also don't get an IP address via DHCP. Logs are updated:

 

http://teamhokies.com/misc/AP-Config.txt

http://teamhokies.com/misc/AP-Tech-Support-Dump.txt

http://teamhokies.com/misc/AP-Tech-Support-Supplemental.txt

 

Thanks again for your help

Reset the AP, let it get the ip address from DHCP and start from there.  Do not set the NTP server or anything.

I did a factory reset, connected via the instant wireless network and confirmed that it was set to request an IP address from an DHCP server. It hadn't gotten one so I rebooted it, it still didn't get an address. The status windows shows:

 

Virtual Controller IP: 0.0.0.0

VC DNS: 0.0.0.0

Management: Local

Master: 169.254.139.227

Uplink type: ethernet

Uplink status: Up

 

I tried disabling DHCP server from my cable modem and enabling it on a TP-Link wireless router running dd-wrt and got the same result.