Skip to content
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

Provide a tool to diagnose network setup issues #476

Open
azeey opened this issue Jan 29, 2024 · 1 comment
Open

Provide a tool to diagnose network setup issues #476

azeey opened this issue Jan 29, 2024 · 1 comment
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@azeey
Copy link
Contributor

azeey commented Jan 29, 2024

Desired behavior

Many new users run into problems using Gazebo due to improper network configuration. It would be great if we can provide a tool to diagnose the problem. As a first step, we can provide a tool like
https://docs.ros.org/en/rolling/How-To-Guides/Installation-Troubleshooting.html#enable-multicast that checks if there is a UDP multicast problem blocking discovery.

Alternatives considered

n/a

Implementation suggestion

This could be a gz command.

Additional context

Related issues:
gazebosim/gz-sim#1879
gazebosim/gz-sim#2285

@azeey azeey added enhancement New feature or request help wanted Extra attention is needed labels Jan 29, 2024
@mjcarroll mjcarroll moved this from Inbox to To do in Core development Jan 30, 2024
@mapi-ng
Copy link

mapi-ng commented Aug 11, 2024

Hi @azeey, thank you for bringing this issue.

I have just recently installed ROS2 and Gazebo and I ran into this issue.

I think just having a timeout and an error message with suggestion to enable multicast would be of great help to new users. As a user trying to troubleshoot this kind of issue it would not be my first thought to run a separate gz command for network diagnosis - here is why.

Before I realized that it was sufficient to Enable multicast, I had troubles understanding what the real problem was. My first thought was about graphics driver configuration.

Only after using verbose output with -v 4 debug level did I understand that the issue was rather network related and only then was I able to find this related issue: gazebosim/gz-sim#2285

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
Status: To do
Development

No branches or pull requests

2 participants