{"id":1726,"date":"2021-03-14T16:27:42","date_gmt":"2021-03-14T15:27:42","guid":{"rendered":"https:\/\/grupp-web.de\/cms\/?p=1726"},"modified":"2021-03-20T12:05:23","modified_gmt":"2021-03-20T11:05:23","slug":"installation-of-cisco-packet-tracer-8-0-0-on-rpm-based-linux-systems","status":"publish","type":"post","link":"https:\/\/grupp-web.de\/cms\/2021\/03\/14\/installation-of-cisco-packet-tracer-8-0-0-on-rpm-based-linux-systems\/","title":{"rendered":"Installation of Cisco Packet Tracer 8.0.0 on RPM-based Linux-systems"},"content":{"rendered":"\n<p>This is an updated version of my &#8222;<a href=\"https:\/\/grupp-web.de\/cms\/2020\/01\/03\/installation-of-packet-tracer-7-3-on-rpm-linux-systems-without-alien\/\" data-type=\"URL\" data-id=\"https:\/\/grupp-web.de\/cms\/2020\/01\/03\/installation-of-packet-tracer-7-3-on-rpm-linux-systems-without-alien\/\">Installation of Cisco Packet Tracer 7.3.0 or 7.3.1 on RPM-Linux-Systems without alien<\/a>&#8220; to install Cisco Packet Tracer 8.0.0. It is the result of installing it on my own openSUSE Tumbleweed based systems.<\/p>\n\n\n\n<p>State of the openSUSE packages is around March, 2021. For other  RPM-based Linux distributions you have to look whether this works the same way. Especially the needed and already available libraries might differ in your system.<\/p>\n\n\n\n<p>Why was this necessary at all? Well &#8230; Cisco always only supported the Ubuntu distribution of Linux, although they always delivered the software with an installer, and not as .deb. or .rpm-package. Since Packet Tracer 7.x Cisco decided to go one step further, and to stop the development of the generic Linux installer &#8211; don&#8217;t ask me why. Instead since then they only deliver a DEB-package, that can not be installed directly on a lot of other Linux-distributions, especially not on RPM-based distributions. And for Packet Tracer 7.3.0 Cisco says that the software is only for Ubuntu 18.04.03 LTS, no idea which version of Ubuntu is the minimum for Packet Tracer 8.<\/p>\n\n\n\n<p>It is of course also possible to look for <code>alien<\/code>, a tool to install DEB-packets on RPM-based systems. But as <code>alien<\/code> is not in the standard repos for openSUSE Tumbleweed, and I also wanted to see for myself once the inside mechanisms of  a DEB-packet, I did this work that might work on several RPM-based distributions.<\/p>\n\n\n\n<p><strong>Disclaimer:<\/strong> Although I have tried to document all procedures properly, I do not take any responsibility for this tutorial.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Unpack DEB-file for Packet Tracer<\/h2>\n\n\n\n<pre class=\"wp-block-code\"><code>mkdir \/tmp\/PacketTracerInst\ncp PacketTracer_800_amd64_build212_final.deb \/tmp\/PacketTracerInst\ncd \/tmp\/PacketTracerInst\nar -xv PacketTracer_800_amd64_build212_final.deb\nmkdir control\ntar -C control -Jxf control.tar.xz\nmkdir data\ntar -C data -Jxf data.tar.xz\ncd data<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Remove current PT installation<\/h2>\n\n\n\n<p>The following commands normally need root-privileges. I personally prefer to switch to a root console. You can do this with <code>sudo -i<\/code> or <code>su -<\/code> (I always prefer <code>su -<\/code> over <code>sudo<\/code>, but this is your choice, just have a root shell).<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>andreas@r-andreas:\/tmp\/PacketTracerInst\/data&gt; su -\nPasswort: &nbsp;\n<strong>r-andreas:~ #<\/strong> cd \/tmp\/PacketTracerInst\/data\/\n<strong>r-andreas:\/tmp\/PacketTracerInst\/data #<\/strong><\/code><\/pre>\n\n\n\n<p>After you now have a root shell we start over in the above directory. It is assumed that you have the old installation in <code>\/opt\/pt<\/code><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>rm -rf \/opt\/pt\nrm -rf \/usr\/share\/applications\/cisco-pt.desktop\nrm -rf \/usr\/share\/applications\/cisco-ptsa.desktop\nrm -rf \/usr\/share\/applications\/cisco-pt7.desktop\nrm -rf \/usr\/share\/applications\/cisco-ptsa7.desktop\nrm -rf \/usr\/share\/icons\/hicolor\/48x48\/apps\/pt7.png\nxdg-desktop-menu uninstall \/usr\/share\/applications\/cisco-pt.desktop\nxdg-desktop-menu uninstall \/usr\/share\/applications\/cisco-ptsa.desktop\nxdg-desktop-menu uninstall \/usr\/share\/applications\/cisco-pt7.desktop\nxdg-desktop-menu uninstall \/usr\/share\/applications\/cisco-ptsa7.desktop\nupdate-mime-database \/usr\/share\/mime\ngtk-update-icon-cache --force \/usr\/share\/icons\/gnome\nrm -f \/usr\/local\/bin\/packettracer<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Installation of new PT-files<\/h2>\n\n\n\n<p>We are still in the directory <code>\/tmp\/PacketTracerInst\/data<\/code><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cp -r usr \/\ncp -r opt \/<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">In openSUSE-Tumbleweed &#8211; symlink for a needed library<\/h2>\n\n\n\n<pre class=\"wp-block-code\"><code>ln -s \/usr\/lib64\/libdouble-conversion.so.3.1.5 \/usr\/lib64\/libdouble-conversion.so.1<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">After the installation of files, update icon and file assocation<\/h2>\n\n\n\n<pre class=\"wp-block-code\"><code>xdg-desktop-menu install \/usr\/share\/applications\/cisco-pt.desktop\nxdg-desktop-menu install \/usr\/share\/applications\/cisco-ptsa.desktop\nupdate-mime-database \/usr\/share\/mime\ngtk-update-icon-cache --force --ignore-theme-index \/usr\/share\/icons\/gnome\nxdg-mime default cisco-ptsa.desktop x-scheme-handler\/pttp<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Symlink to PT-starter<\/h2>\n\n\n\n<pre class=\"wp-block-code\"><code>ln -sf \/opt\/pt\/packettracer \/usr\/local\/bin\/packettracer<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Environment settings<\/h2>\n\n\n\n<p>Lines to have in <code>\/etc\/profile<\/code>, or if supported the preferred placement is in <code>\/etc\/profile.local<\/code><\/p>\n\n\n\n<p>If you already had PT7 installed, you just need to edit two lines and change the version number from 7 to 8.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>PT8HOME=\/opt\/pt\nexport PT8HOME\nQT_DEVICE_PIXEL_RATIO=auto\nexport QT_DEVICE_PIXEL_RATIO<\/code><\/pre>\n\n\n\n<p>To get these settings active on your workstation, log off and log in again. Settings in the startup profiles, are then automatically done. Verify them with the commands <code>echo $PT8HOME<\/code> and <code>echo $QT_DEVICE_PIXEL_RATIO<\/code> in a command line shell. You should see the above values!<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">PT still not working?<\/h2>\n\n\n\n<p>If PT is still not starting after all this, you should have a deeper look what&#8217;s wrong with the installation. For this, go to <code>\/opt\/pt<\/code> and copy the text-file <code>packettracer<\/code>, already available in this place, to a file <code>ptdebug<\/code>. This can for example be done by using the command <code>cp -p \/opt\/pt\/packettracer \/opt\/pt\/ptdebug<\/code>. Then, in this new file, replace \/ remove all redirections in the last three lines. The redirections start with a greater sign <code>&gt;<\/code>. Including the <code>&gt;<\/code> remove the rest of the line. The relevant lines in the file should now be:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>#!\/bin\/bash\n\necho Starting Packet Tracer 8.0.0\n\nPTDIR=\/opt\/pt\nexport LD_LIBRARY_PATH=\/opt\/pt\/bin\npushd \/opt\/pt\/bin\n.\/PacketTracer \"$@\"\npopd<\/code><\/pre>\n\n\n\n<p>Then, still from a command line shell, go again to the directory <code>\/opt\/pt<\/code> (not in a root shell!) and there enter the command <code>.\/ptdebug<\/code>. In my situation, with a working PT installation, the output looks like this:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>andreas@r-andreas:\/opt\/pt&gt; .\/ptdebug \nStarting Packet Tracer 8.0.0\nQt WebEngine resources not found at \/opt\/pt\/bin\/resources. Trying parent directory...\nInstalled Qt WebEngine locales directory not found at location \/opt\/pt\/bin\/translations\/qtwebengine_locales. Trying application directory...<\/code><\/pre>\n\n\n\n<p>The above output seems to be the &#8222;normal&#8220; output of a working Packet Tracer. If anything else is shown, try to interpret the problem or send the output to someone for help.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Thanks<\/h2>\n\n\n\n<p>A huge thank you to those reporting me typos and errors in this tutorial, especially my team-mate <a rel=\"noreferrer noopener\" href=\"https:\/\/social.tchncs.de\/@toheine\" data-type=\"URL\" data-id=\"https:\/\/social.tchncs.de\/@toheine\" target=\"_blank\">Tobi<\/a>! He also created a nice installation script that uses the above commands to install Packet Tracer 8.0.0 very easy. <a rel=\"noreferrer noopener\" href=\"https:\/\/codeberg.org\/toheine\/pt-installer\" target=\"_blank\">The script is available here<\/a> and everyone is able to contribute special things for other Linux-distros that can not install Debian-packages.<\/p>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>This is an updated version of my &#8222;Installation of Cisco Packet Tracer 7.3.0 or 7.3.1 on RPM-Linux-Systems without alien&#8220; to install Cisco Packet Tracer 8.0.0. It is the result of installing it on my own openSUSE Tumbleweed based systems. State of the openSUSE packages is around March, 2021. For other RPM-based Linux distributions you have &#8230; <a title=\"Installation of Cisco Packet Tracer 8.0.0 on RPM-based Linux-systems\" class=\"read-more\" href=\"https:\/\/grupp-web.de\/cms\/2021\/03\/14\/installation-of-cisco-packet-tracer-8-0-0-on-rpm-based-linux-systems\/\" aria-label=\"Mehr Informationen \u00fcber Installation of Cisco Packet Tracer 8.0.0 on RPM-based Linux-systems\">Weiterlesen<\/a><\/p>\n","protected":false},"author":1,"featured_media":1729,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1726","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-allgemein"],"_links":{"self":[{"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/posts\/1726","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/comments?post=1726"}],"version-history":[{"count":7,"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/posts\/1726\/revisions"}],"predecessor-version":[{"id":1738,"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/posts\/1726\/revisions\/1738"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/media\/1729"}],"wp:attachment":[{"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/media?parent=1726"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/categories?post=1726"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/tags?post=1726"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}