someguy123/net-tools repository overview

⁠Docker Networking Toolkit

⁠Originally created by @someguy123 (Github⁠ | Steemit⁠)

⁠Licensed under the MIT license (See LICENSE)

Docker Hub: someguy123/net-tools

This is a docker image which builds Ubuntu 18.04 LTS with various networking tools pre-installed, for debugging networks.

It was created as Ubuntu's docker image contains absolutely no networking tools, not even the most basic ifconfig, route, or ip. This makes it practically useless for basic networking tasks.

Originally developed for GNS3 (network prototyping tool)⁠, this container is perfect for troubleshooting and testing your GNS3 topology using the built-in Docker support. No need to set up bloated Linux VMs, just type into the image selection box someguy123/net-tools and you're ready to debug your network.

As this image is likely to be used directly from it's console, bash-completion and command-not-found are both included, plus a colorised bash prompt with timestamps.

Basic utilities such as tmux, screen, vim and nano are also included, making this image feel more like a normal VM, rather than a barebones docker container.

⁠For the most up to date instructions, package contents, and more details, such as how to use it within GNS3, check out the Github for this project https://github.com/Someguy123/docker-networktools⁠

⁠What's included

• bash-completion - to make bash tab completion better
• command-not-found - when you type a command that doesn't exist, it informs you of which package a command is in
• mtr-tiny - fast and easy to read realtime traceroutes for both IPv4 and IPv6 (tiny version skips all the GTK bloat)
• dnsutils - provides tools such as dig and nslookup for DNS debugging
• net-tools - basic networking tools such as ifconfig, netstat, route, arp
• nmap - port scanning and other network reconnaissance
• traceroute - self explanatory. alternative to mtr
• netcat - nc tool. highly versatile TCP/UDP/unixsocket client and server
• iproute2 - provides the ip and bridge tools for advanced network configs
• tcpdump - similar to wireshark, but CLI based. for inspecting network packets
• iputils-ping - for the ping command. supports both IPv4 and v6 in the same binary, instead of ping + ping6
• openssh - server and client. for testing ssh connectivity, and so you may ssh into the container for a better experience
• tmux - run multiple things in one terminal session, with tabs and split windows
• screen - similar to tmux, for running things in the background
• vim/nano - for times when you need a text editor. remember! don't expect files on a container to be persisted. use a volume.

⁠Basic Usage

Launch the docker image, with the SSH port forwarded. SSH will offer a better terminal experience than docker's TTY

NOTE: Please be careful with your docker port forwards. The SSH password is only 3 characters (net), there is no firewall inside of the container, and there is no rate limiting such as fail2ban.

Your container could be compromised if the SSH port is exposed to the internet carelessly.

docker run --name nettools -p 127.0.0.1:2222:22 -itd someguy123/net-tools

Now you can SSH into the container, use the username root and the password net

ssh [email protected] -p 2222

[email protected]'s password:
Welcome to Ubuntu 18.04.1 LTS

04:05:59 32b9bd38c2f9:~ # ping 8.8.4.4
PING 8.8.4.4 (8.8.4.4) 56(84) bytes of data.
64 bytes from 8.8.4.4: icmp_seq=1 ttl=37 time=16.8 ms
64 bytes from 8.8.4.4: icmp_seq=2 ttl=37 time=16.3 ms

Alternatively you can use the container without logging into SSH, just remove -p 127.0.0.1:2222:22, and use docker to launch a shell:

docker exec -it nettools bash

⁠For the most up to date instructions, package contents, and more details, such as how to use it within GNS3, check out the Github for this project https://github.com/Someguy123/docker-networktools⁠