MWareman Posted October 8, 2021 Posted October 8, 2021 Hello, I suspect the ISY daemon is not running with permissions necessary to send broadcast packets. I have this rule which works flawlessly on native ISY - but packets are not sent when the same rule runs on ISY on POLISY.. Is there a way I can allow the daemon to send UDP to the broadcast address? Michael.
Jimbo.Automates Posted October 9, 2021 Posted October 9, 2021 I think it may be an issue that freebsd doesn't allow that as the broadcast address. I had this issue in a nodeserver when moving to Polisy, I'll look it up in the morning when I have time.Sent from my Pixel 3 XL using Tapatalk 1
MWareman Posted October 9, 2021 Author Posted October 9, 2021 I have tried the network broadcast address as well with the same issues. I also tried Netcat on POLISY with the same issue (nc -u 255.255.255.255 50223). Netcat additionally documents -b flag on FreeBSD (https://www.freebsd.org/cgi/man.cgi?query=netcat) but this option is missing from the implementation on POLISY: [admin@polisy ~]$ nc -u -b 172.20.255.255 50223 Password: nc: invalid option -- b usage: nc [-46DdEFhklNnrStUuvz] [-e policy] [-I length] [-i interval] [-O length] [--no-tcpopt] [--sctp] [-P proxy_username] [-p source_port] [-s source] [-T ToS] [-V rtable] [-w timeout] [-X proxy_protocol] [-x proxy_address[:port]] [destination] [port] [admin@polisy ~]$
Jimbo.Automates Posted October 9, 2021 Posted October 9, 2021 Not sure about the -b option, must not have the latest Netcat available on Polisy? Hopefully @Michel Kohanim can help with that. This works for me, but have to cntl-c it to get out: nc -u 192.168.86.255 50223
MWareman Posted October 9, 2021 Author Posted October 9, 2021 The nc command works - but I have wireshark running on another host and it does not show any packets when I send them. Changing the IP in the nc command to a unicast (where wireshark is running) and the packets arrive. 1
Michel Kohanim Posted October 10, 2021 Posted October 10, 2021 @MWareman, I don't thing it's supported through UDP. Did you also try Multicast? With kind regards, Michel 1
MWareman Posted October 11, 2021 Author Posted October 11, 2021 4 hours ago, Michel Kohanim said: @MWareman, I don't thing it's supported through UDP. Did you also try Multicast? With kind regards, Michel Awesome! This worked flawlessly. Sending to 224.0.0.1 (the multicast address for "All systems on this subnet") did the trick. Since multicast implies udp anyway - is there a functional difference between selecting 'udp' or 'multicast' in the NR? Either appears to work the same and produce the same payload. Thank you! 1
Michel Kohanim Posted October 11, 2021 Posted October 11, 2021 @MWareman, There is a difference in BSD. Although the underlying protocol is UDP, the sock options are different. With kind regards, Michel 1
Recommended Posts