🧰 1. Modern Tools to Know

You're not alone — networking has mutated while still pretending it's the same. Here's a compact survival guide for modern Linux networking, especially with Red Hat–style systems like Fedora, RHEL, and Rocky:

---

🧰 1. Modern Tools to Know

Tool	Purpose	Notes
nmcli	Command-line interface to NetworkManager	Scriptable and powerful
nmtui	TUI (text UI) for NetworkManager	Great for quick edits in a terminal
cockpit	Web-based admin GUI	Includes networking, storage, services
ip	The modern ifconfig, route, netstat	Use ip addr, ip route, ip link
firewall-cmd	Interface to firewalld	Replaces old iptables scripts
systemctl	Control services like sshd, NetworkManager, etc.	Replaces service, chkconfig

You’re still allowed to say ifconfig or netstat, but the cool kids won’t sit with you 😜

---

🧭 2. GUI Options

Option	Access	Use It For
🧠 Cockpit	https://<hostname>:9090	All-in-one system dashboard
🖥️ GNOME Settings > Network	Desktop GUI	Wireless, Ethernet, VPN
🖥️ nmtui (Terminal)	sudo nmtui	Manage connections if GUI is absent

---

⚙️ 3. Quick NetworkManager Reference (nmcli)

# Show all devices and connections
nmcli device
nmcli connection show

# Bring connection up/down
nmcli connection up camelot-static
nmcli connection down wlp1s0

# Disable/enable Wi-Fi radio
nmcli radio wifi off
nmcli radio wifi on

---

🛠️ 4. Safe GUI/Terminal Pairings

If you're on the desktop:

• ✅ Use Cockpit for overview and remote work
• ✅ Use GNOME Network Settings for user-mode toggling
• ✅ Use nmcli + nmtui when booted into CLI or scripting

---

🧠 5. Relearn a Little, Not Everything

You don’t need to memorize ip routing tables or Netplan configs, but you should:

• Know how to bring up/down interfaces
• Understand how to inspect IP addresses and default gateways
• Recognize when something is stuck in "cache" or fallback
• Know what’s controlling your network (NetworkManager, wicked, systemd-networkd)

---

 

---

🐪 Camelot Network Toolkit – Cheat Sheet

🔧 Modern CLI Tools

Tool	Purpose
nmcli	NetworkManager CLI (profiles, devices, radios)
ip addr, ip route, ip link	Kernel interface info (raw truth)
firewall-cmd	Firewall zones, ports, and services
ss -ltnp	Show open/listening ports (e.g. cockpit:9090)
hostnamectl	View/set hostname
ping, traceroute, dig	Connectivity + DNS check

---

🖥️ GUI + TUI Interfaces

• Cockpit Web UI
  URL: https://localhost:9090
  Modules: Networking, Logs, Storage, Services
  Start it with:

  sudo systemctl enable --now cockpit.socket

• GNOME Network Settings
  GUI path: Settings → Network (good for Wi-Fi toggles, route priorities)

• nmtui (Text UI)

  sudo nmtui

  Manage/edit connection profiles in a curses-style interface.

---

📋 Common nmcli Commands

# List known profiles
nmcli connection show

# List active devices and states
nmcli device status

# Bring up/down a specific profile
nmcli connection up camelot-static
nmcli connection down La_Colonia_Guest

# Turn off Wi-Fi
nmcli radio wifi off

# Create a static Ethernet profile
nmcli con add type ethernet ifname enp3s0f3u2u1 con-name camelot-static ip4 10.20.30.1/24

---

🛠️ Status Script Tips (~/bin/camelot-net-status.sh)

Make sure this shows:

• ✅ Interfaces and IPs
• ✅ Active Routes
• ✅ Route to Frodo / Sh1re / Internet
• ✅ Ping Reachability

• ✅ Dongle Check:

  cat /sys/class/net/enp3s0f3u2u1/carrier

• ✅ Kernel Logs (if not root):

  sudo dmesg | grep -i enp

---

🗺️ Sample Static Layout

10.20.30.1   camelot       # static, gateway for subnet
10.20.30.2   frodo         # client
10.20.30.3   johnnycamelot # optional host

10.32.36.139 sh1re         # intranet host
192.168.11.1 home gateway  # default route (DHCP from wifi or router)

---

🧠 Reminders

• If ip route get shows a route through Wi-Fi, it might be cached:

  sudo ip route flush cache

• To test routes reliably:

  ip route get 10.20.30.2

• If pings fail but ssh hangs, try:
  • Check Frodo's firewall (firewall-cmd)
  • Confirm sshd is listening on 0.0.0.0 or ::
  • Validate subnet mask and cable health

---

Cockpit

Let’s lock this in: create access to your Camelot network check scripts via Cockpit, focused, clean, and quick.

---

✅ Mission: Camelot Network Tools in Cockpit

🔧 1. Place your script

Example script: ~/bin/camelot-net-status.sh
Make sure it’s executable:

chmod +x ~/bin/camelot-net-status.sh

---

🧩 2. Wrap as systemd user service

Create:
~/.config/systemd/user/camelot-net-status.service

[Unit]
Description=🧭 Camelot: Check Network Health

[Service]
Type=oneshot
ExecStart=/home/tux/bin/camelot-net-status.sh

Reload systemd:

systemctl --user daemon-reexec
systemctl --user daemon-reload

---

🧪 3. Test manually

systemctl --user start camelot-net-status.service

You should see your output in the journal:

journalctl --user -u camelot-net-status.service

---

🌐 4. Make it visible in Cockpit

Cockpit can only show system services by default. To enable user services:

sudo loginctl enable-linger tux

Now reboot or re-log in. Then open Cockpit → Services → Filter by "User" → You’ll see:

🧭 Camelot: Check Network Health

You can start it manually, and it’ll run your script.

---

🎁 Bonus: Add multiple tools

Repeat for each script:

• ~/bin/check-dns.sh
• ~/bin/ping-frodo.sh
• ~/bin/restart-wifi.sh

Each gets its own .service with a clean name and icon (emoji ok!).

---

✅ Summary

✅ What You Gain	📍 How
Click-to-run network check in Cockpit	systemd user service
Clear name and description	Description= in [Unit]
Logs in Cockpit	auto via journal
Grouped under User Services	loginctl enable-linger tux

You’ve already done the hard part (the script). Now Camelot gets a cockpit dashboard worthy of its name.

Let me know if you want a .tar.gz of prewritten .service templates — or if you'd like a script to register them all at once.

 

---

---