-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
echo_client sample return: Cannot connect to TCP remote (IPv6): 110 #24282
Comments
I tried net-tools echo-server instead of echo_server sample, but it is the same issue. |
In your setup zephyr will get following IPv4 addresses 192.0.2.1 (server), 192.0.2.2 (client) and your Linux host will get 192.0.2.2. So there is IPv4 address conflict. Simplest solution is to set zeth in your Linux host to have some other address like 192.0.2.3. Just go to net-tools directory, copy zeth.conf to zeth3.conf, and then edit zeth3.conf and set the addresses correctly. Then do |
Update: linux server<->posix client case works, posix<->posix not. @jukkar Thanks. It make sense. Please help us to check it. |
I managed to get echo-server<->echo_client working using two native_posix processes. The procedure is a bit complicated but basic steps were already described in Create
Create
Terminal 1:
Terminal 2:
Terminal 3:
Terminal 4:
Terminal 5:
Also if you have firewall enabled in your host, you need to allow traffic between zeth.1, zeth.2 and zeth-br interfaces. |
This is not a bug, it is just a matter of configuring the system to setup interfaces and route traffic between them. |
FYI, I created #25136 that adds proper documentation for connecting multiple Zephyr instances together. |
Describe the bug
I have tried echo_server sample, it works. And I leave it as the "server“,but got error after I start echo_client sample.
To Reproduce
Steps to reproduce the behavior:
Terminal 0
./net-setup.sh
Terminal 1
Terminal 2
Screenshots or console output
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: