Hi Atul, To clarify, would your user case work if Hostname and Port properties were enhanced to support evaluating expression language using the flow files?
Regards, Jim > On Jun 4, 2024, at 8:41 AM, Atul Saroha <atul...@gmail.com> wrote: > > Hi All, > > We recently started using nifi for the last 6 months. We are trying to figure > out an approach to one of our problems. > > Our application receives UDP packets which are RADIUS packets > <https://networkradius.com/doc/3.0.10/concepts/introduction/AAA.html> . Our > flow is to receive such packets through UDP and send response in UDP for > every packet we receive. For receiving, we are using ListenUDP and then put > these records to Kafka. > However to send responses, we need to use attributes which are set by the > ListenUdp processor, i.e. udp.sender and udp.post <http://udp.post/>. As > There multiple source system who are sending such UDP packets and we have to > revert acknowledgement responses to the sender server only using UDP. > > > Nifi has a PutUdp processor which supports Expression Language. However as > per doc it supports only variable registry. > Hostname > Destination hostname or IP address > Supports Expression Language: true (will be evaluated using variable registry > only) > Port > Destination port number > Supports Expression Language: true (will be evaluated using variable registry > only) > > > Is there a way to use attributes to post back udp on sender ip address. > > > > Thanks and Regards, > Atul Saroha > Ph.No. 8447784271
