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

Bi-directional IPv6 connectivity in Codelab have only uni-directional code example (TZ-997) #79

Closed
digidhamu opened this issue Jul 9, 2024 · 5 comments

Comments

@digidhamu
Copy link

I could not get the ping command to work from the BR Thread CLI when connecting to Linux or Mac IPv6 addresses. Could you please add more steps for bi-directional connectivity using the ping command? This example only covers one direction, but not from the CLI.

3.1. Bi-directional IPv6 Connectivity

@github-actions github-actions bot changed the title Bi-directional IPv6 connectivity in Codelab have only uni-directional code example Bi-directional IPv6 connectivity in Codelab have only uni-directional code example (TZ-997) Jul 9, 2024
@zwx1995esp
Copy link
Collaborator

zwx1995esp commented Jul 9, 2024

Hi, @digidhamu Did you ping the host address from thread BR device? If yes, I hope the explaination here: https://github.com/orgs/openthread/discussions/9688#discussioncomment-7771734 Hope it can help you a lot.

@zwx1995esp
Copy link
Collaborator

And the examples related in the docs, it shows that the topology should be like:

           Wi-Fi           Thread
(Host) <----------> (BR) <===========> (Thread CLI device)

The (Thread CLI device) device and (Host) can access from each other.

@digidhamu
Copy link
Author

Hi, @digidhamu Did you ping the host address from thread BR device? If yes, I hope the explaination here: https://github.com/orgs/openthread/discussions/9688#discussioncomment-7771734 Hope it can help you a lot.

Yes. Would be great if we add this in the document with simple example

@digidhamu
Copy link
Author

And the examples related in the docs, it shows that the topology should be like:

           Wi-Fi           Thread
(Host) <----------> (BR) <===========> (Thread CLI device)

The (Thread CLI device) device and (Host) can access from each other.

Thread CLI device works perfectly. However, BR also uses Thread CLI hence the confusion

@chshu
Copy link
Collaborator

chshu commented Sep 6, 2024

Added a FAQ here: https://docs.espressif.com/projects/esp-thread-br/en/latest/qa.html#q1-why-can-t-i-access-the-host-from-the-br-device-using-the-ping-command

@chshu chshu closed this as completed Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants