Thursday, 26 June 2014

Simple Wireless Connection & SSID

Using the help of Cisco Support, I was able to create a simple SSID to broadcast from the access point as well as have a wireless device to connect to it. Here's some of the code used:

Dot11 ssid test
>Vlan 1
>Authentication open
>Mbssid Guest-mode

Int dot11 0

>ssid test
>Mbssid
>encryption vlan 1 mode wep mandatory
>encryption vlan 1 key 1 size 40bit 0 0123456789

interface Dot11Radio0.1

>encapsulation dot1Q 1 native
>bridge group 1
interface FastEthernet0.1
>bridge group 1
>encapsulation dot1Q 1 native

bridge irb

bridge 1 route ip
wr


Combined with the network I created earlier, of a router and switch, the router was able to give out addresses via DHCP. 
Scanning with my phone, I was able to discover the SSID of "test".

This was the status notification on the access point when my phone connected/disconnected. 

As shown on the screen shot above, shown and checked using a networking application, the phone was automatically allocated an IP address and default gateway. (Ignore the DNS info, that's not set on the router as of yet)
The phone was also able to successfully ping the default gateway.

Thursday, 19 June 2014

Cisco Aironet 1200 Wireless Access Point GUI access

I finally managed to gain access to the Wireless Access Point using the GUI and a browser.

The key concern that was causing me issue was being unable to access the GUI via an internet browser like what most Cisco resources referred to, Generally being very brief such as "Enter 10.1.10.1 etc" in to your browser.

Firstly, I created a basic network with the access point, a computer, a switch, and a router. It's visually replicated on Packet Tracer below to show the rough layout.
I setup up the router with the basic settings on the interface (ip address 192.168.1.254), and enabled it as a DHCP server.
ip dhcp excluded-address 192.168.1.254
ip dhcp pool TEST
>network 192.168.1.0 255.255.255.0
>default-router 192.168.1.254
This allocated the PC connected a basic address and was able to communicate with the router.
(The switch does not need any configuration for this basic network, which is used for access testing.)

This network so far was working, accept for the access point. It was not communicating although the interface was up. At first I attempted to give the Fast-Ethernet connection a address manually, but this did not let it connect to the network correctly. What I discovered was for the physical connection, you apply the address to the "BVI 1" interface. I used the following code so that it acquired an address for the DHCP server:
interface BVI1
>ip address dhcp
This gave the interface an address automatically for the sake of testing the GUI. In a final network I would be using static address. After the address were applied, it brought up the interface and I was then able to connect to the access point via a GUI (Using the address provided by the DHCP server). All default passwords/usernames were "Cisco".


Progress Report

I spent last week focusing on my mid-project progress report, of which I handed in on time before the due date without requiring an extension.

Monday, 9 June 2014

Current Wireless State

With the help of a Cisco Wireless chapter, I have managed to configure the wireless Lan controller.
Although guides have not been help thus far, next step is to configure the wireless access point for end user connectivity.