[Ubuntu] Wireless stop working after upgrade

If wireless fail to work after upgrade, be sure to use lspci | grep network to look for your wireless device and include this info when you post online for help.

If you're using Broadcom BCM4312 (full name: "Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)") same as mine, then you probably could easily fix by installing the following:

sudo apt-get install firmware-b43-installer b43-fwcutter

or try another one if the above doesn't work:

sudo apt-get install broadcom-sta-common

You're adviced to reboot your system, but before that you may try:

1. off & on your wireless device, it may work straight away without system reboot.
2. run command modprobe b43

If you choose to reboot and the wireless device doesn't start, try modprobe b43. To autoload the device at startup, edit /etc/modules, add "b43" to the list. That should load it during startup.

Good luck!

[Ubuntu] After upgrade cannot access internet despite connection is up

I upgraded our server last night via apt-get update & apt-get upgrade, when the server reboot it cannot connect to internet and other network segment. It can access only all the resources in the same subnet.

There are a few solutions worth to try:

• ifdown the network interface and ifup it again
• when perform upgrade of Ubuntu, the system might modified /etc/resolv.conf to include 127.0.0.1 as nameserver. Sometimes this will mess thing up and you can't get online. You can either delete everything inside, or use google DNS: nameserver 8.8.8.8
• if you have bonding, you might want to add dns-nameserver 8.8.8.8 8.8.4.4 under your bond0
• restart your networking: restart networking (this could be different from reboot Ubuntu. Because my connection got fix by restarting the network, while reboot doesn't help at all

If you do not wish to tackle with all this stupid problem, my advice is only upgrade when you need it. As long as your server is running fine and the upgrade is not going to fix any issues, just keep it as it is.

[Ubuntu] Wireless not working when on battery

If you have read my previous post How to release/renew IP when dhclient doesn't work, but you still unable to use your wireless when running your laptop on battery mode, then it could have something to do with the power management in Ubuntu.

The symptom you might get is:

1. the wireless IP cannot be renew/release
2. the wireless connection is up, but you can ping local or internet
3. the wireless takes forever to get an IP from your router

The reason behind is when you're on battery, Ubuntu will activate power saving on your wireless device. This made the device cannot function properly. In this case my wireless device is:

"Broadcom Corporation" "BCM4312 802.11b/g LP-PHY" -r01 "Foxconn International, Inc." "T77H030.00 Wireless Mini PCIe Card"

If you are asking for help, you can identify your network controller by enter this command in terminal (special thanks to Serendah Linux from Ubuntu Malaysia LoCo Team to provide this command):

lspci -mm | grep Network | sed 's/.*"Network controller" //'

There are some solution that propose to deal with the 'wireless' file in the following location

• /etc/pm/power.d
• /usr/lib/pm-utils/power.d

but those doesn't work for me, and it might happen to you as well. If that is the case, you can still solve it by manual enter the following command into terminal:

• iwconfig eth1 power off

Please note that the "eth1" has to be your wireless interface. Some might name after "wlan1". You have to enter the command every time you reboot a new session. I have not found any working method to execute this command during start up, if you do found it, please share with me.

[Fedora] Laptop Broadcom Wireless not working?

The downside of Fedora compared to Ubuntu on my laptop is the Broadcom BCM4312 wireless device doesn't install automatically, that mean I'm unable to turn on my wireless for net browsing.

Luckily, how-to instruction is well documented in FedoraForum.org:
http://forums.fedoraforum.org/showthread.php?t=239922

[CentOS] Installing CentOS 6.3 Minimal Edition: Part 1

In this post I would list down the steps & tasks I performed after during and after successful installation of CentOS minimal edition.

During Installation
I install CentOS 6.3 in a VM via Oracle VirtualBox. The initial graphic RAM given was 12mb, that has caused CentOS setup fail to boot into a GUI installation. Installing from the old DOS-like environment is headache because somehow it does not show up any available drive for me to select to hold the CentOS.


After a few trials, I decided to re-configured and install in GUI environment. The installation went smooth and very quickly it is done and CentOS is up.

* One thing to take note during the installation is to setup the LAN connection otherwise you would not get connection once boot into CentOS. (Special thanks to Sharuzzaman Ahmat Raslan from Facebook General Linux Discussion M'sia for his advice and screenshot)

To setup the LAN, simply click on the "Configure Network" button on the bottom left.

 

After installation
Once CentOS boot up I'm required to login. Key in root and password (set during installation) then we can start to install everything.

****** This step only required if you forgot to setup LAN during installation ******

Before that I would need to bring up the network interface. I used NAT for the VM. The network interface is not up by default, I did ifconfig and only can see "lo". To bring up the network interface simply type:

# ifup eth0

Run ifconfig to check again and now eth0 has already up and running with DHCP.

****** End of network interface section ******

First thing to do is to perform update to overall system.

# yum update

It is easier and more straight forward to work under GUI than terminal mode. So I decided to install the Gnome Desktop Environment & KDE. The reason I install both because there are some KDE tools & programs are useful to me. Before we can install Gnome/KDE, we must first install the "X Windows System". Yum has an option to do groupinstall. It will help you resolve all dependencies, for novice users this come in very handy. Execute the following:

# yum groupinstall -y 'X Window System'

So what is mean by "-y" in the command line above? It means "answer yes to all", so the system will perform every resolved dependencies without getting further permission from me.

To install Gnome, execute:

# yum groupinstall -y 'Desktop'

* A reminder here: Restart is not required after install "X Window System". If one restarts the system, remember to bring up eth0 again.

Once the installation done, execute:

# startx

I'm now in the Gnome Desktop environment. To make sure it run every time we restart the system, simply go /etc/inittab and change the id:3:initdefault: to id:5:initdefault:.

* To change and save the inittab file, we can use:

# vi innittab

press "Insert" on keyboard to enter editing mode. Once done, press ESC and type ":wq".

Reboot with command init 6 and I can now work in desktop environment.

===============================
There are some issue with minimal edition of CentOS that is it comes with very limited tools we can use to configure the OS. The most critical stuff that are missing is text editor such as gEdit / Kedit / Leafpad. Personally I prefer Leafpad, but to install Leafpad it is not as straight forward.

Some other issue:

1. the network interface is not configure to load automatically when OS starts
2. Mozilla Firefox is not pre-install

I will cover in Part 2 how to install those missing stuff as well as configure the network interface so it loads with the system.

Until then, have fun with your newly installed CentOS!

===============================
Some useful links for reference:

• Yum introduction: http://yum.baseurl.org/wiki/YumGroups
• Yum maintenance: http://www.centos.org/docs/5/html/yum/sn-yum-maintenance.html
• Automatic update and retrieval and installation: http://www.cyberciti.biz/faq/fedora-automatic-update-retrieval-installation-with-cron/

[Ubuntu] Bonding - ALB and 802.3ad

Update 31/07/13: Be sure to install ifenslave before configuring the bonding.

Office network switch was upgraded to layer 3 switch recently, play around with bonding to create link aggregation. This can be done easily under Windows, but in Linux it is really big headache. Not because the steps are complicated and redundant, but you simply can't proof whether the configuration is working or not because Linux doesn't have a friendly way for user to check whether the bonding is up and running fine.

We can check under /proc/net/bonding/bonding, but even if it is up and running, it doesn't mean the networking is actually well connected.

By the time I write this article, I still unable to get it run fine, probably due to the switch is not well configured yet, waiting for technician to do a check on that. Meanwhile, I would like to share my /etc/networking/interfaces configuration here, so whoever encountered Linux bonding problem can refer to here, without the need to search for thousand solutions online but none of those are beginner friendly or prove working.

I would say the configuration below "should be working", due to the fact that such configuration appear working when we do "netstat -i" or "ifconfig". There are a lot of solutions online, some help you to understand the concept but can never get the "bond0" interface up.

Without more words, here we go:

Adaptive Load Balancing, bonding mode=6

 auto lo  
 iface lo inet loopback  
 auto bond0  
 iface bond0 inet static  
      slaves none  
      address 192.168.0.2  
      gateway 192.168.0.1  
      netmask 255.255.255.0  
      dns-nameservers 8.8.8.8  
      bond-mode 6  
      bond-miimon 100  
 auto eth0  
 iface eth0 inet manual  
      bond-master bond0  
      bond-primary eth0 eth1 eth2 eth3  
 auto eth1  
 iface eth1 inet manual  
      bond-master bond0  
      bond-primary eth0 eth1 eth2 eth3  
 auto eth2  
 iface eth2 inet manual  
      bond-master bond0  
      bond-primary eth0 eth1 eth2 eth3  
 auto eth3  
 iface eth3 inet manual  
      bond-master bond0  
      bond-primary eth0 eth1 eth2 eth3  

802.3ad Link Aggregation, bonding mode=4

 auto lo  
 iface lo inet loopback  
 auto bond0  
 iface bond0 inet static  
      slaves none  
      address 192.168.0.2  
      gateway 192.168.0.1  
      netmask 255.255.255.0  
      dns-nameservers 8.8.8.8  
      bond-mode 4  
      bond-lacp-rate 1  
      bond-miimon 100  
 auto eth0  
 iface eth0 inet manual  
      bond-master bond0  
      bond-primary eth0 eth1 eth2 eth3  
 auto eth1  
 iface eth1 inet manual  
      bond-master bond0  
      bond-primary eth0 eth1 eth2 eth3  
 auto eth2  
 iface eth2 inet manual  
      bond-master bond0  
      bond-primary eth0 eth1 eth2 eth3  
 auto eth3  
 iface eth3 inet manual  
      bond-master bond0  
      bond-primary eth0 eth1 eth2 eth3  

I hope the above will help one who stuck with bonding. If this doesn't work properly and better solution is found, I would greatly welcome feedback and input.

Enjoy bonding!

========================================

Update 24/12/12:
The bonding configuration above is proven working, the issue I encountered was caused by the Dell PowerConnect layer 3 switch, which has some unknown issue that made the ports reserved for LACP not working properly. Re-configure and restart has get it up and running.

One more matter to take note is that you can actually remove the "bond-primary" under each eth. As for the dns-nameservers, it is advisable to specify that. Without that we have encountered some strange issue with VMs:

1. the host and guest OS cannot ping and see each others.
2. there is a "ghost" IP address, 192.168.0.222 appeared and tie with one of the ethernet. Bring up/down the bonding as well as each ethernet cannot get rid of it. Not even after restart.

Issues above being solved once the dns-nameservers is specified.

Now my server is running @ 4 Gbps and the HDDs has now become the bottleneck. Sigh... it's time to upgrade!