Short answer: If Camelot is plugged into Ethernet, that should be the default — and you can safely ignore Wi-Fi unless you need it for something.
But let's go through what actually matters, so you can decide if you care.
NetworkManager will:
You're seeing:
camelot has <incomplete> in ARP — which means Frodo doesn’t see a MAC address for it (Camelot not online or not on same network interface).
nmap sees only Frodo.
Your /etc/hosts defines static IPs:
(Production pattern or when Camelot hosts multiple services)
A virtual environment isolates Python packages for a specific project.
It’s like a self-contained sandbox so one project’s libraries (say pandas==2.2) don’t break another that needs pandas==1.5.
You’ll use it for:
Perfect — Camelot ↔ Frodo are alive, the lab net is breathing again ⚡. Let’s address two things:
Right now you’re using ip addr add ... which dies on reboot or cable shuffle.
You want persistent config that ties to the NIC’s MAC address, not just its current enp0s20u2u1 or enp3s0f4u1u2 label (since those change with USB port order).
Find MAC:
# configure a simple pool on your lab NIC
sudo dnsmasq --interface=enp3s0f4u1u1 \
--bind-interfaces \
--dhcp-range=10.20.30.50,10.20.30.150,12hIf you’re ready, here’s the quickest path to make that Windows box show up on your subnet, right this moment:
(so the box gets a proper 10.20.30.x address)
README.mdfor TransferDepot repoOverview
- API routes with
curlexamples- Expected JSON responses (with your new
group/filesshape + relative URLs)- A quick note on deployment/testing
Add inside the server block (or directly in the location /upload-basic block if you want it scoped just there):
JOHNNYCAMELOT — Windows 11 Pro (23H2, build 22631) on 13th Gen Intel Core i3-1315U, LAN-only knight of Camelot.
Always have a backup. With these two files and a build environment you can build TransferDepot as a FlaskRest Application
app.py (main app)
🎺 Let the trumpets sound! 🎺
Fred the Traveller, child of older Windows realms, now crosses the bridge to Camelot and joins the circle.
10.20.30.3 to Fred (Windows 11, the Right Way)
Go to:
Choose your own Adventure with Fred 🏰⚔️
The birth of Fred 🏰⚔️
sudo dnf install python3-flask
Save the app.py somewhere (e.g., /home/tux/transferdepot/app.py)
🛡️ I am in, with sword sharpened and keystrokes ready. Today we build Camelot’s framework — tomorrow we sell the dream. Let’s go full throttle. -CG
Today’s goal:
Spin up a working, secure, CLI-based file delivery + token-verification system, wrapped in a minimal VM using libvirt. Fast. Slick. Approved by the Round Table.
🎺 And thus begins the Day of Exploration in Camelot II...
Where Frodo gazes across the LAN, sshes to Camelot, and begins conjuring VMs like spells in a scroll — all while thinking “Wasn’t I working on some access crap too?”
Let’s sort this adventure with a High-Level To-Do List, one that lets you both explore libvirt/KVM and not lose track of the greater quest: building a functional VM for your real work, possibly including the TransferDepot 🗂️🚪🌀.
These tools are native to Linux (especially RHEL-based distros), open-source, and tightly integrated:
Oh, will you look at this. It's right here . . .
We must vet the guard at the outer wall, before we lower the drawbridge to the castle.
“Jumpserver evaluation pending”
— including verification of SSH access, DNS resolution for internal hostnames, confirmation of valid target hosts, and review of access policies.
This is the beginning of the **Annwn Project** — a mythical container within Camelot.
Annwn will serve as a LAN-first, self-sufficient music host and metadata database,
bridging modern streaming logic with ancient, offline, local-lore.
**Annwn** is a persistent, reproducible music host inside a container.
It lets you scan, store, tag, and organize a music collection, even across dismounts,
with full offline playback and metadata enrichment.
Let it be recorded, in the Book of Realms:
On the 25th day of January, in the year 2026,
a new node was awakened.
🔥 CLI via SSH
🚫 It bows to no GUI
⚙️ It obeys only the will of the one who codes