-
Notifications
You must be signed in to change notification settings - Fork 4
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
Examine Traffic #965
Comments
Suggested revision for 'Install tcp' section:
Nothing shows up for both unencrypted and encrypted data packet sections: This page should also indicate that following the steps on Setting up security are a prerequisite for the Enable encryption section. |
Thanks for trying this out. I agree the test case should better inform users to follow the previous sections of the Security tutorial and have taken note to improve this for next time audrow/yatm#366 Noted on not being able to display encrypted or unencrypted data packages. Could I check the version of |
this can be reproducible for fast-dds, using cyclone we can see the data payload via UDP with we can see fast-dds listens on the following ports, as expected. root@tomoyafujita:~# netstat -tulpn | grep -e talker -e listener
udp 0 0 0.0.0.0:7400 0.0.0.0:* 3304/listener
udp 0 0 0.0.0.0:7400 0.0.0.0:* 3289/talker
udp 0 0 0.0.0.0:7410 0.0.0.0:* 3289/talker
udp 0 0 0.0.0.0:7411 0.0.0.0:* 3289/talker
udp 0 0 0.0.0.0:7412 0.0.0.0:* 3304/listener
udp 0 0 0.0.0.0:7413 0.0.0.0:* 3304/listener
udp 0 0 0.0.0.0:57153 0.0.0.0:* 3289/talker
udp 0 0 43.135.146.89:59268 0.0.0.0:* 3289/talker
udp 0 0 10.0.0.137:60530 0.0.0.0:* 3289/talker
udp 0 0 43.135.146.89:45435 0.0.0.0:* 3304/listener
udp 0 0 10.0.0.137:47449 0.0.0.0:* 3304/listener
udp 0 0 0.0.0.0:47705 0.0.0.0:* 3304/listener but never put the data on the network interface, i guess. this could be related to share memory transport or data sharing. (expecting that data sharing cannot be enabled since string is not PoD.) @MiguelCompany any thoughts? |
Yes. Running on the same host will by default use the shared memory transport, so no traffic will be seen on udp ports You would see the traffic if the talker and listener are run on different hosts. |
@MiguelCompany thanks for the confirmation. @Yadunund i will try to come up with PR for this, probably adding some note for |
@Yadunund how about ros2/ros2_documentation#3683, we need to backport this to iron only. |
@Yadunund we can close this, addressed in ros2/ros2_documentation#3683. CC: @clalancette |
Awesome, thanks for taking care of that! |
Check the documentation for the 'Examine Traffic' page
Setup
Links
Checks
You can find the code used to generate this test case here
The text was updated successfully, but these errors were encountered: