-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Unable to work with two bridges on different namespace #305
Comments
Hi @iamkashish, can you please share the logs of the two bridges when setting |
Hi @gabrik , So I tried with peer mode with deny in config file, the config file of left machine will have "^/right.*" in deny and vice-versa. The logs are left_log_2 and right_log_2. |
Hey @gabrik , |
Hey @gabrik , |
Hi @iamkashish The only way to exchange the data now is to have both sides using same namespace or one side without namespace. I think your requirement is indeed useful, but we need to think of a better way for bridge to identify whether |
Describe the bug
If I start one bridge with a namespace "/left" and then the other with namespace "/right", the topics from left to right or vice-versa are created. But the publisher get lost, meaning: ros2 topic echo /right/ doesn't show anything.
But if I use one bridge with a namespace "/left" and then other with no namespace. It works fine.
Maybe there is some silly mistake, but I tried various ways.
To reproduce
zenoh-bridge-ros2dds --namespace left -e tcp/<left-ip-address>:7447
in one machine.zenoh-bridge-ros2dds --namespace right -e tcp/<right-ip-address>:7447
in another machine.ros2 run demo_nodes_cpp talker
in left machineros2 echo /left/chatter
in right machineSystem info
The text was updated successfully, but these errors were encountered: