<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ssh on toorun.dev</title><link>https://toorun.dev/tags/ssh/</link><description>Recent content in ssh on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 02 Sep 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/ssh/index.xml" rel="self" type="application/rss+xml"/><item><title>Network Protocols Explained: TCP, UDP, DNS, HTTP, HTTPS, FTP, SSH, SCP, NTP, SMTP, POP3, IMAP, SNMP, MQTT and More</title><link>https://toorun.dev/posts/network-protocols-explained-tcp-udp-dns-http-https-ftp-ssh-scp-ntp-smtp-pop3-imap-snmp-mqtt/</link><pubDate>Wed, 02 Sep 2026 10:00:00 +0000</pubDate><guid>https://toorun.dev/posts/network-protocols-explained-tcp-udp-dns-http-https-ftp-ssh-scp-ntp-smtp-pop3-imap-snmp-mqtt/</guid><description>Network Protocols Explained: TCP, UDP, DNS, HTTP, HTTPS, FTP, SSH, SCP, NTP, SMTP, POP3, IMAP, SNMP, MQTT and More Every application on a network eventually uses some combination of IP, TCP, or UDP. Above that sits the real application protocol: DNS, HTTP, SSH, FTP, SMTP, MQTT, and many more.
If you understand the basic idea behind each protocol, it becomes much easier to design systems, debug network problems, and choose the right tool for the job.</description></item></channel></rss>