25 Sep, 2012
1 commit
-
It is desirable to use different port numbers for sending and receiving
packets with netconsole in the case where you have more than one device
on the local subnet with netconsole enabled for broadcast. When they
use the same port for both, any output from one will look like input to
the other. This is typlically not desirable.This patch allows the input and output ports to be specified separately
in the environment.Signed-off-by: Joe Hershberger
Cc: Mike Frysinger
Acked-by: Mike Frysinger
16 Sep, 2009
2 commits
-
The standard netcat, while ubiquitous, doesn't handle broadcast udp packets
properly. The local ncb util does however. So if ncb can be located in
the standard locations, automatically use that instead.Signed-off-by: Mike Frysinger
-
The netcat utility likes to exit when it receives an empty packet (as it
thinks this means EOF). This can easily occur when working with command
line editing as this behavior will be triggered when using backspace. Or
with tabs and command line completion. So create two netcat processes -
one to only listen (and put it into a loop), and one to do the sending.
Once the user quits the transmitting netcat, the listening one will be
killed automatically.Signed-off-by: Mike Frysinger
10 Dec, 2008
1 commit
-
While the doc/README.NetConsole does have a snippet for people to
create their own netcat script, it's a lot easier to make a simple
dedicated script and tell people to use it.Also spruce it up a bit to make it user friendly.
Signed-off-by: Mike Frysinger