Setting the optimum channel for your WiFi using ubuntu

So today I finally decided to fix our WiFi troubles at home. We have a 100mbps internet connection from starhub with a Cisco DCP3925 router and although I can get a full 100mbps speed when connected by a LAN cable, on WiFi I barely got 10mbps on I tried to call starhub for help but twice they made me change my WiFi channel to a random number and it didn’t work very well. I figured they were shooting in the dark with the channel numbers so I decided to do some research on my own and sort this out. Its really silly on part of starhub to use such trial and error methods to fix people’s WiFi. So here is the gist. Wifi works on 2.4GHz spectrum. The 2.4GHz spectrum is around 100MHz wide and it has 11 channels each 20MHz wide centered 5MHz apart from their neighbouring channels. Herein lies the muck. Each channels spreads itself over the center of next two channels on each side. While being on the same channel as another network is not ideal its better than being on a neighboring overlapping channel because 802.11 spec has methods for dealing with co-channel interference. This is bad because that means there is other wifi networks talking on some of the frequencies that your wifi uses.. So the ideal situation in your wifi setup is that there is no one talking two channels next to you. Enough of theory, now time for practical. How do you tell what are the channels being used in the area in your WiFi zone? In ubuntu you can use the iwlist command. sudo iwlist...

HTTPS/TLS on NginX and getting a certificate signed by a certificate authority

Today I decided to switch over my website to https mode and acquire a signed certificate for my website. I took the Comodo CA option and have gone for a free 30 day trial period. If things go smooth I might go ahead and purchase the certificate plan. I also learnt about three standardised different levels of validations plans from Cerificate Authorities i.e. Domain Validation : These types of certificate validations provide ssl encryption and certificate authority validates the ownership of the domain against the email address using whois record for the domain. This is the cheapest kind and the one I am using for this website at the moment. If you are committing financial transactions on your site its better to atleast get a OV certificate, which I explain next. Organisation Validation : These kind of certificate validations involve more extensive checks including in-person checks of your organisation’s details before a certificate is issued for your website. these are more secure. Extended Validation Certificates : These kind of certificates are issued after extremely intensive checks on your organisations. these are the most reliable certificates you can get. If your site uses this kind of certificate, it will get the elusive green bar in the address bar of your browser with your company name mentioned alongside. like all the bank websites get. Installing the certificate is quiet easy. First test that things work with ssl on your nginx server. First of all create directory to hold the key and certs: mkdir /etc/nginx/ssl create a key and unsigned certificate file for yourself: sudo openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout /etc/nginx/ssl/