Feed on
Posts
Comments
  1. Download the ASA 8.42 files (asa842-initrd.gz and asa842-vmlinuz) for GNS3 from a reputable source (I got mine from http://www.mediafire.com/download.php?l010dd0c1nayf0d)
  2. Open Edit -> Preferences -> Qemu and click the ASA tab
  3. Enter an Identifier name – I used “asa842”
  4. Enter 1024 in RAM
  5. Enter the following for Qemu Options:
    -vnc none -vga none -m 1024 -icount auto -hdachs 980,16,32
  6. Enter the paths where you placed the files from step 1 into the designated boxes for Initrd and Kernel
  7. Enter the following for Kernel cmd line:
    -append ide_generic.probe_mask=0x01 ide_core.chs=0.0:980,16,32 auto nousb console=ttyS0,9600 bigphysarea=65536
  8. Leave all other options at defaults
  9. Click the Save button then click OK
  10. Add an ASA to a new project/topology and start it (a terminal window should appear – if you used the defaults for the GNS3 install on Windows 7, then the terminal emulator will be putty)
  11. Once the ASA is up, enter enable and then enter the following to activate features (these activation keys might take a long time to apply – meaning ~5-15 minutes, so be patient):
    activation-key 0x4a3ec071 0x0d86fbf6 0x7cb1bc48 0x8b48b8b0 0xf317c0b5
    activation-key 0xb23bcf4a 0x1c713b4f 0x7d53bcbc 0xc4f8d09c 0x0e24c6b6
  12. Add a loopback adapter to Windows:
    Open a command prompt as Administrator
    Enter hdwwiz.exe to open the Add Hardware Wizard
    Once the Add Hardware Wizard is open, click Next
    Choose “Install the hardware that I manually select from a list (Advanced)” and click Next
    Select “Network adapters” and click Next
    Select “Microsoft” and “Microsoft Loopback Adapter” under Manufacturer and Network Adapter respectively, then click Next
    Reboot
  13. After reboot, add an ASA to a topology and start it
  14. Add a Cloud Object to the topology and right-click to Configure, selecting the name you used for the Cloud Object – probably C1 if it’s the first Cloud Object and you didn’t rename it
  15. Select the loopback adapter that you created in Step 12 and click the Add button
  16. Add an Ethernet switch to the topology and draw a direct connection from the switch to the ASA and switch to the Cloud Object
  17. In the ASA console:
    config t
    int gi 0
    ip address 10.10.10.1 255.255.255.0
    nameif management
    no shut
  18. Open Network and Sharing Center in Windows and change the IP of the loopback adapter to 10.10.10.2/24.
  19. Ping the Windows loopback adapter from the ASA firewall to test connectivity.
  20. If you don’t already have a tftp server installed, then install one. I use the free one from Solarwinds, but there are a few other good options.
  21. If you don’t already have the ASDM, then download it from Cisco or another reputable source.
  22. In the ASA console, copy the ASDM bin file to flash on the ASA:
    copy tftp://10.10.10.2/asdm-711.bin flash
  23. Set the ASA to load the ASDM during the next boot
    config t (if you’re not already in config mode)
    asdm image flash:asdm-711.bin
    http server enable
    http 10.10.10.2 255.255.255.255 management
    username <user of your choice> password <password of your choice> privilege 15
  24. Reboot the ASA to ensure the ASDM image is loaded during boot.
  25. Browse to https://10.10.10.1 using the browser of your choice and click the Install ASDM Launcher button to download and install the ASDM app from the ASA.
  26. Enjoy!

Note: Just for giggles, I ran through these exact instructions on my now Windows 8.1 laptop running GNS3 0.8.6 all-in-one and it worked without a hitch!  For those running into networking problems – probably can’t ping the loopback from the ASA or vice versa – check Windows Firewall and make sure the IP addresses you use are not in use on other segments in your own routed network…

After spending a few minutes following the erroneous/incomplete (?) official documentation from Google for configuring Pidgin for Google Apps accounts, I started searching more widely and found this blog article (thanks neale!) that provides the correct way to configure Pidgin for Google Apps users.  I find it quite strange that Google doesn’t have the correct documentation…  Here is a short excerpt with small modifications from that blog article – just so that it’s here should that blog disappear…

How to configure the account

You’ll want to load the “Modify Account” screen (assuming the account is already created). That can be accessed by going to the Accounts menu, selecting the account in question, and choosing “Edit Account” from the list of options.

Once the screen is loaded, click on the Advanced tab. You’ll be presented with a number of different configuration options. The following list contains the settings I updated, along with what I set their values to. Any omitted settings can be left as-is.

  • Connection security: Use old-style SSL (ATTN: the default of “require encryption” had to be changed)
  • Connect port: 5223 (ATTN: the default of 5222 had to be changed)
  • Connect server: talk.google.com

With those changes in place, Pidgin connected to Google Talk without error.

Note: These steps were performed on Pidgin 2.7.9-5.el6.2. If you’re using a different version of Pidgin, your mileage may vary.

In the course of running my home lab on the latest VMware hypervisor (ESXi 5.1.0 799733), I thought it prudent to evaluate the install and function of the VMware Tools package for a CentOS 6.3 guest. Here’s how I got her done:

  1. Add the VMware GPG keys (optional, but a good idea):
    rpm --import http://packages.vmware.com/tools/keys/VMWARE-PACKAGING-GPG-DSA-KEY.pub
    rpm --import http://packages.vmware.com/tools/keys/VMWARE-PACKAGING-GPG-RSA-KEY.pub
  2. Create the vmware-tools.repo in /etc/yum.repos.d/ with the following contents:
    [vmware-tools]
    name=VMware Tools
    baseurl=http://packages.vmware.com/tools/esx/5.1latest/rhel6/$basearch
    enabled=1
    gpgcheck=1
  3. Install the VMware tools core package with dependencies:
    yum install vmware-tools-core

From now on, any time the WMware tools for ESXi 5.1 are updated, you can update them via the usual yum update method.  Bear in mind that if you upgrade your ESXi install, you’ll need to manually update the baseurl variable in /etc/yum.repos.d/vmware-tools.repo.

*Note: there are additional packages available should you require more than the core functionality of VMware tools – you can view them by browsing the packages at http://packages.vmware.com/tools/esx/5.1latest/rhel6/ or by running yum search vmware.

After battling for a little while on this and referring to many docs provided by Perle, I decided to find the Cisco console pinout from Cisco and just marry up the functions on the Perle pinout diagrams with them.  After that, bingo!  For anybody else that might be looking for a more simple description of the wiring necessary to connect most Cisco switches and routers to an IOLAN STS16 (or similar), here it is:

IOLAN RJ-45 Plug
Pin | Function | Color
1 | GND | White-Orange
2 | RTS | Orange-White
3 | DSR | White-Green
4 | TXD | Blue-White
5 | RXD | White-Blue
6 | GND | Green-White
7 | CTS | White-Brown
8 | DTR | Brown-White

CISCO RJ-45 Plug
Ping | Function | Color
1 | CTS | Orange-White
2 | DTR | White-Green
3 | TXD | White-Blue
4 | GND | Green-White
5 | NC/GND | White-Orange
6 | RXD | Blue-White
7 | DSR | Brown-White
8 | RTS | White-Brown

I’ve been using Komodo Edit for the past few weeks to create/edit scripts – just don’t want to forget this option should the related synapses stop firing as well as I might hope…

http://www.activestate.com/komodo-edit

I downloaded the x86_64 fc16 src rpms from http://code.google.com/p/exfat/downloads/list (0.9.7-1 at the time) and built them on CentOS 6.3 x86_64, which worked like a charm.  Pre-reqs of auto-buildrequires fuse-devel scons gcc packages are necessary, so as root or sudo:
yum install auto-buildrequires fuse-devel scons gcc
rpm -ivh fuse-exfat*.src.rpm exfat-utils*.src.rpm

Then hop into ~/rpmbuild/SPECS and:
rpmbuild -ba fuse-exfat.spec

watch and wait, then:
rpmbuild -ba exfat-utils.spec

watch and wait, then (if all went well in the rpmbuilds, of course):
cd ~/rpmbuild/RPMS/x86_64
yum install exfat-utils*.rpm fuse-exfat*.rpm

or you could just cheat and download them here (built on 2.6.32-279.2.1.el6.x86_64):
fuse-exfat-0.9.7-1.el6.x86_64
exfat-utils-0.9.7-1.el6.x86_64 

  1. Login as root and run the following (accept all dependencies):
    yum install python python-devel xorg-x11-proto-devel libXext-devel gcc-c++ libXrender* PyQt4 PyQt4-devel qt qt-devel qemu-img libvirt
    Note: You need to pay attention to the output from yum as the availability of the required packages can’t be guaranteed – you might need to enable some 3rd-party repos and/or download some packages directly using RPMFind.net.
  2. Download the latest GNS3 source, unpack it to /opt, create symbolic link, create subfolders and set permissions (at this time, the GNS3 version is 0.8.3, but a newer version might be available – it’s your call as to which version to use):
    wget http://iweb.dl.sourceforge.net/project/gns-3/GNS3/0.8.3/GNS3-0.8.3-src.tar.gz
    tar -xvf GNS3-0.8.3-src.tar.gz -C /opt
    cd /opt
    ln -s GNS3-0.8.3-src GNS3
    cd GNS3
    mkdir Dynamips IOS Project Cache Temp
    chmod o+rw Project Temp 
  3. Change directory into Dynamips, download the binary and make it executable (at this time, the Dynamips version is 0.2.8-RC3, but a newer version might be available – it’s your call as to which version to use and the URL to download it):
    cd Dynamips
    wget http://downloads.sourceforge.net/project/gns-3/Dynamips/0.2.8-RC3-community/dynamips-0.2.8-RC3-community-x86_64.bin
    chmod +x dynamips*.bin
  4. Download GNS3 icon from here and link in the right locations:
    cd /opt/GNS3
    wget http://www.rehmert.com/wp-content/uploads/2012/08/gns3-150x150.png
    ln -s /opt/GNS3/gns3-150x150.png /usr/share/icons
    ln -s /opt/GNS3/gns3-150x150.png /usr/share/pixmaps
  5. Create a /usr/bin/gns3 with the following content:
    #!/bin/bash
    python "/opt/GNS3/gns3"

  6. Set +x on /usr/bin/gns3:
    chmod +x /usr/bin/gns3
  7. Create app for use in app menu and launcher creation
    Create /usr/share/applications/gns3.desktop with the following contents:
    [Desktop Entry]
    Name=GNS3
    Comment=GNS3
    Exec=gns3
    Icon=gns3-150x150.png
    Terminal=0
    Type=Application
    Encoding=UTF-8
    Categories=Development
  8. Now you’ll find GNS3 listed in the Applications -> Programming menu location and can create application launchers in panels or on the desktop with ease…
  9. Edit /opt/GNS3/src/GNS3/Node/AbstractNode.py to comment out the following lines:
    if QtCore.QT_VERSION >= 0x040600:
    flags = flags | self.ItemSendsGeometryChanges

    To avoid the following error message:
    AttributeError: 'xxxxxxxxxxx' object has no attribute 'ItemSendsGeometryChanges'

Back to the blog…

I took a long hiatus from blogging in order to give other alternatives (Facebook, Twitter, etc.) their fair shake, but I’ve just found too many annoying quirks (unnecessary functionality changes, no communication regarding updates to platforms, restrictions on post and file (photos, videos, etc.) sizes, data not backed up/guaranteed, etc.) with all of them that point me back to running my own blog.  Don’t get me wrong, those social apps have their place, but I’ll be making less use of all of them now – probably just posting links back here…

With the arrival of our twins (Avery & Tyler) on September 20th, I’ll have far less available space in my brain, so this will be near-line storage for the overflow…

Fair warning: I’m going to voice my opinions here – probably in raw form…  If you find that troubling, change the channel to fluffy puppies or laughing babies…

« Newer Posts