NC command lacks functionality (?)

[Peter Renzland]

Thanks Denys!

I see that ...

config_g:CONFIG_NC=y
config_g:# CONFIG_NC_SERVER is not set
config_g:CONFIG_NC_EXTRA=y

That would explain it.

Peter



On 09  Jan 10, at 14:22 , Denys Vlasenko wrote:

> On Saturday 10 January 2009 19:46, Peter Renzland wrote:
>> I am using Tomato 1.23 on a WRT54GL router, Linux 2.4.20 (patched),
>> Busybox v1.12.3
>>
>> nc appears to be unable to listen:
>>
>>
>> # nc -l 9876
>> nc: illegal option -- l
>> BusyBox v1.12.3 (2008-12-14 02:54:58 PST) multi-call binary
>>
>> Usage: nc [-iN] [-wN] [-f FILENAME|IPADDR PORTNUM] [-e COMMAND]
>>
>> Open a pipe to IP:port or file
>>
>> Options:
>> 	-e	Exec rest of command line after connect
>> 	-i SECS	Delay interval for lines sent
>> 	-w SECS	Timeout for connect
>> 	-f FILE	Use file (ala /dev/ttyS0) instead of network
>>
>>
>> Might this be a consequence of ...
>>
>> "BusyBox has been written with size-optimization and limited  
>> resources
>> in mind. It is also extremely modular so you can easily include or
>> exclude commands (or features) at compile time."
>>
>> I.e. that Tomato's nc command has been configured to lack "-l"
>> functionality?
>
> Yes. It depends on .config. With attached one, I'm getting
>
> # ./busybox nc -lvv 9876
> listening on 0.0.0.0:46846 ...
> ^C
>
> And btw, you are using -l incorrectly. You need to also use
> -p <PORT> to set port. In your example, 9876 will be ignored.
> --
> vda
> <.config.txt>