Skip to main content

How to deploy 2.4GHz Wireless properly?

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)


Popular posts from this blog

Fortigate guide for Begineer - 6

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

Solving the "A general system error occured:Invalid fault" error in vSphere 4

Below error was come out when you try to migrate VM to other host for some reason. Below error was come out when you try to edit VM setting. Below error was come out when you power on the VM. How to solve those error? Here is how I resolve the error! Login to the Host that errored VM exist by using Terminal or Direct Console. Enter below command and press enter. restart Wait until all VMware Services are restarted. After that try to Power On/Edit Settings or Migrate the errored VM and you will see all you can do without any error pop-up. This kind of errors can occur if you shutdown/restart VM unproperly or shutdown/restart the Host unproperly that VM exist. You can check log file deeply if you willing to know precisely on this. May you all be happy. (Be knowledgeable, pass it on then)

Link Aggregating with Synology NAS and Cisco Switch

I’d like to share how to setup Link Aggregating between Synology NAS and Cisco Switch. I’ve got one Synology NAS with 4 Network Ports and I’m going to use 2 of them. Both Network Port to be as one Logical Link, Fault Tolerance and Load Balancing. To do that, I need to configure Link Aggregating on Synology NAS and EtherChannel with LACP on Cisco Switch. Below is brief steps to do to meet with my requirements. - Get connected Synology NAS and Cisco Switch as shown in picture. - Bonding two Network Ports of Synology NAS and assign IP Address - Configure EtherChannel with LACP in Cisco Switch and add two physical ports as Member. OK. Let’s begin from Synology NAS. - Login to the Synology and go to Control Panel>Network>Create>Create Bond - Select IEEE 802.3ad to get Fault Tolerance and Load Balancing Featureyou’re your switch not support 802.3ad you can only select Fault Tolerance only feature). After that click “Next”. - Choose the network port f