As I setup my laptop with Ubuntu 13.04, I did several things to configure my networking needs. This article attempts to document my setup.
If you want to see all of my setup, please checkout my Ubuntu 13.04 Install page.
For the most part, networking just works on the installation. The network manager works nicely and is your key to managing network connections. My laptop has handled switching between wireless networks fairly nicely as well as connecting to a USB Network device (my docking station).
This post will look at
I am having trouble connecting to an old client. I had it working on a previous version of Ubuntu, and now they have turned my access back on for some more work. Of course, it won’t work!
Here’s the troubleshooting story in case it helps anyone else:
You would think a stereotypical Linux user would not mind getting his hands dirty in the command-line trying to make a program work. Well, either this user is not typical or that’s not true. The LogMeIn Hamagi VPN solution seems to have some cool features, but the Linux client was painful to figure out. Some documentation or instructions would be nice, but I think a nice basic user interface would also be helpful. Command-line is cool, but I just need to get connected, and I don’t want to learn yet another networking tool to get where I need to go.
If you are attempting Hamachi, this blog post is your lifesaver:
Next task is finding the Linux client. They don’t have a production one, but they do have a beta version available. Check out their beta page: LogMeIn Labs & Betas. This part is awesome once you find it — choose your flavor, deb or rpm, they have it. The Deb worked great for me on Ubuntu x64 10.04.
After installing, it was like nothing happened. No new menu items show up in the menu. Well, don’t worry, it installs a service and a command line program. Here are the files shown in the package:
When the package installs, it starts the service. You can see it running here:
Now, you have it installed. You need to use the command-line program to connect. First, you simply need to connect to the LogMeIn server (everything goes through there server). Note that you don’t need a user name or any credentials for this part (that will come later). Here’s the command plain and simple:
sudo hamachi login
Now, if you have an account on LogMeIn, you need to “attach” to it. If you are connecting to someone else’s network, you can skip this step.
sudo hamachi attach <email_address>
As far as I can tell, the next command just sets a name for your client. This is the name that will appear in the administration pages online for LogMeIn Hamachi.
sudo hamachi set-nick <name>
In my case, I set my nickname to “stephen”:
Then, online it will show this name:
Now, the final step is to connect to the network. This is where it got really confusing for me. It was not the command or how to do anything, but the problem was just determining what network ID to use. So, let me walk you through how to figure out the ID.
The person with the account on LogMeIn who setup the network, will need to login and view the “My Networks” page. Then, click on the edit link next to the network:
Once you know this ID, you can simply run the command:
sudo hamachi do-join "<network ID>"
It may ask you the password for the network. The LogMeIn account holder can optionally setup the password. If no password was setup, just hit enter, and it will proceed. Here’s what the configuration looks like when you setup a network:
Now, you should be connected. You should have a new network interface in your network settings:
If you need to connect to other machines in the Hamachi network by IP address, you will need the LogMeIn account holder to give you those IP addresses. You talk to other machines via the IP address for the Hamachi network not the local network.
All in all, once you get it setup, it seems to work well. I don’t like the fact that you have to run the program as administrator. For my other VPNs, I don’t need super user access to configure or connect. I also don’t like having an extra service running in the background. Why can’t it just use the Network Manager Applet like the other VPNs?
Now, I would be amiss if I didn’t mention the GUI. I found a Community Thread that points to a front-end called Haiguichi. It has a Deb package that you can install, and that part worked fine. It gives you a new menu item under Applications > Internet > Haiguichi. I couldn’t get it to configure though, and I finally figured out the command-line, so I left it alone.
I have been long wanting a refresh button on the Network Manager. Apparently, I am not the only one who has thought that:
Here is the big argument against:
So, here is the situation — I am working at home connected to my home router. I pick up my laptop and leave it on while I drive to work. When I get to work, it still shows my home wireless network in the list. Then, at lunch, I pick up my laptop and take it to a restaurant that supports WiFi. Again, it is does not recognize the restaurant’s network. From what I read, it could take up to 6 minutes to rescan and see the new networks in those situations.
The solution might be to speed up the scan frequency so I don’t have to wait so long upon arriving at a new location. But, from what I read, that might have power management implications. If you scan too frequently it will never go into power saving mode? I don’t know, but for one thing, why can’t I control the scan frequency?
On the other hand, if I had an option to rescan, I could tell it when to scan without having it scan needlessly too frequently. Why should it scan every 15 seconds when I am at a restaurant that doesn’t have WiFi? When my battery was dying and only lasted 20 minutes, I wanted every ounce of power I could get! I understand making things automatic for the user, but sometimes it is better to let the user decide. The laptop will never know when I change locations like that unless maybe you add a GPS device to it.
Just my thoughts; can I have my refresh button?
Switch to our mobile site