Josh's Toolbox

Iteration 11: What If I Have a Lot of Friends?

There is one major limitation that you run into when designing a low overhead ingress server. I briefly mentioned ports earlier, but let’s talk about them in a bit more detail. A connection between two machines is defined by four pieces of information: the IPs of the two machines and the ports each is using. Ports are just a number, a 16-bit number to be precise.

Iteration 12: Do You Know What You Are Doing Claude?

While making the previous change, Claude made an unrelated change that actually would’ve broken things. And with that maneuver, Claude hands me the lead. Josh 🟨Claude76

Iteration 13: Do I Know What I Am Doing?

I realized that like the UDP knobs, we’d want similar knobs to turn for TCP. When a UDP connection is opened, conntrack by default tracks that connection for 30 seconds. When a TCP connection is opened, conntrack tracks it till it closes, or if never sees that, for 5 DAYS.

Iteration 14: Are We There Yet?

I promise we’re almost out of iterations. This iteration was a simple request from me to further expand the module’s documentation on kernel parameter configuration. Josh 🟨Claude68

Where Does That Leave Us?

And that brings us to the final version. I have not reviewed it, or even tested it. I figure that should take me a few hours, but at the time of writing this blog post, I haven’t invested it. DO NOT USE IT. (Besides, you don’t even know my super special and awesome way I plan to expose WireGuard credentials.) But, this post isn’t about the tool we created, at least not solely.