Tag Archive for 'Linux'

How To: Cisco VPN Client On Ubuntu 7.04 (Feisty Fawn)

IMPORTANT UPDATE, SEE BELOW

So, I installed Ubuntu 7.04 Feisty Fawn beta about 2 months ago. I installed it on my notebook and one of my workstations, both of which had Windows installed previously. I’m not dual booting on those machine, they’re 100% Ubuntu now.

After getting everything setup and running nicely, I realized I had no way of connecting to the Cisco PIX VPN we have at work. This is really important for me to be able to do, my job depends on it. I immediately went to Google and started searching. Turns out a nice fellow named Alexander Griesser has created a patch for the Cisco VPN client. The most recent CIsco VPN client for linux won’t compile with kernels 2.6.19 or newer. There’s really not much of a difference between his instructions and this how-to. However, I’m including more detailed instructions for those who may not be familiar with compiling software on Linux.

Here’s the steps I took to get the Cisco VPN Client to work under Unbutu 7.04 (Feisty Fawn). Note: A $ at the beginning of a line signifies a command to be run from the terminal.

  1. Download vpnclient-linux-4.8.00.0490-k9.tar.gz (mirror) to your home directory.
  2. Open a terminal window and untar the vpnclient with the following command:
    $ tar xzf vpnclient-linux-4.8.00.0490-k9.tar.gz
    This will create a new folder called vpnclient in your home directory. Leave the terminal window open, you’ll need it later.
  3. Download the patch (mirror) and save it to the vpnclient folder that was created in step 2.
  4. Go back to your terminal window and move into the vpnclient folder:
    $ cd vpnclient/
  5. Now patch the Cisco VPN source with this command:
    $ patch < vpnclient-linux-2.6.22.diff
  6. Next we actually build the Cisco VPN client, issue this command:
    $ sudo ./vpn_install
    Just hit enter for everything it asks you, the defaults are all OK. You may see lots of warnings, but those are OK.
  7. The VPN client is installed, now we need to start it:
    $ sudo /etc/init.d/vpnclient_init start
  8. Place your .pcf configuration files in /etc/opt/cisco-vpnclient/Profiles/
  9. If your .pcf file is called myVPN.pcf, you’ll connect to the VPN with the following command:
    $ sudo vpnclient connect myVPN


That’s it! You should now be able to connect to your Cisco VPN with the official Cisco VPN client on Linux. This will probably work on pretty much any linux setup, not just Ubuntu.

UPDATE (8/18/2007):
Alexander Griesser released a new patch that works with kernel versions 2.6.22 and greater. The new patch is backwards compatible, so it also works with older kernels as well, such as 2.6.10 and 2.6.21. All the download links above point to the newest release of the patch. I’ll continue to update this how-to as he releases new patches.

UPDATE (10/04/2007):
Cisco has finally released a new version of their vpn client for Linux. This new version compiles on all the new 2.6.xx kernels without the need for patching! You can download it from Alexander’s site or you can get it right here.

UPDATE (12/29/2007): Alexander Griesser has a new project page for his Cisco VPN client patches. It contains basic usage information and will most likely always have the latest and greatest patch available for download. In addition to that, Alexander has a new patch to make version 4.8.01.0640-k9 of the Cisco VPN Client compile on 64bit systems. Again, you can download the latest Cisco VPN Client for linux from the following link:
http://www.longren.org/files/vpnclient-linux-x86_64-4.8.01.0640-k9.tar.gz

Popularity: 89% [?]

Some Uptimes

uptimesI like to know how long each of my boxes have been up and running. I really don’t care so much about Windows PC’s, but I really like knowing how long my Linux boxes have been up. Notifications of uptimes are very nice, if a server goes down, I’ll get an email letting me know it’s no longer up and running.

Anyway, for the last year and a half or more I’ve been using The Uptime Project from MrEriksson. I don’t think the project is being developed or even maintained any longer, but it still works very well. All you need to do is get a username and password then download the client for your operating system.

But, I just wanted to point out that one uptime, for router.longren.org. It’s got an uptime of 155 days, almost half a year, by far the best uptime for any box I’ve personally owned. The neat thing about The Uptime Project is that it records reboots and total downtime.

Popularity: 6% [?]

MySQL Is Huge

Take note of this graphic. Notice there’s been 3,775,826 queries processed by that MySQL server in a little more than 5 days. Nothing too impressive right? Right.
Lots of Queries

We know MySQL can handle many more queries than that in a much shorter period of time. What amazes me is how well MySQL performs on the server it’s running on. The box hosting that MySQL server is an old HP. It’s got 1 Pentium II 400mhz processor with 128Mb of RAM. And it serves data to anywhere between 10 and 14 seperate PC’s at any given point in time. In addition to that, this MySQL server also provides data to a web interface that is used by 50 or so people. The MySQL server pumps out about 500Mb worth of data every day.

MySQL never ceases to amaze me in what it can do on less than optimal hardware.

Popularity: 6% [?]

Slackware 11.0 Release Candidate 5

Slackware 11.0 Release Candidate 5 is here. Lots of updates to existing packages. Not many packages were upgraded. Patrick is giving the scouts honor that this will be the last RC before 11.0 final.

Head on over to the Slackware Blog to have a look at the full changelog entry. Hopefully we will see Slackware 11.0 released sometime next week or maybe even by the end of the week since we’ve seen such a long RC cycle. I don’t think we’ve seen anything greater than RC2 since Slackware 9.0 or so. It’s been a while since we’ve seen this many release candidates.

Popularity: 6% [?]

Slackware 11.0 Release Candidate 4

Slackware 11.0 Release Candidate 4 is out! This release sees kernel 2.4.33.3 included as the default. Soon after RC4 was made, Patrick made another small update to the ChangeLog:

Sun Sep 3 19:59:47 CDT 2006
a/udev-097-i486-8.tgz: Fixed a missing ‘[’ in rc.udev. Thanks to
guilherme for pointing out the error, and to J., who found the missing
‘[’. (It had fallen off my desk and ended up under a table)
kernels/System.map: Forgot to gzip a bunch of these. Thanks, Steve’o.

This should definitely be the last RC before Slackware 11.0 final is released. In the past two or three Slackware releases (10.0, 10.1, and 10.2), we’ve only seen 2 or 3 release candidates. I suppose there’s a chance we’ll see RC5 this time, but I’m thinking this RC4 will be the last. Probably see Slackware 11.0 final within a week and a half or so.

Popularity: 4% [?]

Slackware 11.0 Release Candidate 3

Slackware 11.0 Release Candidate 3 is here!! The 2.6 kernel was moved from /testing/ to /extra/. What’s that mean? Not much really, other than it’s considered to be more stable since it’s now in /extra/.

Head on over to the Slackware Blog for more details.

Popularity: 5% [?]



cheap xbox 360 games - buy from zavvi
cheap xbox 360 games - zavvi

mobile phones - Web Design - Flights - Loans - Loans - Scottsdale Landscaping
Bike Insurance - Landlords Insurance - Search Engine Marketing - Mobile Phone



people-charming