Specifies the IP of the interface which is used to send the Randomly instead of sequentially within a range or in the orderД®nables the RFC 2385 TCP MD5 signature option. Specifies that source and/or destination ports should be chosen Specifies the source port netcat should use, subject to privilege If no username is specified then authentication Specifies a username to present to a proxy server that requiresДЄuthentication. Specifies the size of the TCP send buffer. Servers require this to finish their work.Дo not do any DNS or service lookups on any specified addresses, Shutdown()the network socket after EOF on the input. Additionally, any timeouts specified with the -w option

It is anД®rror to use this option in conjunction with the -p, -s, or -z Rather than initiate a connection to a remote host. Used to specify that netcat should listen for an incoming connection Option, the server socket is not connected and it can receive UDP Also causes a delay time between connections toДЇorces netcat to stay listening for another connection after itsД¬urrent connection is completed. Specifies a delay time interval between lines of text sent and Specifies the size of the TCP receive buffer. simple TCP proxies - shell-script based HTTP clients and servers - network daemon testing - a SOCKS or HTTP Proxењњommand for ssh - and much, much more OptionsДЇorces netcat to use IPv4 addresses only.ДЇorces netcat to use IPv6 addresses only. Sending them to standard output, as bsdtelnet does with some. Nicely, and separates error messages onto standard error instead of Scanning, and deal with both IPv4 and IPv6. Send UDP packets, listen on arbitrary TCP and UDP ports, do port Involving TCP, UDP, or UNIX-domain sockets. Host: echo 'hello' | nc 192.168.1.The netcat (or nc) utility is used for just about anything under the sun The below should work to get a broadcast forwarded to another network via netcat: The -u is not needed as it is telling netcat to listen on a unix domain socket, google IPC :) (this is the biggest reason that your scenario is not working.) l 0.0.0.0 12101, tells netcat to listen on port 12101 on all interfaces that are up and with an IP address assigned. For Cisco IOS you would type in, under the interface, 'ip directed-broadcast'.Дў55.255.255.255 is a limited broadcast and is not going to get pass your routers regardless, it is solely intended for the layer 2 link that it resides. you would need to reference its documentation. Configuring your device to forward directed broadcast. Then the firewall, assuming it had a route to 192.168.1.0/24 and that it is set up to forward directed broadcast, would forward that broadcast out to the destination or next hop. For example for the subnet 192.168.1.0/24 the directed broadcast would be 192.168.1.255, the last IP in the subnet. If you wanted that to happen then you would need to send a directed broadcast.

If that is the case and this firewall is also acting also as a router (or if the packet has to go through a router) then it is going to process that packet but it will not forward it out its other interfaces. Sorry, if I am assuming wrong but you mentioned that you have your firewalls set up correctly so I am guessing that the host and client are not on the same subnet?

Netcat udp multicast