Does not discover other nodes' domain participants

3 posts / 0 new
Last post
Offline
Last seen: 1 day 5 hours ago
Joined: 09/10/2022
Posts: 55
Does not discover other nodes' domain participants

Hi. I'm using rti v6.

I use different pcs together in the network. They send and receive data to eachother with other protocols. Ips are set by dhcp and there is not any difference in configuration between them in network setting. I use multicast discovery.

The problem is that computer A, B and C's domain participant in "local host" can discover eachother without any problem. And computer A and B can discover each other. But computer C can't discover computer A and B. And computer A and B cant discover computer C too. When I checked discovery packets. Computer C receives discovery packet with invalid domain id (like -12345).

I don't understand the problem. Could you please help me?

Howard's picture
Offline
Last seen: 2 days 22 hours ago
Joined: 11/29/2012
Posts: 656

It's hard to help without additional data.  Can you use wireshark and upload an ethernet packet file captured during discovery? It doesn't have to be long, 1 minute of data, during which you start applications on computers A, B and C.  Please annotate your post with the IP addresses of A, B and C.

Also, this type of question is best answered by RTI's support team.  I assume you're on a project that an RTI support contract.  Just login to the RTI support portal or send an email to support@rti.com with your customer information and they will respond.

FrankG's picture
Offline
Last seen: 3 days 20 hours ago
Joined: 03/07/2025
Posts: 2

To check that I am understanding this. Computers A, B, C on the same subnet with the same general configuration. C cannot discover A or B and neither A nor B can discover C. C shows an invalid Domain ID discovery packet.

You may wish to use DDS Ping (in the Utilities tab) to verify the right connectivity, but I suspect that the issue will be in the configuration of C. I would start by concentrating effort at C. The WireShark trace suggested by Howard will be revealing.

Temporarily disabling SHMEM transport before capturing the trace would improve the WireShark capture. I am not sure what you meant in your post, but participants on A would naturally use SHMEM rather then any IP network for on-machine communication. Same for B and C. That may be hiding a wider issue with IP networking.

- Frank