Skill

setup-netconsole

Configure netconsole to stream kernel oops and panic messages over UDP to another host on the LAN, for capturing crashes on systems that hang before writing to disk. Use when the user says "set up netconsole", "stream kernel logs over the network", or is dealing with crashes that leave no local log trail.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin linux-debugging

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Netconsole streams kernel messages to a remote syslog receiver over UDP at very low level — it keeps working during hangs when disk I/O and userspace are already dead. Essential for diagnosing freezes that leave no local evidence.

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Stars1

Forks0

Last CommitApr 17, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Set Up Netconsole

Prerequisites

Ask the user:

Receiver host — IP of a machine on the same LAN that will collect logs (e.g. a Raspberry Pi, NAS, or router with syslog).
Receiver port — default 6666 is fine.
Sender interface — usually the main Ethernet interface. Detect with ip route get <receiver-ip>.

Step 1: Load the module with target config

Identify sender gateway MAC (required by netconsole):

ip route get <receiver-ip>
# note the dev (e.g. eno1)
arp -n <gateway-ip>
# note the MAC

Load netconsole:

sudo modprobe netconsole netconsole=@<sender-ip>/<iface>,<port>@<receiver-ip>/<gateway-mac>

Test it:

echo "netconsole test from $(hostname)" | sudo tee /dev/kmsg

On the receiver, you should see the line arrive.

Step 2: Set up receiver

On the receiver host, either:

Quick — netcat one-liner:

nc -u -l <port> | tee -a netconsole-$(hostname).log

Persistent — systemd-journal-remote or rsyslog: Configure rsyslog to listen on UDP and write to /var/log/netconsole-<sender>.log.

Step 3: Persist across reboots

Create /etc/modules-load.d/netconsole.conf:

netconsole

And /etc/modprobe.d/netconsole.conf:

options netconsole netconsole=@<sender-ip>/<iface>,<port>@<receiver-ip>/<gateway-mac>

Note: if the sender uses DHCP, the IPs may shift. Consider configuring a DHCP reservation or switching to dynamic netconsole via configfs (/sys/kernel/config/netconsole/).

Step 4: Verify after reboot

dmesg | grep netconsole
# should show: netconsole: network logging started

Caveats

Netconsole is UDP — no guarantee of delivery. For critical cases use a wired LAN, not Wi-Fi.
Large messages may be truncated. Kernel oops output is designed to fit.
Does not help with sudden power loss or pre-networking crashes (very early boot).
Firewalls: ensure UDP/<port> is open on the receiver.