m (1 revision(s)) |
m (explicitly name the "second machine" as debugger; what about iptables or firewall?) |
||
| Line 3: | Line 3: | ||
Assume we have two computers on the same network. | Assume we have two computers on the same network. | ||
The machine with a problem: | The machine with a problem (the debugee): | ||
<pre>IP address: 192.168.1.1 | <pre>IP address: 192.168.1.1 | ||
</pre> | </pre> | ||
And a second machine | And a second machine (the debugger): | ||
<pre>IP address: 192.168.1.2 | <pre>IP address: 192.168.1.2 | ||
MAC address of eth0: 00:11:22:33:44:55</pre> | MAC address of eth0: 00:11:22:33:44:55</pre> | ||
| Line 21: | Line 21: | ||
For more information on netconsole, see http://www.mjmwired.net/kernel/Documentation/networking/netconsole.txt | For more information on netconsole, see http://www.mjmwired.net/kernel/Documentation/networking/netconsole.txt | ||
Comment: There should be some explicit statement about whether iptables and/or the firewall on the debugger needs to be changed temporarily, etc. Also, is there some other way to use netconsole so that it is active before you can invoke modprobe from a shell, such as during boot itself? | |||
Revision as of 17:15, 27 August 2009
Setting up netconsole
Assume we have two computers on the same network.
The machine with a problem (the debugee):
IP address: 192.168.1.1
And a second machine (the debugger):
IP address: 192.168.1.2 MAC address of eth0: 00:11:22:33:44:55
The debugger
On a different machine than the one you are seeing the problem, you need to run nc -l -u 6666
This will listen on udp port 6666 for any messages.
The debugee
On the machine that you're trying to debug a problem, run (as root) modprobe netconsole netconsole=4444@192.168.1.1/eth0,6666@192.168.1.2/00:11:22:33:44:55
If you replace the IP/MAC addresses with those relevant to your machines/network in the command above, you should see messages appearing on the debugging machine.
For more information on netconsole, see http://www.mjmwired.net/kernel/Documentation/networking/netconsole.txt
Comment: There should be some explicit statement about whether iptables and/or the firewall on the debugger needs to be changed temporarily, etc. Also, is there some other way to use netconsole so that it is active before you can invoke modprobe from a shell, such as during boot itself?