Link to home
Start Free TrialLog in
Avatar of jskfan
jskfanFlag for Cyprus

asked on

Set up WAP in the Network

I would like to get a big picture of how to set up Wireless Access Point in the Network.
For instance, let's say we already have a wired network connected to Internet, and we need  to install WAPs in conference rooms so that users who use the rooms will be able to connect to internet.

Assuming there is no wireless LAN Controller  used in the Network..

Can someone explain how to connect and configure the involved components that will get the wireless connection to work.?

Thank you
SOLUTION
Avatar of Shane McKeown
Shane McKeown
Flag of Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jskfan

ASKER

What I was trying to understand:
Let 's say our Network is already connected to internet, I mean each workstation is wired to the Network and connected to internet, but we need our conference rooms to have Wireless Internet connection for Laptop users.

we'll get a one WAP for each Conference room…Then from there:

Where are we connect each WAP? to any Network Switch?
How are we going to configure each WAP ? IP address, Default Gateway?
How are Laptops going to connect to each WAP, assuming all WAPs have the same SSID and password?

Thank you
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jskfan

ASKER

<<<WAP's do not need default gateway - they only need that if you want to manage them from a remote location. Why you ask? Because a WAP is simply a network switch with an aerial. Network switches don't need IP's to function...only for management - same with WAP's>>>

The reason I asked is because WAPs in the Network will get internet connection through the main router that is providing internet connection to user workstations.

for instance, if Out of the box WAP gets IP address of 192.168.1.1, and that address already exists in the network then we'll have to manually change it. and the subnet where wireless devices are should be different than the production subnets…which might be in 10.x.x.x range.


What I need from Wireless Network Expert is to tell me how this can be lined up, for instance:

Get an unmanageable switch, plug it to the port of the internet router, plug each WAP to the unmanageable switch, login to each WAP using the browser and configure IP address and SSID of each WAP, etc..
that was my assumption from someone who does not have knowledge about setting up wireless network in the company, an expert might suggest a better way to do it…


Thanks
SOLUTION
Avatar of Craig Beck
Craig Beck
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jskfan

ASKER

So if My production Network is in 10.x.x.x network, and I want Wireless network to be in 192.168.x.x Network,  This may need some specific configuration.

Because the production Network (10.x.x.x) requests for Internet will all be sent to the edge router or firewall that will NAT the network IPs to public addresses…

how can I configure the same thing for Wireless Netwok ?
I assume the end goal here is separation from the production network? Meaning wifi users can't access the production network at all?

In that case yes you need vlans...the router needs to have option to create vlan and your switches need to be managed so they can work with vlans as well...

What make/model is the router and your switches?
Avatar of jskfan

ASKER

All is going to be Cisco …
Avatar of jskfan

ASKER

Simple Way:
I guess I will just need to purchase a separate internet router like the one used at home and connect it to a dumb  switch and connect  the WAPs to the switch


Complicated Way:
if I want to provide wireless connection from the existing wired connection in the LAN and with a separate Network Segment (192.168.x.x) then the configuration will  get complicated between the core switch and the Edge Router facing internet.

BECAUSE:

from Core switch we can configure
IP route 0.0.0.0 0.0.0.0 10.10.10.1 (which is the internal interface IP of Cisco Edge Router or Firewall connecting to Core Switch and that will do the NAT).
When the traffic comes back from internet:
IP route 0.0.0.0 0.0.0.0 10.10.10.2( which is the IP address of the Core switch interface connecting with the EDGE Router)
Avatar of jskfan

ASKER

I wonder if my above assumption is correct ?
I'll draw a diagram when I get home...
Ok I'm not home yet, but you can do it without having to use dumb switches and a separate internet feed if you really need to.  I would recommend a second internet router though at least if you can integrate that in a DMZ-style.

Basically, create a new VLAN for guest traffic on your switches.  The Cisco AP would have two or more VLANs on it (management/corporate and guest as a minimum).  You could then put a new internet router (connected to your main internet feed) onto the guest VLAN and use that as the guest client's default gateway.  This allows you to use all the same infrastructure in a shared fashion without allowing access to corporate resources from the guest network.

Don't worry about IP addresses for Access Points.  If you use Cisco APs they will use DHCP to obtain an IP by default.  You can then login to the AP and change the IP yourself, so there'll be no issue with IP conflicts.
Avatar of jskfan

ASKER

Craigback…

Thanks I will wait for the Diagram, to have a good big picture..
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jskfan

ASKER

I will check that …thank you!