Skip to main content

Where are my machines? (nmap)

I do odd jobs from my home office. It's not much but it supports my hobbies. Recently I was handed a POS and asked to configure it/integrate a new PinPad from a vendor that was not already supported.

The first task was to login. It was a linux based system with an ethernet port and ssh-server running. When the machine boots up it calls for an IP address from the local DHCP server. In my case the DHCP is served by my firewall. Depending on the type of software running on the DHCP server sometimes they list the IP address leases. This one did not.

nmap is a tool used to locate hosts and open ports. It has a number of good and bad uses.

The first step is to install nmap. This is simple on most Linux distros. Since the system I'm on is OSX I had an extra step. Assuming that I already macports already installed.
sudo port install nmap

Once the installation was completed I needed to execute the search.
nmap -v -p22 10.0.1.2-200

"-v" is the option for verbose

"-p22" is the setting to search for port 22 on each IP address. (port 22 is the ssh server port in most configurations)

"10.0.1.2-200" tells nmap to search the 199 IP address from 10.0.1.2 thru 10.0.1.200... for example: 10.0.1.2, 10.0.1.3, 10.0.1.4 ... and so on.

I got my list of devices and since it was a short list it was easy enough to try each.
Initiating Connect Scan at 19:10
Scanning 10 hosts [1 port/host]
Discovered open port 22/tcp on 10.0.1.27
Discovered open port 22/tcp on 10.0.1.21
Completed Connect Scan at 19:10, 0.20s elapsed (10 total ports)
Nmap scan report for 10.0.1.5
Host is up (0.19s latency).
PORT STATE SERVICE
22/tcp closed ssh

Nmap scan report for 10.0.1.20
Host is up (0.023s latency).
PORT STATE SERVICE
22/tcp closed ssh

Nmap scan report for 10.0.1.21
Host is up (0.0028s latency).
PORT STATE SERVICE
22/tcp open ssh

Nmap scan report for 10.0.1.22
Host is up (0.0061s latency).
PORT STATE SERVICE
22/tcp closed ssh

Nmap scan report for 10.0.1.23
Host is up (0.00027s latency).
PORT STATE SERVICE
22/tcp closed ssh

Nmap scan report for 10.0.1.24
Host is up (0.0028s latency).
PORT STATE SERVICE
22/tcp closed ssh

Nmap scan report for 10.0.1.25
Host is up (0.20s latency).
PORT STATE SERVICE
22/tcp closed ssh

Nmap scan report for 10.0.1.27
Host is up (0.0025s latency).
PORT STATE SERVICE
22/tcp open ssh

Nmap scan report for 10.0.1.28
Host is up (0.0063s latency).
PORT STATE SERVICE
22/tcp filtered ssh

Nmap scan report for 10.0.1.29
Host is up (0.0062s latency).
PORT STATE SERVICE
22/tcp filtered ssh

Read data files from: /opt/local/share/nmap
Nmap done: 199 IP addresses (10 hosts up) scanned in 20.18 seconds

Comments

Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: http://www.eeti.com.tw/drivers_Linux.html (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the setup.sh answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…