Showing posts with label network. Show all posts
Showing posts with label network. Show all posts
Tuesday, 23 December 2014
How to RUN GNS3 with lower Memory and CPU consumption on a Laptop
New GNS3 Setup With Lower CPU Load and Lower Memory Consumption ..Try It !!!
Some Things I've learnt about GNS3
I am in no way an expert on GNS3, just a trainee 
below are a few things i have learnt lately. I thought it might be a
good idea to produce something like this. If everyone replied to it and
added a few tips of their own it could be turned into a CLN GNS3 tips
and tricks document.
GNS3 Web Sites
http://www.gns3.net GNS3’s primary Web site
http://wiki.gns3.net GNS3’s Wiki site
http://www.ipflow.utc.fr/index.php/Cisco_7200_Simulator Dynamips – the actual emulator
http://www.ipflow.utc.fr/blog/ Dynamips blog
http://dyna-gen.sourceforge.net/ Dynagen
http://www.ipflow.utc.fr/bts/ Dynamips/Dynagen bug tracking
http://7200emu.hacki.at Hacki’s forum
===
1. GNS3 has less chance of crashing if the bin files are unzipped.
2. Currently images for 2600 routers must be uncompressed to work with Dynamips.
3. To dramatically reduce the load on your processor, right click on the router and choose idle, after a few moments it will give you a list to choose from.
Choose the one with a * against it, if you don't see a * in the choice run it again.
4. If you don't need any special routers then use the same type on the whole lab, this will use far less processing power and memory.
5. To print out the diagram of your network click file then export, you can export all or just what is visible.
6. To move your router/routers/links etc click the left mouse button and draw around what you want to move, you can then move everything that is inside that shape.
7. I find that if you move around the interface identities they eventually go back to their original position. I don't move them anymore as it looks a bit
messy when that happens.
8. You can't use GNS3 for the SWITCH studies, GNS3 only has basic switch capabilities.
9. You can create computers and run ping's/telnet with VPC, the document attached shows you how, its very simple to follow. I did find that it takes a few times for it to accept being a cloud, once you click ok just open it back up and check it.
10. I personally find that it is best to connect your links between routers when they are switched off, sometimes i find it fails otherwise.
11. You can create a router to act like a pc, this is shown below but it is also in the document.
Router(config)# no ip routing Turns off IP routing function
Router(config)# interface fa0/0 Switches to FastEthernet interface
Router(config-if)# ip address address subnet_mask Assigns IP address and subnet mask to interface
Router(config-if)# no shutdown Turns interface on
Router(config-if)# exit Returns to global configuration mode
Router(config)# ip default-gateway gateway_address Configures the default gateway
Router(config)# ip http server Optional – starts http server process
===
12. You can connect GNS3 to real equipment, i have not done this yet myself, it is in the document attached how to do this.
13. When using windows 64 bit GNS3 will default to program files (x86). GNS3 is a 32 bit program for windows so point it to program files not the (x86).
14. I have a Lenovo Thinkpad with a i7 processor and 4GB of RAM. With 7 routers of the same type my processor is running between 8 and 15 %, my RAM consumption is around 2.3 to 2.8 GB. That is also using a few other programs on my laptop at the sometimes.
below are a few things i have learnt lately. I thought it might be a
good idea to produce something like this. If everyone replied to it and
added a few tips of their own it could be turned into a CLN GNS3 tips
and tricks document.http://www.gns3.net GNS3’s primary Web site
http://wiki.gns3.net GNS3’s Wiki site
http://www.ipflow.utc.fr/index.php/Cisco_7200_Simulator Dynamips – the actual emulator
http://www.ipflow.utc.fr/blog/ Dynamips blog
http://dyna-gen.sourceforge.net/ Dynagen
http://www.ipflow.utc.fr/bts/ Dynamips/Dynagen bug tracking
http://7200emu.hacki.at Hacki’s forum
===
2. Currently images for 2600 routers must be uncompressed to work with Dynamips.
3. To dramatically reduce the load on your processor, right click on the router and choose idle, after a few moments it will give you a list to choose from.
Choose the one with a * against it, if you don't see a * in the choice run it again.
4. If you don't need any special routers then use the same type on the whole lab, this will use far less processing power and memory.
5. To print out the diagram of your network click file then export, you can export all or just what is visible.
6. To move your router/routers/links etc click the left mouse button and draw around what you want to move, you can then move everything that is inside that shape.
7. I find that if you move around the interface identities they eventually go back to their original position. I don't move them anymore as it looks a bit
messy when that happens.
8. You can't use GNS3 for the SWITCH studies, GNS3 only has basic switch capabilities.
9. You can create computers and run ping's/telnet with VPC, the document attached shows you how, its very simple to follow. I did find that it takes a few times for it to accept being a cloud, once you click ok just open it back up and check it.
10. I personally find that it is best to connect your links between routers when they are switched off, sometimes i find it fails otherwise.
11. You can create a router to act like a pc, this is shown below but it is also in the document.
Router(config)# interface fa0/0 Switches to FastEthernet interface
Router(config-if)# ip address address subnet_mask Assigns IP address and subnet mask to interface
Router(config-if)# no shutdown Turns interface on
Router(config-if)# exit Returns to global configuration mode
Router(config)# ip default-gateway gateway_address Configures the default gateway
Router(config)# ip http server Optional – starts http server process
===
12. You can connect GNS3 to real equipment, i have not done this yet myself, it is in the document attached how to do this.
13. When using windows 64 bit GNS3 will default to program files (x86). GNS3 is a 32 bit program for windows so point it to program files not the (x86).
14. I have a Lenovo Thinkpad with a i7 processor and 4GB of RAM. With 7 routers of the same type my processor is running between 8 and 15 %, my RAM consumption is around 2.3 to 2.8 GB. That is also using a few other programs on my laptop at the sometimes.
Thursday, 28 August 2014
How Update DNS Records in Local Linux Machine - [ Ubuntu ]
Created Thursday 28 August 2014
By TDL Matias
***************************************************************
This tutorial is to use as my own keep track record of things I do everyday with Linux.. I had to install a new linux distro into a user computers, the distro in question was Ubuntu 12.04 - 64bit.
I have gave the machine a name = DevOps14 with IP 172.xx.xx.184 - The problem is that that same machine, had being installed on the intranet before with same hostname (DevOps14) and had assigned previously the IP address 172.xx.xx.185 ..
after installed, I tried to access it using the hostname, I was getting network names conflit errors ..
When I tried to ping it .. I was getting the following error ...
user@host1:~$ traceroute -n devops14.uk.domain
traceroute to devops14.uk.domain (172.xx.xx.185), 30 hops max, 60 byte packets
1 172.16.14.70 2996.257 ms !H 2996.201 ms !H 2996.180 ms !H
user@host1:~$ ping -c 3 devops14.uk.domain
PING devops14.uk.domain(172.xx.xx.185) 56(84) bytes of data.
From host1.uk.domain (172.xx.xx.xx) icmp_seq=1 Destination Host Unreachable
From host1.uk.domain (172.xx.xx.xx) icmp_seq=2 Destination Host Unreachable
From host1.uk.domain(172.xx.xx.xx) icmp_seq=3 Destination Host Unreachable
--- devops14.uk.domain ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2014ms
Then, I went and updated our DNS server records usind rndc tool ... Tried do ping the devops14 again .. but not avail ..
user@host1:~$ ping -c 3 devops14.uk.domain
PING devops14.uk.domain (172.xx.xx.185) 56(84) bytes of data.
From host1.uk.domain (172.xx.xx.xx) icmp_seq=1 Destination Host Unreachable
From host1.uk.domain (172.xx.xx.xx) icmp_seq=2 Destination Host Unreachable
From host1.uk.domain (172.xx.xx.xx) icmp_seq=3 Destination Host Unreachable
---devops14.uk.domain ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2000ms
pipe 3
Ok then ..IF I have updated the DNS - Records, theres no reason that I could not ping that machine right into the IP - 172.xx.xx.184 instead of 172.xx.xx.185 ... Something was no really adding up ...
So I went into https://www.google.com/ to investigate and se if someone had come accross the same issue it was then when I found in a Ubuntu forum [http://askubuntu.com/questions/414826/how-to-flush-dns-in-ubuntu-12-04 ]
That I had only to refresh the network DNS record on my local machine with this command.
user@host1:~$ sudo /etc/init.d/nscd restart
* Restarting Name Service Cache Daemon nscd [ OK ]
And then PING it again ....
user@host1:~$ ping -c 3 devops14.uk.domain
PING devops14.uk.domain (172.xx.xx.184) 56(84) bytes of data.
64 bytes from devops14.local (172.xx.xx.184): icmp_seq=1 ttl=64 time=0.582 ms
64 bytes from devops14.local (172.xx.xx.184): icmp_seq=2 ttl=64 time=0.139 ms
64 bytes from devops14.local (172.xx.xx.184): icmp_seq=3 ttl=64 time=0.103 ms
---devops14.uk.domain ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.103/0.274/0.582/0.218 ms
All working fine now ...
Monday, 19 August 2013
How To Install VMWare Tools v4 on Ubuntu 12.04 LTS Server
How To Install VMWare Tools v4 on Ubuntu 12.04 LTS Server and 12.10 Server
Originally posted by: Justin Schier
Last Updated: October 24, 2012
Tested With: Ubuntu 12.10 Server, Ubuntu 12.04 LTS Server, Ubuntu 12.04.1 LTS Server, Ubuntu 11.10 Server
All the guides I found on the Internet, including VMWare’s website were outdated in some way, so I decided to write a guide of my own. I just went through these steps from start to finish on a fresh server and had no problems. In about 5 minutes, you will be able to install VMWare Tools on Ubuntu Server.
- Use Install VMWare Tools option in VMWare Client to attach media
- Update the server
- Create the mount point
- Mount the ISO
You should see the message: mount: block device /dev/sr0 is write-protected, mounting read-only - Change Directory
- Copy the tar file to your /tmp directory
- Install Build tools if necessary
- Change Directory
- Unmount the ISO
- Expand the tar
- Change Directory
- To prevent a potential error in the install script on Ubuntu 11.10+, create a special directory
Unable to create symlink “/usr/lib64/libvmcf.so” pointing to file ”/usr/lib/vmware-tools/lib64/libvmcf.so/libvmcf.so”.
- Run the Install Script. The -d flag automatically answers the default to all questions. To customize it, just omit the -d.
- Reboot
Also, please follow me on Twitter: @justinschier
This is "How to do Computing" for everyday usage ...
Tuesday, 30 July 2013
Issues with VMware 8 wont run Kernel 3.8 wont let VMware 8 & 9 work
When I try to launch VMware workstation, I get the following error:
No errors, when I select INSTALL nothing happens just closes.
I install manually:
I will start a bounty to fix this.
Ubuntu 13.04 64bit
I have tried a different Kernel, but end up with the same problem.
Tried this as suggested: here
Before you can run VMware, several modules must be compiled and loaded into the kernel CANCEL / INSTALL
No errors, when I select INSTALL nothing happens just closes.
I install manually:
sudo apt-get install open-vm-tools open-vm-tools-dev open-vm-dkms open-vm-toolbox open-vm-tools-devBut already installed to the latest versions.
I will start a bounty to fix this.
Ubuntu 13.04 64bit
pst007x@pst007x-Serval-Professional:~$ uname -a
Linux pst007x-Serval-Professional 3.9.0-030900-generic #201304291257 SMP Mon Apr 29 16:58:15 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
I have tried a different Kernel, but end up with the same problem.
Tried this as suggested: here
#!/bin/bash
cd
cp -prn /usr/lib/vmware/modules/source /usr/lib/vmware/modules/source-backup
mkdir fixed
cd fixed
find /usr/lib/vmware/modules/source -name "*.tar" -exec tar xf '{}' \;
## add missing header on kernels
sed -i '/#include "compat_wait.h"/a\#include "compat_sched.h"' vmnet-only/vnetUserListener.c
sed -i '/#include "compat_page.h"/a\#include "compat_sched.h"' vmci-only/include/pgtbl.h
## comment out an invalid definition
sed -i 's|\(extern void poll_initwait(compat_poll_wqueues \*);\)|//\1|' *-only/include/compat_wait.h
tar cf vmblock.tar vmblock-only
tar cf vmci.tar vmci-only
tar cf vmmon.tar vmmon-only
tar cf vmnet.tar vmnet-only
tar cf vmppuser.tar vmppuser-only
tar cf vsock.tar vsock-only
cp -p *.tar /usr/lib/vmware/modules/source
cd /lib/modules/`uname -r`/build/include/linux
ln -s ../generated/autoconf.h
ln -s ../generated/utsrelease.h
cd
vmware-modconfig --console --install-all
# clean up
cd
rm -rf fixed
cd /lib/modules/`uname -r`/build/include/linux
rm autoconf.h utsrelease.h
cd /usr/lib/vmware/modules/
rm -rf source-backup
cd
pst007x@pst007x-Serval-Professional:~/Desktop$ sudo ./run
[sudo] password for pst007x:
sed: can't read vmci-only/include/pgtbl.h: No such file or directory
sed: can't read *-only/include/compat_wait.h: No such file or directory
tar: vmppuser-only: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
ln: failed to create symbolic link ‘./autoconf.h’: File exists
ln: failed to create symbolic link ‘./utsrelease.h’:
File exists
Stopping VMware services:
VMware Authentication Daemon done
VM communication interface socket family done
Virtual machine communication interface done
Virtual machine monitor done
Blocking file system done
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-tGleah/vmmon-only'
/usr/bin/make -C /lib/modules/3.9.0-030900-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9.0-030900-generic'
CC [M] /tmp/modconfig-tGleah/vmmon-only/linux/driver.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/linux/driverLog.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/linux/hostif.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/common/apic.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/common/comport.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/common/cpuid.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/common/hashFunc.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/common/memtrack.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/common/phystrack.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/common/task.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/common/vmx86.o
CC [M] /tmp/modconfig-tGleah/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/modconfig-tGleah/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-tGleah/vmmon-only/vmmon.mod.o
LD [M] /tmp/modconfig-tGleah/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.9.0-030900-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-tGleah/vmmon-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-tGleah/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/modconfig-tGleah/vmmon-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-tGleah/vmnet-only'
/usr/bin/make -C /lib/modules/3.9.0-030900-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9.0-030900-generic'
CC [M] /tmp/modconfig-tGleah/vmnet-only/driver.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/hub.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/userif.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/netif.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/bridge.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/filter.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/procfs.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/smac_compat.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/smac.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/vnetEvent.o
CC [M] /tmp/modconfig-tGleah/vmnet-only/vnetUserListener.o
LD [M] /tmp/modconfig-tGleah/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-tGleah/vmnet-only/vmnet.mod.o
LD [M] /tmp/modconfig-tGleah/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.9.0-030900-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-tGleah/vmnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-tGleah/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/modconfig-tGleah/vmnet-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-tGleah/vmblock-only'
/usr/bin/make -C /lib/modules/3.9.0-030900-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9.0-030900-generic'
CC [M] /tmp/modconfig-tGleah/vmblock-only/linux/block.o
CC [M] /tmp/modconfig-tGleah/vmblock-only/linux/control.o
CC [M] /tmp/modconfig-tGleah/vmblock-only/linux/dentry.o
CC [M] /tmp/modconfig-tGleah/vmblock-only/linux/file.o
CC [M] /tmp/modconfig-tGleah/vmblock-only/linux/filesystem.o
CC [M] /tmp/modconfig-tGleah/vmblock-only/linux/inode.o
CC [M] /tmp/modconfig-tGleah/vmblock-only/linux/module.o
CC [M] /tmp/modconfig-tGleah/vmblock-only/linux/stubs.o
/tmp/modconfig-tGleah/vmblock-only/linux/dentry.c:38:4: warning: initialisation from incompatible pointer type [enabled by default]
/tmp/modconfig-tGleah/vmblock-only/linux/dentry.c:38:4: warning: (near initialisation for ‘LinkDentryOps.d_revalidate’) [enabled by default]
/tmp/modconfig-tGleah/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate’:
/tmp/modconfig-tGleah/vmblock-only/linux/dentry.c:104:7: warning: passing argument 2 of ‘actualDentry->d_op->d_revalidate’ makes integer from pointer without a cast [enabled by default]
/tmp/modconfig-tGleah/vmblock-only/linux/dentry.c:104:7: note: expected ‘unsigned int’ but argument is of type ‘struct nameidata *’
CC [M] /tmp/modconfig-tGleah/vmblock-only/linux/super.o
/tmp/modconfig-tGleah/vmblock-only/linux/control.c: In function ‘ExecuteBlockOp’:
/tmp/modconfig-tGleah/vmblock-only/linux/control.c:285:9: warning: assignment from incompatible pointer type [enabled by default]
/tmp/modconfig-tGleah/vmblock-only/linux/control.c:296:4: warning: passing argument 1 of ‘putname’ from incompatible pointer type [enabled by default]
In file included from include/linux/proc_fs.h:5:0,
from /tmp/modconfig-tGleah/vmblock-only/linux/control.c:28:
include/linux/fs.h:2040:13: note: expected ‘struct filename *’ but argument is of type ‘char *’
/tmp/modconfig-tGleah/vmblock-only/linux/inode.c:49:4: warning: initialisation from incompatible pointer type [enabled by default]
/tmp/modconfig-tGleah/vmblock-only/linux/inode.c:49:4: warning: (near initialisation for ‘RootInodeOps.lookup’) [enabled by default]
LD [M] /tmp/modconfig-tGleah/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: "putname" [/tmp/modconfig-tGleah/vmblock-only/vmblock.ko] undefined!
CC /tmp/modconfig-tGleah/vmblock-only/vmblock.mod.o
LD [M] /tmp/modconfig-tGleah/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.9.0-030900-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-tGleah/vmblock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-tGleah/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/modconfig-tGleah/vmblock-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-tGleah/vmci-only'
/usr/bin/make -C /lib/modules/3.9.0-030900-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9.0-030900-generic'
CC [M] /tmp/modconfig-tGleah/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-tGleah/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-tGleah/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-tGleah/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-tGleah/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-tGleah/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-tGleah/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-tGleah/vmci-only/common/vmciHashtable.o
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:127:4: error: implicit declaration of function ‘__devexit_p’ [-Werror=implicit-function-declaration]
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:127:4: error: initialiser element is not constant
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:127:4: error: (near initialisation for ‘vmci_driver.remove’)
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:1754:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘vmci_probe_device’
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:1982:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘vmci_remove_device’
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:119:12: warning: ‘vmci_probe_device’ used but never defined [enabled by default]
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:121:13: warning: ‘vmci_remove_device’ used but never defined [enabled by default]
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:2063:1: warning: ‘vmci_interrupt’ defined but not used [-Wunused-function]
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:2137:1: warning: ‘vmci_interrupt_bm’ defined but not used [-Wunused-function]
/tmp/modconfig-tGleah/vmci-only/linux/driver.c:1717:1: warning: ‘vmci_enable_msix’ defined but not used [-Wunused-function]
cc1: some warnings being treated as errors
make[2]: *** [/tmp/modconfig-tGleah/vmci-only/linux/driver.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [_module_/tmp/modconfig-tGleah/vmci-only] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-3.9.0-030900-generic'
make: *** [vmci.ko] Error 2
make: Leaving directory `/tmp/modconfig-tGleah/vmci-only'
Unable to install all modules. See log for details.
pst007x@pst007x-Serval-Professional:~/Desktop$
pst007x@pst007x-Serval-Professional:~$ sudo vmware-modconfig --console --install-all
[sudo] password for pst007x:
Stopping VMware services:
VMware Authentication Daemon done
VM communication interface socket family done
Virtual machine communication interface done
Virtual machine monitor done
Blocking file system done
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-IFjtiM/vmmon-only'
/usr/bin/make -C /lib/modules/3.9.0-030900-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9.0-030900-generic'
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/linux/driver.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/linux/driverLog.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/linux/hostif.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/common/apic.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/common/comport.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/common/cpuid.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/common/hashFunc.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/common/memtrack.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/common/phystrack.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/common/task.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/common/vmx86.o
CC [M] /tmp/modconfig-IFjtiM/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/modconfig-IFjtiM/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-IFjtiM/vmmon-only/vmmon.mod.o
LD [M] /tmp/modconfig-IFjtiM/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.9.0-030900-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-IFjtiM/vmmon-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-IFjtiM/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/modconfig-IFjtiM/vmmon-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-IFjtiM/vmnet-only'
/usr/bin/make -C /lib/modules/3.9.0-030900-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9.0-030900-generic'
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/driver.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/hub.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/userif.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/netif.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/bridge.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/filter.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/procfs.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/smac_compat.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/smac.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/vnetEvent.o
CC [M] /tmp/modconfig-IFjtiM/vmnet-only/vnetUserListener.o
LD [M] /tmp/modconfig-IFjtiM/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-IFjtiM/vmnet-only/vmnet.mod.o
LD [M] /tmp/modconfig-IFjtiM/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.9.0-030900-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-IFjtiM/vmnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-IFjtiM/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/modconfig-IFjtiM/vmnet-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-IFjtiM/vmblock-only'
/usr/bin/make -C /lib/modules/3.9.0-030900-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9.0-030900-generic'
CC [M] /tmp/modconfig-IFjtiM/vmblock-only/linux/block.o
CC [M] /tmp/modconfig-IFjtiM/vmblock-only/linux/control.o
CC [M] /tmp/modconfig-IFjtiM/vmblock-only/linux/dentry.o
CC [M] /tmp/modconfig-IFjtiM/vmblock-only/linux/file.o
CC [M] /tmp/modconfig-IFjtiM/vmblock-only/linux/filesystem.o
CC [M] /tmp/modconfig-IFjtiM/vmblock-only/linux/inode.o
CC [M] /tmp/modconfig-IFjtiM/vmblock-only/linux/module.o
CC [M] /tmp/modconfig-IFjtiM/vmblock-only/linux/stubs.o
/tmp/modconfig-IFjtiM/vmblock-only/linux/control.c: In function ‘ExecuteBlockOp’:
/tmp/modconfig-IFjtiM/vmblock-only/linux/control.c:285:9: warning: assignment from incompatible pointer type [enabled by default]
/tmp/modconfig-IFjtiM/vmblock-only/linux/control.c:296:4: warning: passing argument 1 of ‘putname’ from incompatible pointer type [enabled by default]
In file included from include/linux/proc_fs.h:5:0,
from /tmp/modconfig-IFjtiM/vmblock-only/linux/control.c:28:
include/linux/fs.h:2040:13: note: expected ‘struct filename *’ but argument is of type ‘char *’
/tmp/modconfig-IFjtiM/vmblock-only/linux/dentry.c:38:4: warning: initialisation from incompatible pointer type [enabled by default]
/tmp/modconfig-IFjtiM/vmblock-only/linux/dentry.c:38:4: warning: (near initialisation for ‘LinkDentryOps.d_revalidate’) [enabled by default]
/tmp/modconfig-IFjtiM/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate’:
/tmp/modconfig-IFjtiM/vmblock-only/linux/dentry.c:104:7: warning: passing argument 2 of ‘actualDentry->d_op->d_revalidate’ makes integer from pointer without a cast [enabled by default]
/tmp/modconfig-IFjtiM/vmblock-only/linux/dentry.c:104:7: note: expected ‘unsigned int’ but argument is of type ‘struct nameidata *’
/tmp/modconfig-IFjtiM/vmblock-only/linux/inode.c:49:4: warning: initialisation from incompatible pointer type [enabled by default]
/tmp/modconfig-IFjtiM/vmblock-only/linux/inode.c:49:4: warning: (near initialisation for ‘RootInodeOps.lookup’) [enabled by default]
CC [M] /tmp/modconfig-IFjtiM/vmblock-only/linux/super.o
LD [M] /tmp/modconfig-IFjtiM/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: "putname" [/tmp/modconfig-IFjtiM/vmblock-only/vmblock.ko] undefined!
CC /tmp/modconfig-IFjtiM/vmblock-only/vmblock.mod.o
LD [M] /tmp/modconfig-IFjtiM/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.9.0-030900-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-IFjtiM/vmblock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-IFjtiM/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/modconfig-IFjtiM/vmblock-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-IFjtiM/vmci-only'
/usr/bin/make -C /lib/modules/3.9.0-030900-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.9.0-030900-generic'
CC [M] /tmp/modconfig-IFjtiM/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-IFjtiM/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-IFjtiM/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-IFjtiM/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-IFjtiM/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-IFjtiM/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-IFjtiM/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-IFjtiM/vmci-only/common/vmciEvent.o
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:127:4: error: implicit declaration of function ‘__devexit_p’ [-Werror=implicit-function-declaration]
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:127:4: error: initialiser element is not constant
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:127:4: error: (near initialisation for ‘vmci_driver.remove’)
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:1754:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘vmci_probe_device’
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:1982:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘vmci_remove_device’
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:119:12: warning: ‘vmci_probe_device’ used but never defined [enabled by default]
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:121:13: warning: ‘vmci_remove_device’ used but never defined [enabled by default]
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:2063:1: warning: ‘vmci_interrupt’ defined but not used [-Wunused-function]
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:2137:1: warning: ‘vmci_interrupt_bm’ defined but not used [-Wunused-function]
/tmp/modconfig-IFjtiM/vmci-only/linux/driver.c:1717:1: warning: ‘vmci_enable_msix’ defined but not used [-Wunused-function]
cc1: some warnings being treated as errors
make[2]: *** [/tmp/modconfig-IFjtiM/vmci-only/linux/driver.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [_module_/tmp/modconfig-IFjtiM/vmci-only] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-3.9.0-030900-generic'
make: *** [vmci.ko] Error 2
make: Leaving directory `/tmp/modconfig-IFjtiM/vmci-only'
Unable to install all modules. See log for details.
pst007x@pst007x-Serval-Professional:~$ sudo apt-get install build-essential
Reading package lists... Done
Building dependency tree
Reading state information... Done
build-essential is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
pst007x@pst007x-Serval-Professional:~$
Thursday, 16 May 2013
Update script working with Backtrack 5
I could not find an update script working with Backtrack 5 so I decided to make a quick one.
Updated version: 2.0
Changelog Version 2.0
Screenshot:
If you know more tools I could add to the script in order to update them please feel free to post them here.
Also if you find any bugs or have any feedback feel free to contact me in this thread. I will update the thread with each update to the script.
NOTE: Please make sure you understand what the script does before running it.
Enjoy!
Updated version: 2.0
Changelog Version 2.0
Code:
* Reviewed all tools. * Compatible with Backtrack 5 R2/R3. * Removed the menu.
Code:
git clone git://github.com/sickn3ss/backtrack_update.git cd backtrack_update chmod a+x backtrack5_update.py ./backtrack5_update.py
If you know more tools I could add to the script in order to update them please feel free to post them here.
Also if you find any bugs or have any feedback feel free to contact me in this thread. I will update the thread with each update to the script.
NOTE: Please make sure you understand what the script does before running it.
Enjoy!
Friday, 29 March 2013
XAMPP: Another web server daemon with SSL is already running
Assumption: XAMPP is unzipped @ /opt/ folder.
If you get the error "XAMPP: Another web server daemon with SSL is already running" when you run "./lampp start". Simply follow the steps below to get rid of this error:
1. Open the file /opt/lampp/etc/httpd.conf
2. Search the "Listen 80" and change it to some other port (e.g. Listen 2145) (Line No. 40)
3. Open the file /opt/lampp/etc/extra/httpd-ssl.conf
4. Search the "Listen 443" and change it to some other port (e.g. Listen 16443) (Line No. 39)
5. Open the file "/opt/lampp/lampp"
6. Search for the port "testport 80" and replace it to "testport 2145". Also change the "testport 443" to "testport 16443". (Happens to be the Line No. 197, 214)
7. Now go and run "/opt/lampp/lampp start". (It should work now).
Hope this Helps :-)
Monday, 21 January 2013
Subscribe to:
Posts (Atom)
-
How To Hide and unhide the hard disk Volumes using CMD Commands : First check how many drives are there in my computer and then s...
-
Simplify Your Ansible Playbook Creation with ChatGPT Are you tired of writing complex Ansible playbooks manually? Want to streamline your ...
-
New GNS3 Setup With Lower CPU Load and Lower Memory Consumption ..Try It !!!
