1 2In U-Boot, we implemented the networked console via the standard 3"devices" mechanism, which means that you can switch between the 4serial and network input/output devices by adjusting the 'stdin' and 5'stdout' environment variables. To switch to the networked console, 6set either of these variables to "nc". Input and output can be 7switched independently. 8 9We use an environment variable 'ncip' to set the IP address and the 10port of the destination. The format is <ip_addr>:<port>. If <port> is 11omitted, the value of 6666 is used. If the env var doesn't exist, the 12broadcast address and port 6666 are used. If it is set to an IP 13address of 0 (or 0.0.0.0) then no messages are sent to the network. 14 15For example, if your server IP is 192.168.1.1, you could use: 16 17 => setenv nc 'setenv stdout nc;setenv stdin nc' 18 => setenv ncip 192.168.1.1 19 => saveenv 20 => run nc 21 22 23On the host side, please use this script to access the console: 24 25 tools/netconsole <ip> [port] 26 27The script uses netcat to talk to the board over UDP. It requires you to 28specify the target IP address (or host name, assuming DNS is working). The 29script can be interrupted by pressing ^T (CTRL-T). 30 31Be aware that in some distributives (Fedora Core 5 at least) 32usage of nc has been changed and -l and -p options are considered 33as mutually exclusive. If nc complains about options provided, 34you can just remove the -p option from the script. 35 36It turns out that 'netcat' cannot be used to listen to broadcast 37packets. We developed our own tool 'ncb' (see tools directory) that 38listens to broadcast packets on a given port and dumps them to the 39standard output. It will be built when compiling for a board which 40has CONFIG_NETCONSOLE defined. If the netconsole script can find it 41in PATH or in the same directory, it will be used instead. 42 43For Linux, the network-based console needs special configuration. 44Minimally, the host IP address needs to be specified. This can be 45done either via the kernel command line, or by passing parameters 46while loading the netconsole.o module (when used in a loadable module 47configuration). Please refer to Documentation/networking/logging.txt 48file for the original Ingo Molnar's documentation on how to pass 49parameters to the loadable module. 50 51The format of the kernel command line parameter (for the static 52configuration) is as follows: 53 54 netconsole=[src-port]@[src-ip]/[<dev>],[tgt-port]@<tgt-ip>/[tgt-macaddr] 55 56where 57 58 src-port source for UDP packets 59 (defaults to 6665) 60 src-ip source IP to use 61 (defaults to the interface's address) 62 dev network interface 63 (defaults to eth0) 64 tgt-port port for logging agent 65 (defaults to 6666) 66 tgt-ip IP address for logging agent 67 (this is the required parameter) 68 tgt-macaddr ethernet MAC address for logging agent 69 (defaults to broadcast) 70 71Examples: 72 73 netconsole=4444@10.0.0.1/eth1,9353@10.0.0.2/12:34:56:78:9a:bc 74 75or 76 77 netconsole=@/,@192.168.3.1/ 78 79Please note that for the Linux networked console to work, the 80ethernet interface has to be up by the time the netconsole driver is 81initialized. This means that in case of static kernel configuration, 82the respective Ethernet interface has to be brought up using the "IP 83Autoconfiguration" kernel feature, which is usually done by defaults 84in the ELDK-NFS-based environment. 85 86To browse the Linux network console output, use the 'netcat' tool invoked 87as follows: 88 89 nc -u -l -p 6666 90 91Note that unlike the U-Boot implementation the Linux netconsole is 92unidirectional, i. e. you have console output only in Linux. 93