03-14-2017
How to scan IP range using nmap
My goal:
1. Find all ports open on a whole range.
Last edited by sk151993; 03-14-2017 at 10:00 AM..
Reason: removed profanity
10 More Discussions You Might Find Interesting
1. Cybersecurity
I am pretty new at running nmap ,and i have some doubt about some o/ps the nmap shows
I tried to scan my own system for UDP open ports
I see that if i use one UDP port say 13
It shows that its in open state , etc
But if i scan for the whole UDP ports in the nmap-services . I gives te... (2 Replies)
Discussion started by: DPAI
2 Replies
2. UNIX for Dummies Questions & Answers
Hi,
Whenever I tried to run nmap on my linux (red hat 6.2) boxes i got these outputs:
4444/tcp filtered krb524
6666/tcp filtered irc-serv
6699/tcp filtered napster
8888/tcp filtered sun-answerbook
Can anybody please... (10 Replies)
Discussion started by: necro
10 Replies
3. Shell Programming and Scripting
Hi everyone!
I've temporarily come out of hibernation (and will be gone for about two weeks after this post too) to ask for input on a small PHP script I have just completed.
The script aims to be a remote front-end for Nmap - now for the safety of this post, I ask that any replies refrain from... (6 Replies)
Discussion started by: Karma
6 Replies
4. AIX
I'm trying to compile nmap 4.11 on an aix 5.2 machine and get the following error when attempting the 'make' command;
make
"Makefile", line 1: make: 1254-055 Dependency line needs colon or double colon operator.
"Makefile", line 14: make: 1254-055 Dependency line needs colon or double colon... (2 Replies)
Discussion started by: zuessh
2 Replies
5. Shell Programming and Scripting
I want to print between the range two patterns if a particular pattern is present in between the two patterns. I am new to Unix. Any help would be greatly appreciated.
e.g.
Pattern1
Bombay
Calcutta
Delhi
Pattern2
Pattern1
Patna
Madras
Gwalior
Delhi
Pattern2
Pattern1... (2 Replies)
Discussion started by: joyan321
2 Replies
6. Solaris
I 'm getting following error when i run nmap for an ip .. what could be the reason for it ?
#nmap 10.22.67.18
Starting Nmap 4.68 ( Nmap - Free Security Scanner For Network Exploration & Security Audits. ) at 2009-07-06 19:07 UTC
Warning: Unable to open interface e1000g3301000 -- skipping it.... (2 Replies)
Discussion started by: fugitive
2 Replies
7. UNIX for Dummies Questions & Answers
Hello guys, i'm having a problem with nmap, what i'd like to do is a scan to find around 100 or so IP address that are up, and that correspond to sites.
The command i need should basically find sites through ip address randomly generated, let's say i generate 2000 ip, i'd like to know how many of... (0 Replies)
Discussion started by: AscaL
0 Replies
8. Cybersecurity
I'm seeing a persistent address showing up on my firewall router logs. The address is 10.98.115.9:67, and is broadcasting to 255.255.255.255. I know that this would typically signal a BOOTP service, such as a bootp server announcing itself on the network. But I can't isolate which machine it... (3 Replies)
Discussion started by: renoir611
3 Replies
9. IP Networking
I was just wondering, why does Nmap need root when doing an -sU UDP Scan?
Please and Thank You. (3 Replies)
Discussion started by: amreason
3 Replies
10. Homework & Coursework Questions
Scripting language : Bash Shell Script
1. problem statement
I have to create function in which read IP addresses one by one from one file (iplist.txt) and scan these IP using nmap. This scan IP's output is saved in output.txt file and parse output.txt to save only open ports with particular IP... (3 Replies)
Discussion started by: sk151993
3 Replies
LEARN ABOUT DEBIAN
file::find::object::rule::extending
File::Find::Object::Rule::Extending(3pm) User Contributed Perl Documentation File::Find::Object::Rule::Extending(3pm)
NAME
File::Find::Object::Rule::Extending - the mini-guide to extending File::Find::Object::Rule
SYNOPSIS
package File::Find::Object::Rule::Random;
use strict;
use warnings;
# take useful things from File::Find::Object::Rule
use base 'File::Find::Object::Rule';
# and force our crack into the main namespace
sub File::Find::Object::Rule::random () {
my $self = shift()->_force_object;
$self->exec( sub { rand > 0.5 } );
}
1;
DESCRIPTION
File::Find::Object::Rule inherits File::Find::Rule's extensibility. It is now possibile to extend it, using the following conventions.
Declare your package
package File::Find::Object::Rule::Random;
use strict;
use warnings;
Inherit methods from File::Find::Object::Rule
# take useful things from File::Find::Object::Rule
use base 'File::Find::Object::Rule';
Force your madness into the main package
# and force our crack into the main namespace
sub File::Find::Object::Rule::random () {
my $self = shift()->_force_object;
$self->exec( sub { rand > 0.5 } );
}
Yes, we're being very cavalier here and defining things into the main File::Find::Object::Rule namespace. This is due to lack of
imaginiation on my part - I simply can't find a way for the functional and oo interface to work without doing this or some kind of
inheritance, and inheritance stops you using two File::Find::Object::Rule::Foo modules together.
For this reason try and pick distinct names for your extensions. If this becomes a problem then I may institute a semi-official registry
of taken names.
Taking no arguments.
Note the null prototype on random. This is a cheat for the procedural interface to know that your sub takes no arguments, and so allows
this to happen:
find( random => in => '.' );
If you hadn't declared "random" with a null prototype it would have consumed "in" as a parameter to it, then got all confused as it doesn't
know about a '.' rule.
NOTES ABOUT THE CALLBACK
The callback can access the File::Find::Object::Result using "$self->finder->item_obj()".
AUTHOR
Richard Clamp <richardc@unixbeard.net>
COPYRIGHT
Copyright (C) 2002 Richard Clamp. All Rights Reserved.
This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
SEE ALSO
File::Find::Object::Rule
File::Find::::Rule::MMagic was the first extension module for File::Find::Rule, so maybe check that out.
perl v5.14.2 2012-05-05 File::Find::Object::Rule::Extending(3pm)