Chapters: 
Bridges

🪄 “The Camelot Bridge”

(short, memorable, and much less swear-inducing) 

10.20.30.1  → camelot
10.20.30.2  → frodo

No new networks.
No mystery subnets.
No auto-assigned 10.42.x.x.
No analysis.
No surprises.

Just two machines on one clean wired LAN.

✅ FINAL, CLEAN CONFIG — TEMPORARY FIRST (to confirm it works)

We do it temporarily first so nothing breaks permanently if the NICs fight us again.

After it works → I give you the permanent stable setup.

🟦 FRODO (Ethernet = enp0s26u1u2u1)

Run this exactly: 

sudo ip addr flush dev enp0s26u1u2u1
sudo ip addr add 10.20.30.2/24 dev enp0s26u1u2u1
sudo ip link set enp0s26u1u2u1 up

🟩 CAMELOT (Ethernet = enp3s0f4u1)

Run this exactly: 

sudo ip addr flush dev enp3s0f4u1
sudo ip addr add 10.20.30.1/24 dev enp3s0f4u1
sudo ip link set enp3s0f4u1 up

🟨 TEST — MUST DO THIS NEXT

From Camelot: 

ping -c 3 10.20.30.2

From Frodo: 

ping -c 3 10.20.30.1

👉 Tell me yes/no

Do they ping each other now?

If yes → I give you the exact permanent NetworkManager config so these IPs stick forever, no more 10.42 resets, no more fighting, no more churn.

If no → we fix the remaining physical/link issue in one step.

You asked for 10.20.30.x — and we will get you there.

🎉 YES. We finally landed the configuration you actually want.
Now let’s make 10.20.30.1 ↔ 10.20.30.2 permanent forever — no more resets, no more 10.42 auto-assignments, no more NetworkManager fighting you.

And yes…
we can absolutely call this recipe:

🪄 “The Camelot Bridge”

(short, memorable, and much less swear-inducing)

🧱 THE CAMLOT BRIDGE — PERMANENT STATIC CONFIG

We lock each machine’s Ethernet to a static IP using a NetworkManager file.
After this, they never flip back to 10.42.x.x or DHCP.

Zero surprises on reboot.

🟩 ON CAMELOT

(interface: enp3s0f4u1)

Create a permanent static profile: 

sudo nmcli con add type ethernet ifname enp3s0f4u1 con-name camelot-static ipv4.method manual ipv4.addresses "10.20.30.1/24" ipv4.gateway ""
sudo nmcli con mod camelot-static connection.autoconnect yes

Disable whatever old/tethering/shared-profile was messing things up: 

sudo nmcli con down "Wired connection 1" 2>/dev/null
sudo nmcli con delete "Wired connection 1" 2>/dev/null

Bring the new profile online: 

sudo nmcli con up camelot-static

Camelot is now locked to 10.20.30.1 forever.

🟦 ON FRODO

(interface: enp0s26u1u2u1)

Create the static profile: 

sudo nmcli con add type ethernet ifname enp0s26u1u2u1 con-name frodo-static ipv4.method manual ipv4.addresses "10.20.30.2/24" ipv4.gateway ""
sudo nmcli con mod frodo-static connection.autoconnect yes

Remove old/auto/tether connections that created 10.42.x.x: 

sudo nmcli con down "Wired connection 1" 2>/dev/null
sudo nmcli con delete "Wired connection 1" 2>/dev/null

Activate the new one: 

sudo nmcli con up frodo-static

Frodo is now permanently 10.20.30.2.

🟨 REBOOT TEST (OPTIONAL BUT RECOMMENDED)

After both sides are configured and stable:

  1. Reboot Camelot
  2. Reboot Frodo

Then run: 

ping 10.20.30.1
ping 10.20.30.2

You should see:

  • ☑ Camelot answers
  • ☑ Frodo answers
  • ☑ No more 10.42.x.x
  • ☑ No more DHCP overrides
  • ☑ No more network “magic” messing you around

Absolutely — let’s save this victory and NOT summon the Windows dragon today.
You’ve earned the rest of your Sunday.
The Camelot Bridge is stable, Frodo is loyal, Camelot is responding, and the world is good again. 🛠️✨

And YES — a tiny project called Home Network 10.20.30 is perfect.

Here’s a clean starter you can copy/paste into a folder whenever you’re ready:

🏡 Home Network 10.20.30 Project (Starter Kit) 

home-network-10.20.30/
├── README.md
├── network-map.txt
├── linux-configs/
│   ├── camelot-static.nmcli
│   ├── frodo-static.nmcli
└── windows/
    └── (empty for now — untouched, unbothered, resting peacefully)

README.md (initial draft) 

# Home Network 10.20.30

A tiny project documenting the clean, stable setup of my local wired LAN:

- **Camelot** — 10.20.30.1
- **Frodo** — 10.20.30.2
- **JohnnyCamelot** — (reserved for later)

This network exists to connect my machines directly and reliably without DHCP,
without NetworkManager interference, and without the cursed 10.42.x.x subnet.

This project captures:
- the permanent static configs (nmcli profiles)
- quick instructions for restoring the network
- the “Camelot Bridge” recipe
- Windows notes (eventually… but not today)

network-map.txt 

Camelot (Linux) ........ 10.20.30.1   enp3s0f4u1
Frodo (Linux) .......... 10.20.30.2   enp0s26u1u2u1
JohnnyCamelot .......... 10.20.30.3   (future)
WindowsBox ............. 10.20.30.x   (Sunday not included)

camelot-static.nmcli 

sudo nmcli con add type ethernet ifname enp3s0f4u1 con-name camelot-static \
  ipv4.method manual ipv4.addresses "10.20.30.1/24"

sudo nmcli con mod camelot-static connection.autoconnect yes

frodo-static.nmcli 

sudo nmcli con add type ethernet ifname enp0s26u1u2u1 con-name frodo-static \
  ipv4.method manual ipv4.addresses "10.20.30.2/24"

sudo nmcli con mod frodo-static connection.autoconnect yes

🌱 When you're ready

We can:

  • add the Windows machine without ruining your mood
  • generate a diagram
  • make a “network reset” one-liner
  • create a GitHub repo
  • add an auto-check script
  • build a tiny dashboard that shows who’s alive on 10.20.30.x

Whatever you want.

Just say the word.

networking