Boot Failure from Bad sysctl

Recover a server that became unreachable after a sysctl change broke networking.

A advanced Linux challenge worth 20 points. Solve it hands-on in a real Linux environment in your browser - no local setup, no fake shells.

The Challenge

A sysctl change set net.ipv4.ip_forward=0 on a router/NAT host. After reboot, the machine lost network. Fix the configuration.

Your tasks:

• Identify the bad sysctl: grep -r "ip_forward" /etc/sysctl.d/
• The bad file is /etc/sysctl.d/99-bad.conf — fix the value from 0 to 1
• Apply the correct value live: sysctl -w net.ipv4.ip_forward=1 2>/dev/null

or: echo 1 > /proc/sys/net/ipv4/ip_forward

• Verify network restored: ip route list
• Test that the fixed sysctl.d file is correct: grep "ip_forward" /etc/sysctl.d/99-bad.conf
• Write the bad file path and fix applied to /tmp/sysctl_fix.txt
• Run check to validate