Hi Greg:
Thanks for the reply. However, it's the UDP source port that I'd like
control over. The *${header.CamelNettyRemoteAddress}* correctly resolves to
the in-flight destination *IP:port *of the client that I need to send the
UDP acknowledgement to. My problem is that *camel-netty4* is not giving me
control over the UDP source port, instead it appears to be binding to a
local ephemeral port chosen by the Linux OS.
*
SOURCE IP* Set correctly to the local IP address of the server
sending the UDP ack
*SOURCE PORT* OS ephemeral port (I need to be able to specify this port
number)
*DEST IP* Correctly taken from in-flight exchange
CamelNettyRemoteAddress header.
*DEST PORT* Correctly taken from in-flight exchange
CamelNettyRemoteAddress header.
So my UDP acknowledgements get delivered to the intended client, but the
client rejects them because
it's examining the UDP source port and seeing that it's not the expected
value, but rather a different ephemeral source port in each acknowledgement.
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-specify-the-UDP-source-port-with-camel-netty4-tp5775017p5775057.html
Sent from the Camel - Users mailing list archive at Nabble.com.
