Menu

I told Claude to hold off on isolation. Its networks took two of our LAN's subnets.
📰

I told Claude to hold off on isolation. Its networks took two of our LAN's subnets.

DEV Community: docker·Pierre-Laurent Medori·12 days ago
#qh5riSAA
#devtodocker#devto#dev#claude#network
Reading 0:00
15s threshold

At 14:49 on October 13, I pasted two lines from a production host's routing table into my Claude Code session:

192.168.16.0 0.0.0.0 255.255.240.0 U 0 0 0 br-f1a328c0938f 192.168.32.0 0.0.0.0 255.255.240.0 U 0 0 0 br-0adbee56597f

Enter fullscreen mode

Exit fullscreen mode

Two /20 blocks, each sent to a Docker bridge. Machines on our LAN live in those ranges. From that host, traffic for anything between 192.168.16.0 and 192.168.47.255 went into the bridges instead of the network. I added one sentence, in French: "tu m'as fait un incident en prod". You gave me a production incident.

The first line of the answer said it was very probably its doing. It was. The part worth telling is what I had said before: I had asked to hold off on isolating that service, and the networks that broke the routes were the isolation.

Some context. I run backend engineering at GoodBarber , an app platform. That morning, with Claude Code, I was putting a new internal service on two of our Docker hosts.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.