Tag Archives: network

Acer Aspire One AOD250 Wired Network Fix

As an amendment to this post, I did find one technical issue.  Amusingly wireless networking worked immediately, but wired did not.  It is almost always the other way around for me.  However, there is a really great amount of documentation that exists for this:  http://ubuntuforums.org/showthread.php?t=1206649.  I am going to repeat the pertinent parts here:

tar -xvzf AR81Family-linux-v1.0.0.10.tar.gz
cd src
make
sudo make install
sudo modprobe atl1e

I received an error from the tar command, but I kept going and that worked exactly perfectly for me.  In fact, my wired network registered as connected immediately after running the last command.

Not only did I contribute a bug report, but got the joy of updating the Hardware wiki:  https://wiki.ubuntu.com/HardwareSupport/Machines/Netbooks#Acer%20Aspire%20One.


Bonded Networking

Sometimes things are exactly as easy as they appear to be, and sometimes moreso.

I just followed this guide and now have bonded networking.  In theory, this means I have a 200Mbps connection to my network now.

Since I don’t like it when others point to a webpage and say that all they did was what was written, I’ll be more specific.

  1. I did nothing to my switch/router
  2. I installed ifenslave per the directions
  3. I took down my ethernet connections per the directions
  4. I copyed my /etc/network/interfaces file to a backup
  5. I edited the /etc/network/interfaces file to have the bond0 connection in it  (Ha!  This font makes that look like Bond-O — as in the car-body repair goop; it should be bond[zero])
  6. I brought the bond0 interface up
  7. hooray!

I think it took me longer to type this than to actually do it.

Update:  There was one catch.  My /etc/resolv.conf file ended up blank this morning (i.e., after rebooting).  I find this  a little odd, but I was easily able to fix it by adding the entries back into it.  I now have that backed up so I don’t have to reference my router for that information.


Static IP Configuration

I finally figured out how to get my static IP addresses set through the system configuration files.  I had to resort to this because KDE4 doesn’t have the nice networking interface that KDE3 did — they are still working on that.

There are two key files that come into play:  (1) /etc/resolv.conf and (2) /etc/network/interfaces.

/etc/resolv.conf

me@machine:~$ cat /etc/resolv.conf
# Generated by NetworkManager
domain home
search home
nameserver 71.243.0.12
nameserver 66.237.161.12
nameserver x.x.x.1

This file is pretty simple.  It is the list of domain name servers that help resolve things like http://www.cnn.com into an IP address.  I had to find these values from my router, and thankfully it was picking them up automatically from my new ISP.  I also added my router (x.x.x.1) to the file so it would resolve the names of the machines locally on my network.  I still need to use {machine-name}.local as the syntax, but it works (e.g., ping machine.local).

/etc/network/interfaces

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 120.30.90.140
netmask 255.255.255.0
network 120.30.90.0
broadcast 120.30.90.255
gateway 120.30.90.1

auto eth1
iface eth1 inet static
address 120.30.90.141
netmask 255.255.255.0
network 120.30.90.0
broadcast 120.30.90.255
gateway 120.30.90.1

This file was trickier.  It started out like this:

me@machine:~/junk/config-files/etc/network$ more interfaces-20090809-1
auto lo
iface lo inet loopback

That’s not a lot of information to work with, so a fair amount of searching was required to figure out how to get what I wanted.  All of that information is pretty simple, and helped me understand how some of this works. I don’t think I really need to use the “network” and “broadcast” attributes, but I chose to mostly out of a copy-and-paste coincidence

The final step was a reboot, because just restarting networking didn’t work (sudo /etc/init.d/networking restart).  There must be something cached that needs to be flushed to get this to work while the machine is running.  Something else for me to noodle out another day.

While this was fun for curiosity, the primary motivation for doing this was to hopefully fix my VMware networking problem. I’ll have to test that out later tonight or early tomorrow.