Replacing UDP transport with customized transport mechanism #4139
Replies: 2 comments
-
Hi @kunnalparihar, thanks for using Fast DDS. If you are able to provide us more information about your implementation, we may help to locate and address the issue. |
Beta Was this translation helpful? Give feedback.
-
Also, I am moving this question to the support discussion forum as per Fast DDS CONTRIBUTING guidelines. |
Beta Was this translation helpful? Give feedback.
-
Is there an already existing issue for this?
Expected behavior
Hi, thanks for the great work. I am currently trying to Replace UDP transport with a customized transport mechanism (Not UDP, Not SHM and Not TCP) to communicate between two machines using the FAST DDS application layer.
I expect that data is successfully received by the subscriber's application layer.
Current behavior
So Far, I can send the publisher's application layer to the publisher's transport layer and then send this data subscriber's transport layer (on different machines) but unfortunately, I am not sure why I can't send data from the subscriber's transport layer to subscriber's application layer. The on_data_available function is not triggered.
Steps to reproduce
I need your guidance on this. What could be the reason for this issue and how can i fix this.
Fast DDS version/commit
I am using V2.12.1
Platform/Architecture
Ubuntu Focal 20.04 arm64
Transport layer
UDPv4
Additional context
I am not using UDPv4
XML configuration file
No response
Relevant log output
No response
Network traffic capture
No response
Beta Was this translation helpful? Give feedback.
All reactions