This procedure worked for me, please let me know if you encounter any issue and I’ll update it. Also, please tell me if you can make it work on Mac OS X Leopard (10.5.x).

Setting up Python

First, install zlib library:

wget http://zlib.net/zlib-1.2.5.tar.gz
tar xzf zlib-1.2.5.tar.gz
cd zlib-1.2.5
./configure --64
make
make test
sudo make install

Compile and install the latest version of python:

wget http://www.python.org/ftp/python/2.6.5/Python-2.6.5.tar.bz2
tar xvjf Python-2.6.5.tar.bz2
cd Python-2.6.5
./configure --with-universal-archs=intel --enable-universalsdk=/ --enable-shared
make
make test
sudo make install

Setting up Qt and PyQt

Install Qt libraries:

To limit the DMG size, I compiled a minimum of components.

wget http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.6.2.tar.gz
tar xvzf qt-everywhere-opensource-src-4.6.2.tar.gz
cd qt-everywhere-opensource-src-4.6.2
./configure -arch x86_64 -cocoa -no-dbus -no-cups -no-nis -no-openssl -no-scripttools -no-libtiff -no-libmng -no-script -no-javascript-jit -no-webkit -no-phonon-backend -no-phonon -no-audio-backend -no-multimedia -no-xmlpatterns -no-qt3support  -no-accessibility -opensource -no-dwarf2  -qt-libpng  -qt-libjpeg -no-multimedia -no-mediaservices
make
sudo make install

Install sip:

tar xvzf sip-4.10.2.tar.gz
wget http://www.riverbankcomputing.co.uk/static/Downloads/sip4/sip-4.10.2.tar.gz
python configure.py
cd sip-4.10.2
make
sudo make install

Install PyQt:

wget http://www.riverbankcomputing.co.uk/static/Downloads/PyQt4/PyQt-mac-gpl-4.7.3.tar.gz
tar xvzf PyQt-mac-gpl-4.7.3.tar.gz
cd PyQt-mac-gpl-4.7.3
python configure.py -q /usr/local/Trolltech/Qt-4.6.2/bin/qmake
make
sudo make install

Setting up Py2app

Install setup tools:

wget http://pypi.python.org/packages/2.6/s/setuptools/setuptools-0.6c11-py2.6.egg
mv setuptools-0.6c11-py2.6.egg.sh setuptools-0.6c11-py2.6.egg
sh setuptools-0.6c11-py2.6.egg

Install macholib:

mkdir macholib
cd macholib
svn co http://svn.pythonmac.org/macholib/macholib/trunk/ .
python setup.py install

Install a patched version of py2app with 64-bit support:

You will need to install mercurial if you haven’t already.

hg clone http://hg.hardcoded.net/py2app
cd py2app
python setup.py install

Making the DMG package

Now you can download the source and make the DMG. If you are interested in the details, have a look at setup.py where you can find every instruction to tell py2app how to make an Mac OS X application from GNS3.

wget http://code.gns3.net/gns3-devel/archive/tip.tar.bz2
tar xvjf tip.tar.bz2
cd gns3-devel-xxx
wget http://downloads.sourceforge.net/gns-3/dynamips-0.2.8-RC2-OSX-Leopard.intel.bin?download
mv gns3 gns3.py
python setup.py py2app

If everything work, you should find the DMG the the dist directory.

Method 1

• Install the Apple Devs Tools (on your Mac OS X DVD or download it on ADC account). Run and install XcodeTools.mpkg.

• Download Python 2.6 for MacOS X and install it.

• Download Qt librairies for Mac and install them.

• Download SIP, open a terminal and go in the folder where you downloaded the tar file and compile using the following commands (example for SIP 4.9.3):

Macintosh:$  tar xvzf sip-4.9.3.tar.gz
Macintosh:$  cd sip-4.9.3
Macintosh:sip-4.9.3$  python configure.py
Macintosh:sip-4.9.3$  make
Macintosh:sip-4.9.3$  make install

• Download PyQt and run the following commands to decompress and compile PyQt (example for PyQt 4.6.2):

Macintosh:$  tar xvzf PyQt-mac-gpl-4.6.2.tar.gz
Macintosh:$  cd PyQt-mac-gpl-4.6.2
Macintosh:PyQt-mac-gpl-4.6.2$  python configure.py
Macintosh:PyQt-mac-gpl-4.6.2$  make
Macintosh:PyQt-mac-gpl-4.6.2$  make install

• Download GNS3 source from our website or the development version and start the script named gns3.

Method 2

This method can take a few hours as everything is compiled but this is the most flexible as you can switch between dependencie versions very easilly.

• Download and install MacPorts (you will need the Apple Devs Tools).

• Open a terminal and install GNS3 dependencies.

Macintosh:$ sudo port install python26
Macintosh:$ sudo port install python_select
Macintosh:$ sudo python_select python26
Macintosh:$ sudo port install py26-sip
Macintosh:$ sudo port install py26-pyqt4
Macintosh:$ sudo port install qt4-mac

• Download GNS3 source from our website or the development version and start the script named gns3.

Notes about MacPorts

Optionnaly, to prevent MacPorts to install the last version of the dependencies (which may not work properly with GNS3), you can force a specified version with @.

Example:

Macintosh:$ sudo port install py26-sip @4.9.3_0
Macintosh:$ sudo port install py26-pyqt4 @4.6.2_0
Macintosh:$ sudo port install qt4-mac @4.5.3_0

Also, let say you have installed the latest version of Qt but this one doesn’t work very well with GNS3, you can revert back to your previous Qt version using the comand sudo port activate qt4-mac @version_number. This will automatically deactivate the current version of Qt and activate the one you want.

What is MRTG?

Installing MRTG

• Download MRTG from http://oss.oetiker.ch/mrtg/

• and follow installing instructions to install MRTG

Setup virtual topology

In this case we wan’t to make most simple example so we are using only one router:

• Install Ms loopback adapter to your Windows machine and configured IP-address 10.10.10.1/24 for it.

• Configure router:

hostname R0

!

interface FastEthernet1/0

ip address 10.10.10.2 255.255.255.0

duplex auto

speed auto

!

!

!

snmp-server community mycommunity RO

Verify that ping goes from your local computer to emulated router R0

Configure and run MRTG

• Follow MRTG guide: http://oss.oetiker.ch/mrtg/doc/mrtg-nt-guide.en.html

• After you have configured MRTG with command:

perl cfgmaker mycommunity@10.10.10.2 –global “WorkDir: c:\www\mrtg” –output mrtg.cfg

• Run MRTG with command:

perl mrtg mrtg.cfg

Every time when you run MRTG it will get data from the router and save it. You can run MRTG manually every 5 minutes or configure this to happen automatically. To do this follow MRTG instructions. When you have done this MRTG starts to build graph for you….

This Howto is still a draft and has been tested only on Linux.

Installation

First compile and patch Qemu as you would do for running JunOS. This will give us pcap, lcap and UDP tunnels (i.e. GNS3/Dynamips connections) capabilities.

Then obtain ASA itself. If you are smart and patient you will find it. I used asa802-k8.bin for my installations. As far as I know, nobody has been able to run ASA > version 8.2 (ASA keeps rebooting).

The next step is to get an initrd and a Linux kernel (inside the initrd) from your ASA image to use them with Qemu and also fix the initrd for our needs. The initrd is zipped and archived in the ASA image, we have to extract it.

There are 2 ways, manually or using a tool I created.

Manual method

Create an hexadecimal dump of your image:

hexdump -C asa802-k8.bin > asa802-k8.hex

Search for the ZIP header:

grep “1f 8b 08 00 1d” asa802-k8.hex
001228b0  1f 8b 08 00 1d 3d 73 46  00 03 ec 3a 6d 54 14 57  |…..=sF…:mT.W|

We can see that the ZIP file starts at offset 1228b0.

Let’s find the image size:

ls -la asa802-k8.bin
-rwxr-xr-x  1 root  staff  14524416 26 Nov 20:14 asa802-k8.bin
14524416 bytes.

Now we need to find out where in the file we can start extracting the ZIP part.

echo "14524416 ; ibase=16 ; last - 1228B0" | bc | tail -n 1
13334352

Extract the zipped part of the ASA image:

tail -c 13334352 asa802-k8.bin > asa802-k8.gz

Decompress it with gzip:

gzip -d asa802-k8
gzip: asa802-k8.gz: decompression OK, trailing garbage ignored

Make a temp directory and go into it so we can extract the files contained in the uncompressed archive file (the initrd):

mkdir tmp ; cd tmp

Now extract the archive with cpio (you must have the administrator rights to successfully extract device files).

cpio -i --no-absolute-filenames --make-directories < ../asa802-k8

Copy the Linux kernel to your previous directory:

cp vmlinuz ../asa802-k8.kernel

Before compressing back the initrd, create the following script in asa/scripts/first_start.sh

This script formats the 256 MB flash on first start to be used by ASA. Loads the network drivers modules for Intel e100 (i82559er in Qemu) and Intel e1000 cards and activates the network interfaces to be used in ASA. I noticed that if we immediately start ASA after this first boot, it freezes (don’t really know why but it seems the system do something and slow down during the first minute …). The next time you start the system, the script will still load the activate the network interfaces and automatically start ASA.

#!/bin/sh
 
##
## Author: Jeremy Grossmann (2009)
## Contributor: J. Pedro Flor (28 january 2010)
##
 
FIRST_START=no
if test ! -e /mnt/disk0/lina_monitor
then
 cd /asa/scripts/
 echo "d" > /asa/scripts/fdisk.pf.in
 echo "o" >> /asa/scripts/fdisk.pf.in
 echo "n" >> /asa/scripts/fdisk.pf.in
 echo "p" >> /asa/scripts/fdisk.pf.in
 echo "1" >> /asa/scripts/fdisk.pf.in
 echo "1" >> /asa/scripts/fdisk.pf.in
 echo ""  >> /asa/scripts/fdisk.pf.in
 echo "t" >> /asa/scripts/fdisk.pf.in
 echo "4" >> /asa/scripts/fdisk.pf.in
 echo "w" >>/asa/scripts/fdisk.pf.in
 
 echo ""
 echo -n "Initializing partition..."
 /sbin/fdisk /dev/hda < /asa/scripts/fdisk.pf.in > /dev/null 2> /dev/null
 echo "done"
 
 echo ""
 echo -n "Formating and mounting partition..."
 mkdosfs -F 16 /dev/hda1 > /dev/null 2> /dev/null
 mount -t vfat -o umask=0000,noatime,check=s,shortname=mixed /dev/hda1 /mnt/disk0 > /dev/null 2> /dev/null
 echo "done"
 echo ""
 
 cp /asa/bin/lina /mnt/disk0/lina
 cp /asa/bin/lina_monitor /mnt/disk0/lina_monitor
 FIRST_START=yes
fi
 
# load drivers
modprobe e100
modprobe e1000
ifconfig eth0 up
ifconfig eth1 up
ifconfig eth2 up
ifconfig eth3 up
ifconfig eth4 up
ifconfig eth5 up
 
if test $FIRST_START = yes
then
 echo ""
 echo "          Cisco ASA with <NO> Multiple Security Contexts"
 echo "          =============================================="
 echo ""
 echo "This is your first boot, please wait about 2 minutes for 'disk0' creation"
 echo "and then execute the following commands inside the Linux prompt:"
 echo ""
 echo " # cd /mnt/disk0"
 echo " # /mnt/disk0/lina_monitor"
 echo ""
 echo ""
 echo ""
 echo "Please note to use the following command under ASA to save your configs:"
 echo ""
 echo " ciscoasa(config)# boot config disk0:/.private/startup-config"
 echo " ciscoasa(config)# copy running-config disk0:/.private/startup-config"
 echo ""
 echo ""
 echo ""
 echo "To get webvpn working, execute the following commands:"
 echo ""
 echo " ciscoasa# mkdir disk0:/var"
 echo " ciscoasa# mkdir disk0:/var/log"
 echo " ciscoasa# mkdir disk0:/csco_config"
 echo " ciscoasa# mkdir disk0:/csco_config/97"
 echo " ciscoasa# mkdir disk0:/csco_config/97/webcontent"
 echo ""
 echo "          ( Powered by Pedro Flor )"
 echo "          ( pedro.flor@gmail.com  )"
 echo ""
 exit
fi
 
echo ""
echo ""
echo "Starting Cisco ASA with <NO> Multiple Security Contexts..."
echo ""
 
cd /mnt/disk0
/mnt/disk0/lina_monitor

In order for the script to be loaded at startup, edit etc/init.d/rcS and change /asa/bin/lina_monitor by /asa/scripts/first_start.sh

Change first_start.sh permissions:

chmod 755 first_start.sh

Now you can compress all the file and have the initrd ready to use in Qemu:

find . | cpio -o -H newc | gzip -9 > ../asa802-k8.initrd.gz

Automated extraction method

TODO

Using ASA with Qemu

Create a FLASH (this is a virtual hard disk).

qemu-img create FLASH 256M

Then you can start Qemu.

qemu -hda FLASH -kernel asa802-k8.kernel -hdachs 980,16,32 \
-initrd asa802-k8.initrd.gz -m 512 -no-kqemu -nographic -append \
"console=ttyS0,9600n8 hda=980,16,32 bigphysarea=16384 auto nousb ide1=noprobe"

TODO: networking of ASA. Very similar with JunOS emulation.

Using ASA with GNS3

To be completed:

In Preferences -> Qemu -> Qemuwrapper section:

Set the path to Qemuwrapper (can be found in the GNS3 package)

Set the working directory (e.g. /tmp).

Set the path to your patched Qemu in “Path to Qemu”

In ASA section:

Set the paths to your initrd and kernel.

Drag and Drop an ASA symbol on the scene, start the firewall and telnet to it.

This article explain you how to emulate Juniper JunOS on a PC using Qemu. This is an updated and enhanced version of excellent howtos from Juniper Clue and Internetwork Pro as well as Himawan Nugroho’s blog. I mainly focused on Qemu, so if you wish to install JunOS on a real PC or using VMware, please have a look at the Juniper Clue article for more information (and of course Google).

So what’s new you would say? First, I chose to use the latest version of Qemu: the 0.11.0 which supports the Intel e1000 network card emulation since version 0.10.0. and includes several fixes for it. I have modified and adapted the old patch for Qemu 0.11.0, it includes the UDP tunnel (connection to Dynamips/GNS3), PCAP and LCAP support. Also, the patch allows multicast traffic with the e1000, i82557b and i82559er Qemu emulated network cards. Moreover, this article show how to emulate JunOS on multiple operating systems: Mac OS X, Windows XP and Linux Ubuntu 9.04 without using an untrustworthy obscure binary downloaded from a forum you can’t even read the language

Disclaimer

Please note that JunOS is not provided and will not be. So please don’t ask. Also, I do not take any responsibility on what happen on your PC, keep in mind this howto requires some patience and that is not for complete beginners. Moreover, this howto doesn’t necessarily present the best and/or easiest way to emulate JunOS. This is the cleanest and less intrusive for me but please feel free to give me constructive comments and tell what worked or didn’t worked for you.

What is a Olive?

This is very well summarized on the JuniperClue website:

Olive is also the codename name given to JUNOS software running on an PC rather than a Juniper router. A common misconception is that Olive is some sort of “special software”, but it is actually ordinary JUNOS software running on a PC of similar specifications to a Routing Engine, with no forwarding hardware (or PFE) attached. If you took a Routing Engine out of a Juniper router and booted it in a blade server chassis, it would effectively be an Olive.

Juniper originally developed Olive functionality as a software development platform, before its hardware product was fully implemented. It is not intended as a “router simulator”, and has never been a supported product, or intended for use by the general public in any way. At one point it was used by Juniper internally for lab work, but has largely been phased out of this role with the availability of low-end hardware based platforms such as the M5.

The most common use of the Olive platform is for creative and unix-competent hackers to learn the JUNOS CLI on a low-cost platform. It is capable of forwarding a small amount of traffic, but does not support many of the features found on real Juniper routers. Essentially the forwarding on an Olive is the same as routing traffic via your fxp0 or em0 management interface on a real Routing Engine.

Ok so why all the secrecy?

Again, JuniperClue explained all of this:

Juniper’s official position is that Olive does not exist. Considering that Olive is an unsupported and unsupportable platform using “free” (aka illegally licensed) software, this is not an unreasonable official position. Olive is essentially a hackers platform, with absolutely no support of any kind, and it is not suitable for any type of commercial use. If you are in any doubt, or if you are not able to figure it out, you should invest in a low-cost platform such as J-Series instead.

It is also important to remember that Olive exists because Juniper allows it to exist, and is a testament to the mutual respect between the extremely knowledgeable developer and user bases. If the Olive platform became widely abused, Juniper could easily add additional software checks to prevent it from working. Please do not abuse this feature by doing stupid things like contacting JTAC for support on an Olive, or selling illegal copies of the software as “router simulators”. This type of activity is likely to have serious legal consequences and/or provoke a justified response from Juniper, so just don’t do it.

]]> http://blog.gns3.net/2009/10/olive-juniper/feed/ 107