Skip to content

A collection of commands and quick notes for working with Windows CMD, Raspberry Pi networking, and related tools.

License

Notifications You must be signed in to change notification settings

Zkitszo/network-analysis-commands-tools

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 
 
 

Repository files navigation

network-analysis-commands-tools

A collection of commands and quick notes for working with Windows CMD, Raspberry Pi networking, and related tools.

Network Analysis & NZYME Setup, Configuration, and Feedback


Before continuing

Carry on for network related commands or... Jump to the Nzyme Specific section

Raspberry Pi: Getting IP Address

Get the IP address of your Pi:

hostname -I

Note

Running the above gives the actual IP, where some may mistake the command "hostname -i" to return the same, it does not- depending on settup may return a differrent value- for the most part our applications return the callback IP address- using it will just loop the data back to the Pi.

or

ip addr show

Phased out (older command):

ifconfig

Force 2.4GHz Details

Use the -4 flag for IPv4 details (specific context may be required).


Network Discovery

If hostname is known, from Windows CMD (or other PC on the same network):

ping <hostname>.local

If using default Raspberry Pi settings:

ping raspberrypi.local

Using nmap for subnet scan:

First, get your computer's IP address:

ipconfig

Then scan your subnet:

nmap -sn <ip address/subnet>
# Example:
nmap -sn 192.168.1.0/24

Other useful IP scanning tools:

  • Angry IP Scanner
  • Fing (mobile, on same network)
  • Advanced IP Scanner

Watch for device names like "raspberrypi" if the default hostname is used.


Windows Command Line: User/Path Prompt

Obscure CMD username/path:

Temporary change:

prompt $G

Permanent change:

setx prompt $G

Other useful prompt codes:

  • $P: current drive and full path (default)
  • $N: current drive only
  • $_: new line

Nzyme Specific

Detais and findings as a user setting up Nzyme for the first time directed at those starting with limitted network experiene. You have no choice but to learn.

Setting Up PostgrSQL

I faced a fare bit of chgallenges with this- Hopefully this lets you glide past with out any yourself-

Important

This may be a problematiuc section for less experienced individuals- The documentation lumps the settup into one code bloc- They infact are required to be split up into their oun, individual step, one command at a time, confirming the command's outcome along the way.

Caution

Care and attention are required with this step- very important it is done, and correctly. Since everything is lumpewd into one code block, you must only run the command. Eerything else is just how it'll loo once completted. Ex: postgres=# CREATE USER nzyme WITH ENCRYPTED PASSWORD 'YOUR_PASSWORD_HERE'; CREATE ROLE the first postgres=# is just refrencing path and will already be onscreen- Similar the second CREATE ROLE at the end- That is the outcome of the command provided once the command has run- The correct command here is CREATE USER nzyme WITH ENCRYPTED PASSWORD 'youhavechangedthistoyourpassword';- Following that the command loos like postgres=# GRANT ALL PRIVILEGES ON DATABASE nzyme TO nzyme; GRANT but, the only part you are actually running are GRANT ALL PRIVILEGES ON DATABASE nzyme TO nzyme;- Copying thast whole bloc will not work/ doing it any other way will fail.

Warning

Running the command sudo -u postgres psql returns an error could not change directory to "/home/node000": Permission denied psql (15.14 (Debian 15.14-0+deb12u1)) Type "help" for help. Though, anyone observant wil notice path change to postgres=# which means it wored regardless and you can carry on to the net command.

Important

After this part postgres=# \c nzyme You are now connected to database "nzyme" as user "postgres". nzyme=# GRANT CREATE ON SCHEMA public TO nzyme the actual path will show as nzyme=# where in the documentation it remains as postgres=#- The change to nzyme=# is correct.

The code block for the setup of postgsql should be broken out into seperate commands-

sudo -u postgres psql CREATE DATABASE nzyme; CREATE USER nzyme WITH ENCRYPTED PASSWORD 'password'; GRANT ALL PRIVILEGES ON DATABASE nzyme TO nzyme;

Note

Observe path change- differrent from documentation- yet correct- from postgres=# to nzyme=#- no worries, carry on.

\c nzyme

...

The .config file

I tittle it in such a manner since this section gave me the most difficulties. I had to go back and forth trouble shooting small errors many times. Mostly user errors such as missin some syntax, or getting a path wrong... also, the way Mobaxterm handled its copy/ paste was a huge pain and caused me much trouble. Example: when copying over, there may be phantom characters which are added on... have to watch out not to copy blank space prior or after... I musta openned, saved, ran status over a hundred times due to these silly mistakes. I'll try to call out as much as I can here so you don't have to suffer as I had.

Note

Unldess you are used to it, I am usung Mobaxterm to SSH into the Pi... the style of copy and paste isn't what I'd been used to... ctr dosen't work the same way, nor does right click... change this in the settings menu right quick or suffer.

To open the .config file-

nano /etc/nzyme/nzyme.conf

Nope! Don't forget 'sudo'.

sudo nano /etc/nzyme/nzyme.conf

'rest_listen_uri': Change this to '0.0.0.0'.

Important

Changing 'rest_listen_uri' to '0.0.0.0' tells Nzyme to listen on all network interfaces, not just "localhost." This allows your main computer to talk to the Raspberry Pi.

'http_external_uri': Change this to the actual IP address of your Raspberry Pi (the one you are SSHing into).

Forgot the IP address? Open a new window/ SSH session in Mobaxterm and run the command 'hostname -I' . That command will return an IP address with a -i, but we require the result for -I.

Should look something like this:

SH interfaces: {

Make sure to set this to an IP address you can reach from your workstation.>

rest_listen_uri: "https://0.0.0.0:22900/"

This is usually the same as the rest_listen_uri. ...

http_external_uri: "https://10.0.0.50:22900/" } <<

We are jumping arround a little bit, go back towards the top of the file and find 'database_path'.

A password was setup with postgsql- edit that line to include it. Formatting may vary, you want it to be: 'postgresql://:@:/' where user is 'nzyme'... edit in your password along with host and keep the port the way it is.

Should look something like 'database_path: "postgresql://nzyme:biscote@127.0.0.1:5432/nzyme"'

Save and exit out of nano.

Ctrl+O, Enter (Save) Ctrl+X (Exit)

SH sudo systemctl enable nzyme --now<

To restart incase edits were made to the .config file-

SH sudo systemctl restart nzyme<

Check status-

SH sudo systemctl status nzyme<<

Check messages for any errors

SH sudo journalctl -u nzyme -n 50 --no-pager<

Something I encounterred: The error message There are un-run database changesets means that your configuration file is perfect. Nzyme connected to the database successfully using the password biscote, but it stopped because the database is currently empty (it has no tables).

Need to run the "migration" command once to build the database structure.

SH sudo nzyme-migrate<

Restart

SH sudo systemctl restart nzyme<

Check status- if "Running" all green then load web interface.

SH sudo systemctl status nzyme<

If you see green text saying active (running), you can go to your browser and type https://<YOUR_PI_IP>:22900.

Nzyme Web Interface

Ignore/ accept error- splash page will load.

Settup "Super User"

Nzyme Node & Tap Files

Note

One at a time- start with the Node- ~~~there will be some impotant edits required to a .config file. Complette this and have the Node plus web interface up and runninbg prior to setting up a Tap.~~~ Did this already... setting up Node till web interface is running.

Nzyme Node

The file, settup, .config file, leading upto web interface going live.

  • Node file:

Note

Node file is the same for all OS – compare file size; see... same... Just the naming of the file is differrent. Not sure why there couldn't just be 1 for all. Future proofing? Incase one deviates and requires more/ less code?

as of Nov 29, 2025

(https://github.com/nzymedefense/nzyme/releases/download/2.0.0-alpha.17/nzyme-node_rpios-12bookworm-noarch-2.0.0-alpha.17.deb

  • Tap file:

as of Nov 29, 2025

(https://github.com/nzymedefense/nzyme/releases/download/2.0.0-alpha.17/nzyme-tap_rpios-12bookworm-arm64-2.0.0-alpha.17.deb

Tap file is also the same across OS setups.

One at a time though


WiFi Adapter Management (Linux/Pi)

Important

Sometimes even branded adapters may not be what is advertised. Especially purchasing off 3rd party sites, or market places. Counterfeits, false addvertising, refurbished product where other componnents may have substituted originasls- possible componnent/ chip shortages at time of manufacture for a brief period of time. You may think you are getting an adapter with chipset X when in reality you got your self an adapter with chipset Z. Running commands like 'lsusb' and instead of going by what the advertiser wants you to think is inside, you can retrieve the ID of the device and cross refrence that against a database such as 'WikiDevi'. Using the ID on WikiDevi will help with identifying chipset manufacturer and model. On Windows open the device manager. That ID will be located in Details pane of the device itself, as property 'Hardware IDs'. See https://www.aircrack-ng.org/doku.php?id=compatibility_drivers for further details.

For USB adapters

lsusb

Fof internal adapters

lspci

View capabillities of WiFi adapter(s)

iw list | grep monitor

[Note] The above command 'iw list | grep monitor' returns any instance of the word monitor whether related to monitor mode or not. Running 'iw list' provides an extensive list of ALL your Wifi adapters capabillities, watch for the section which reads 'Supported interface modes'. Alternativelly you can use 'aircrack-ng'.

Set default WiFi adapter:

Confirm current default adapter:

nmcli

Typical interface names:

  • wlan0 (default)
  • wlan1, wlan2, wlan3 (additional adapters)

Show configured connections:

nmcli con show

Preconfigured/assigned to wlan0 (credentials stored?)

Change WiFi adapter:

nmcli connection modify <preconfigured-connection> interface-name wlan1
sudo reboot

After reboot, defaults to selected adapter.
If issues arise, repeat nmcli checks and modify again as needed.

Use aircrack-ng

Focussing on security, 'Aircrack-ng' is a complete suite of tools to assess WiFi network status.

[(https://www.aircrack-ng.org] ((https://www.aircrack-ng.org/)

Other

Collection of applications, software, tools, repositories to aid in all things Wifi- with focus on security- securing WiFi Networks & also methods , tools hackers may use- for educational purposes... understand what bad actors are upto, so that these exploits can be mitigated/ networks secured against tools used.

##WiFi Network Analysis Tools

https://sourceforge.net/projects/airgeddon.mirror/

iperf

https://sourceforge.net/projects/netstalker.mirror/

(Ultra-fast dhcp discovery tool for Linux. Used for LAN reconaissance written in C.

https://sourceforge.net/projects/zeek.mirror/

https://nfdump.sourceforge.net/ -legacy https://github.com/phaag/nfdump http://www.ripe.net/ripe/meetings/ripe-50/presentations/ripe50-plenary-tue-nfsen-nfdump.pdf nfdump syntax "cheatsheet" for filterring https://gist.github.com/phaag/06369bed7f39f97e1de51b1b0f5bc29a

NfSen is a graphical WEB based front end for the nfdump netflow tools. https://sourceforge.net/projects/nfsen/ -legacy https://github.com/phaag/nfsen

WiFi Password Related

Arp spoofer

https://sourceforge.net/projects/elmocut/

Wep hex dictionary already prepared [(https://www.aircrack-ng.org/doku.php?id=aircrack-ng

https://wepattack.sourceforge.net/ https://sourceforge.net/projects/wepattack/

Misc

https://sourceforge.net/projects/prometheus.mirror/ Export metrics for Prometheus https://github.com/phaag/nfexporter

Operating Systems

OS specialized in certain "intrests".

https://sourceforge.net/projects/dragonos-focal/

for Pi https://sourceforge.net/projects/dragonos-pi64/

Kali


Contributing

Contribute. New commands, tools/ resoursces or corrections via pull request or issue.

About

A collection of commands and quick notes for working with Windows CMD, Raspberry Pi networking, and related tools.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published