Classic Sysadmin Task: Which Port Is a Service Listening On?
Test your Linux and Networking skills by identifying which port a service is using. Sounds easy? Perhaps, but be careful - you only get one shot!
Focused hands-on problems designed to help you hone your DevOps or Server Side skills. Some challenges are more educational, while others are based on real-world scenarios. The platform provides hints and feedback for each challenge, including automated solution checks.
Test your Linux and Networking skills by identifying which port a service is using. Sounds easy? Perhaps, but be careful - you only get one shot!
Test your Linux and Networking skills by pinpointing a process that is listening on a given port. Sounds easy? Perhaps, but be careful - you only get one shot!
This exercise tests your ability to configure kubernetes network policies to make sure only pods with specific labels can communicate with each other.
Be a networking Sherlock Holmes - find out which port a Kubernetes app uses and send a request to it.
Prove your networking skills by setting up an improvised proxy server with netcat.
Prove your networking skills by mapping one network address to another using socat.
Prove your networking skills by mapping one network address to another without starting any additional processes.
The culmination of the Docker networking challenges series. Can you create a Docker-like bridge network from scratch and using nothing but basic Linux commands.
Prove your mastery of Linux and containers by connecting multiple network namespaces into a single network.
Prove your Linux networking skills by connecting two network namespaces with a virtual Ethernet device.
There is a container that seems to have access to all host's interfaces but for some reason cannot call any addresses outside of the host. Can you fix it?
Learn how to create fully isolated virtual network environment using Linux network namespaces.
Learn a bunch of Linux networking tricks while trying to access an Nginx server running inside a container started with `ctr` and a bare containerd daemon.
Learn a bunch of Linux networking tricks while trying to access an Nginx server running inside a Docker container with no published ports.