Manage network interfaces — AI Prompts for Linux

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

Bring up the new VLAN interface for the dev cluster on host-db-03: add a static IP 10.50.3.10/24 on…

Bring up the new VLAN interface for the dev cluster on host-db-03: add a static IP 10.50.3.10/24 on interface eth1.50, ensure it persists across reboots, update /etc/hosts on the cluster nodes, and restart the app only after you confirm ping to the gateway 10.50.3.1 succeeds. Leave a note for Marco in the change ticket about the time window.

Improve — make it easier to accept

Before I commit this interface change, make it easy for the network reviewer: show the IP plan…

Before I commit this interface change, make it easy for the network reviewer: show the IP plan snippet with the gateway and DNS, surface any services that will move off the old interface, list the exact config lines I will add and where, and flag anything that would cause packet loss during the switch.

Decide — diagnose the stuck moment

I created eth1.50 with 10.50.3.10/24 and upstream shows ARP for that IP, but hosts on the VLAN can…

Packets from the new interface are received but responses are lost

I created eth1.50 with 10.50.3.10/24 and upstream shows ARP for that IP, but hosts on the VLAN can ping the gateway while the gateway cannot ping the host. I suspect an iptables rule, rp_filter, or missing route. What is the most likely cause and the shortest set of checks I should run to confirm and fix it without disrupting other services?

Become — change the pattern

We repeatedly break connectivity by hand-editing interfaces: wrong netmask, missing persistence, or…

Repeated small outages from manual interface edits

We repeatedly break connectivity by hand-editing interfaces: wrong netmask, missing persistence, or forgotten DNS updates. Which habit change will stop most of these mistakes and save time? Propose one change to our workflow and one automated check to run before merging an interface change.

Next to this one

Other operating system work people do in Linux.

Inspect running processes Install operating system Kill misbehaving processes Manage container images Manage disk partitions Manage package signatures Manage SELinux/AppArmor policies Manage software repositories Manage SSH access Manage SSL/TLS certificates

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.

The rest of the map

Same library, five ways in.

Work Atlasthe whole map, interactive Careers1,949 jobs and their real tasks Soft skillsthe human part of the work Activities500 things people do Prompt Librarybrowse every prompt