linux-kernel - Re: [RFC] netconsole.txt: "nc" needs "-p" to specify the listening port

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <giobmsiixa.fsf@mx10.gouders.net>
Date:	Fri, 03 Aug 2012 08:33:21 +0200
From:	Dirk Gouders <gouders@...bocholt.fh-gelsenkirchen.de>
To:	Cong Wang <xiyou.wangcong@...il.com>
Cc:	Rob Landley <rob@...dley.net>, Milton Miller <miltonm@....com>,
	Borislav Petkov <bp@...en8.de>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Jan Engelhardt <jengelh@...i.de>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] netconsole.txt: "nc" needs "-p" to specify the listening port

Cong Wang <xiyou.wangcong@...il.com> writes:

> On Fri, Aug 3, 2012 at 4:39 AM, Dirk Gouders
> <gouders@...bocholt.fh-gelsenkirchen.de> wrote:
>>
>> From d756d2750e4cf07d3c0942dc3c491d57631d4338 Mon Sep 17 00:00:00 2001
>> From: Dirk Gouders <gouders@...bocholt.fh-gelsenkirchen.de>
>> Date: Thu, 2 Aug 2012 22:20:16 +0200
>> Subject: [PATCH] netconsole.txt: revision of examples for the receiver of kernel messages
>>
>> There are at least 4 implementations of netcat with the BSD-based
>> being the only one that has to be used without the -p switch to
>> specify the listening port.
>>
>> Jan Engelhardt suggested to add an example for socat(1).
>
>
> Looks good, but you missed your SOB.

Thanks for noticing that, attached is the amended patch.

Dirk

>From b3aec70d785d338b1b643fece6606cd32addaf0c Mon Sep 17 00:00:00 2001
From: Dirk Gouders <gouders@...bocholt.fh-gelsenkirchen.de>
Date: Thu, 2 Aug 2012 22:20:16 +0200
Subject: [PATCH] netconsole.txt: revision of examples for the receiver of kernel messages

There are at least 4 implementations of netcat with the BSD-based
being the only one that has to be used without the -p switch to
specify the listening port.

Jan Engelhardt suggested to add an example for socat(1).

Signed-off-by: Dirk Gouders <gouders@...bocholt.fh-gelsenkirchen.de>
---
 Documentation/networking/netconsole.txt |   19 +++++++++++++++++--
 1 files changed, 17 insertions(+), 2 deletions(-)

diff --git a/Documentation/networking/netconsole.txt b/Documentation/networking/netconsole.txt
index 8d02207..2e9e0ae2 100644
--- a/Documentation/networking/netconsole.txt
+++ b/Documentation/networking/netconsole.txt
@@ -51,8 +51,23 @@ Built-in netconsole starts immediately after the TCP stack is
 initialized and attempts to bring up the supplied dev at the supplied
 address.
 
-The remote host can run either 'netcat -u -l -p <port>',
-'nc -l -u <port>' or syslogd.
+The remote host has several options to receive the kernel messages,
+for example:
+
+1) syslogd
+
+2) netcat
+
+   On distributions using a BSD-based netcat version (e.g. Fedora,
+   openSUSE and Ubuntu) the listening port must be specified without
+   the -p switch:
+
+   'nc -u -l -p <port>' / 'nc -u -l <port>' or
+   'netcat -u -l -p <port>' / 'netcat -u -l <port>'
+
+3) socat
+
+   'socat udp-recv:<port> -'
 
 Dynamic reconfiguration:
 ========================
-- 
1.7.8.6

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/