Hi Thomas,
yes, that is true. You may set the field of the Bundle source, but it is ignored/overwritten by the daemon. Maybe some day I will change that, since I had the same problem/question, too. But you may set your own endpoint using the API:
protocol extended set endpoint foo
Now, all bundles sent from this API connection have dtn://myhost/foo as the source, and you will get a notificaiton of new bundles sent to dtn://myhost/foo, too.
HTH, Stephan
On So, 2016-11-06 at 23:30 +0100, Thomas Halwax wrote:
Hi,
I use the extended API to send bundles. Let’s say I set the bundle source to "dtn://myhost/myapp/somevalue“. On the receiver side the source of the bundle is shown as „dtn://myhost/default-endpoint-id“. It’s looks like the daemon does not respect the source value of the bundle but uses the default endpoint id. Is my assumption correct? If so, why is this and is there a way to use my bundle source? My goal is to create a request-response communication but without knowing the correct sender the receiver cannot reply. Should I use the „report_to“ field for this purpose?
Thanks in advance and best regards, Thomas