Skip to main content

GNS Installation on Fedora 19/18/17

What is GNS3 ?

GNS3 is an open source software that simulate complex networks while being as close as possible from the way real networks perform, all of this without having dedicated network hardware such as routers and switches.


Here are the Steps to install GNS on Fedora 17/18/19:
First of all we need to install the telnet and pyqt4:
Telnet will give us the access console of our network devices:
#yum install telnet pyqt4
Now download the GNS3 form below link:

http://sourceforge.net/projects/gns-3/files/GNS3/0.8.4/GNS3-0.8.4-src.tar.bz2/download

#tar -xjvf GNS3-0.8.4-src.tar.bz2

#cd GNS3-0.8.4-src/

#python2.7 setup.py build

#python2.7 setup.py install 

To emulate Cisco devices, We need dynamipsHere we can download the dynamips:

thanks for Huaren Zhong who is providing this repo.

[rpm-sphere]

name=RPM Sphere

baseurl=http://download.opensuse.org/repositories/home:/zhonghuaren/Fedora_18/

enabled=1

gpgcheck=0



Then install dynamips:
#yum install dynamips 


Now we can launch the gns from user prompt and should follow the instructions for IOS path and dynamips testings. 
#gns3 &
Have done. 






Comments

Post a Comment

Popular posts from this blog

Canonical Kubernetes Platform

Recently,  Canonical has announce the release of the Canonical Kubernetes Platform version 1.32, a robust and user-friendly solution for seamless cluster creation and management. This platform is designed to simplify the deployment and maintenance of containerized workloads, making it an ideal choice for both developers and enterprises. Here are some of the attracting features of this Platform.  ZeroOps with Built-in Essentials:  The platform comes pre-configured with critical components such as networking, DNS, metrics server, local storage, ingress, gateway, and load balancer, enabling immediate productivity post-installation. Simplified Installation and Maintenance:   Leveraging snap packages, the installation process is straightforward, and automated patch upgrades enhance security without manual intervention. Effortless Scalability:  Adding new nodes is seamless, and achieving high availability requires minimal effort, ensuring your infrastructure sca...

Docker Container Management from Cockpit

Cockpit can manage containers via docker. This functionality is present in the Cockpit docker package. Cockpit communicates with docker via its API via the /var/run/docker.sock unix socket. The docker API is root equivalent, and on a properly configured system, only root can access the docker API. If the currently logged in user is not root then Cockpit will try to escalate the user’s privileges via Polkit or sudo before connecting to the socket. Alternatively, we can create a docker Unix group. Anyone in that docker group can then access the docker API, and gain root privileges on the system. [root@rhel8 ~] #  yum install cockpit-docker    -y  Once the package installed then "containers" section would be added in the dashboard and we can manage the containers and images from the console. We can search or pull an image from docker hub just by searching with the keyword like nginx centos.   Once the Image download...

Remote Systems Management With Cockpit

The cockpit is a Red Hat Enterprise Linux web-based interface designed for managing and monitoring your local system, as well as Linux servers located in your network environment. In RHEL 8 Cockpit is the default installation candidate we can just start the service and then can start the management of machines. For RHEL7 or Fedora based machines we can follow steps to install and configure the cockpit.  Following are the few features of cockpit.  Managing services Managing user accounts Managing and monitoring system services Configuring network interfaces and firewall Reviewing system logs Managing virtual machines Creating diagnostic reports Setting kernel dump configuration Configuring SELinux Updating software Managing system subscriptions Installation of cockpit package.  [root@rhel8 ~] #  dnf   install cockpit cockpit-dashboard  -y  We need to enable the socket.  [root@rhel8 ~] #  systemctl enable --n...