Skip to main content

How to deploy 2.4GHz Wireless properly?

By
There are a lot of things to take note before we going to deploy 2.4GHz Wireless Network.
If we select channel wrongly, stability and performance of our Wireless Network and it’s client will impact badly.

As we know that we can get Channel 1 to 11 (1 to 13 in some devices) for 2.4GHz spectrum.
A few channels are only non-overlap among these channel.
Channel 1,6 and 11 for range between  1 to 11 are not overlap.
Channel 1,5,9 and 13 for range between 1 to 13 are not overlap.

Currently, many wireless routers automatically select the channel for you upon initial setup, where depending on your wireless environment, it could lead to slow Wi‑Fi speeds and interference. 

It is not always right to configure Automation on channelization on Standlone or Controller Base Wireless devices.
The following explanation will describe what interference you're dealing with and takes you through the steps to selecting the right channel, so you can understand why you should choose between channel 1, 6 and 11 or channel 1,5,9 and 13.

There are three main causes of Wi‑Fi interference
1.     Co-Channel interference
Every client and access point on the same channel competes for time to talk as Wi-Fi devices working with  Half-Duplex.
2.     Adjacent-Channel interference
Every client and access point on overlapping channels talk over each other.
Adjacent-Channel interference on the other hand is where you run into problems and channel selection becomes critical. Luckily, these channel related interferences can be reduced or eliminated by selecting the proper Wi‑Fi channel for your network.
3.     Non-Wi‑Fi interference
Analog Camera, CCTV, Cordless Phone and Microwave Oven, etc are also using same frequency 2.4GHz and they can interference your Wireless Network stability and performance too.

So, we need to select the right Channel for our Wireless Network.
Check below example screenshot which taken by using insider Home (one of the free Wireless Channel Scanner application).


We should choose to configure SINGTEL-931_EXT Wireless from Channel 1 to  Channel 11 according to above screenshot as Channel 11 has less devices and less co-channel and less over-lapping channel.

This is the best configuration for Wireless Setting for Standlone Device .
If we are using Controller Base Wireless Device, we got to use this method too. Just need to ensure to check that we are going to select less devices, less co-channel and over-lapping channel.
Using more than one AP or Wireless Router with more than SSID also need to select and balance the Channel among non-overlapping channel 1,6,11 or 1,6,9,13.

That’s why configuring Wireless Broadcasting Devices or Wireless Controller as Auto Channelization , Auto Channel Width are not always right as we might need to hardcode it manually in some situation.
To do so, you will need and can find free or paid Wireless Channel Scanner application on Internet.

I’ll write about other Wireless post sooner or later. :D

Have a good time.
(Be knowledgeable, pass it on then)

Labels:

Comments

Post a Comment

Popular posts from this blog

Fortigate guide for Begineer - 6

By
I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a...
Post a Comment
Read more

Why do we need network virtualization?

By
We need to think about Server Virtualization first if we want to talk about Network Virtualization. In the era of cloud computing, servers are virtualized and used in Data Centers. We are facing a lot of problem when we virtualized our Servers, 1) Routing and Switching Problem Routing become the issue when we create Virtual Switch and VLANs according to production requirement. Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end. ၂) Firewall Services Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements. New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management. ၃) Load Balancing Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures. Once a tenant reaches their maximum capacity, it ca...
144 comments
Read more

Solving "WSUS administration console was unable to connect to the WSUS Server via the remote API" error

By
Today, I've got below when I try to connect my WSUS Server via WSUS Console. Below logs are display in Event Logs too. The WSUS administration console was unable to connect to the WSUS Server via the remote API.  Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 172.16.99.98:80 Source System Stack Trace:    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)    at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Soc...
7 comments
Read more