netcat - UDP Broadcast

[elluk]

Hi Everyone,

This is going to be an easy one! (hopefully)

With my Win32 version on netcat (nc.exe) I can do the following...
(No windoze comments please!)

nc -u 192.168.1.255 9999

This broadcasts any data over my LAN on UDP 9999.

I can't manage to achieve the same effect from my Centos (or other) boxes.

It does nothing and returns me to prompt.

Can anyone show me how stupid i'm being please?

Thanks,

E

[anomie]

I can't manage to achieve the same effect from my Centos (or other) boxes.

It does nothing and returns me to prompt.

How do you know it does nothing? Watch the outbound udp traffic on that box using tcpdump.

I'm also presuming you've studied the nc manpages to confirm the same options you're trying to use are implemented on CentOS.

[elluk]

I know it does nothing because I'm already monitoring with a packet sniffer.
So thanks.

I have not read the man page (I will do so now).
However, If the functionality is not supported, I would still like a solution.

Am I right in thinking you don't know another way of sending data to a broadcast address?

Can anyone suggest an alternative/fixed method?

[anomie]

Am I right in thinking you don't know another way of sending data to a broadcast address?

No sir, you are not.

I don't have access to my CentOS box at the moment. I'll play around with nc and nmap on it later today and see what I find.

[anomie]

Weird - this isn't working as I'd expected. nc returns to the command line immediately on my CentOS box; probably the same behavior you're seeing. No error, no explanation (but a non-zero return code).

[root@fugu ~]# nc -u 10.0.0.255 9999
[root@fugu ~]# echo $?
1

I tried a few different udp ping combinations using nmap, and that doesn't appear to be the right tool for the job either.

I haven't had a need to arbitrarily send udp packets to a broadcast address before, so I'm not sure what else to recommend.

[elluk]

I also have this problem on a slackware distro.
So I don't think this is a CentOS thing.

Hopefully someone else will pipe up with a reply.

I KNEW YOU DIDN'T HAVE THE ANSWER!

[anomie]

Well, it's a question of incentives. If I can't solve a forum question after a few minutes I move along. It's free advice after all.

Good luck. Post back once you figure it out.

[elluk]

Well in that case...

5$ via paypal for the solution! or anyone else for that matter.

I'll leave it with you

[anomie]

FIVE dollars!!! (Isn't that like 3.50 after paypal tax?)

Tempting, but I'll pass on that... generous offer. Here's my latest stab at it:

# nmap -PU -P0 10.0.0.255 -p 9999

Using nmap -- UDP scan, don't bother with ping discovery (which should allow packets to be sent to the broadcast address), port 9999.

Note the tcpdump packets captured:

fugu# tcpdump port 9999
...
09:50:09.868410 IP fugu.someplace.45585 > 10.0.0.255.9999:...
09:50:10.868663 IP fugu.someplace.45586 > 10.0.0.255.9999:...

Ok?

(This nmap scan was run from a FBSD box, but nmap options should be standard across platforms.)

[elluk]

Thanks mate.

No quite what I was after though. I don't think nmap is the right tool for the job really.

I need the ability to pipe to the stream POSIX styleeee.

e.g.

nc -u 10.0.0.255 9999 < /dev/random

Thanks for trying. I'll keep looking and post if i find anything.