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

Exasock example not exectuing #48

Open
ManishaRiyana opened this issue Sep 3, 2021 · 6 comments
Open

Exasock example not exectuing #48

ManishaRiyana opened this issue Sep 3, 2021 · 6 comments

Comments

@ManishaRiyana
Copy link

Steps to repeat the problem:
1- Generate the .fw using exanic devkit + trigger_example
2- Update the firmware
3- Download this software source
4- make && make install
5- cd exanic-software/examples/devkit
6- gcc exasock-tcp-responder-example.c -lexanic -lexasock_ext
7- $ ./a.out 541 192.168.1.50 8000
Connected to 192.168.1.50:8000
exasock_tcp_get_device: Operation not supported

I've noticed the presence of the "/dev/exasock" as well.

Ive noticed a similar thread where On Ubuntu/Debian,
"sudo update-initramfs -k all -u""
worked as solution. But for me unfortunately it didnt help much.
I am trying for hours to solve this problem, it would be of much help if ypu could help me resolve it

@ManishaRiyana
Copy link
Author

The socket bypass state remains as EXA_BYPASS_AVAIL and is not changing to EXA_BYPASS_ACTIVE which returns an error terminating the code. I tested this by inputting printf statements in exasock/extensions/tcp.c. Any ideas on this issue would be helpful
exasock_tcp_get_device

@ManishaRiyana
Copy link
Author

Operation_not_supported

@korst1k
Copy link

korst1k commented Oct 11, 2021

The same problem for exasock_tcp_build_header() call:
image

@ManishaRiyana
Copy link
Author

Check if your network connection is being directed through the exanic IP interface? Sometimes linux tends to mess up multiple networks present under the same subnet

@korst1k
Copy link

korst1k commented Oct 13, 2021

Yep, we checked this up, setup correct route for endpoint and the problem is gone.

@ManishaRiyana
Copy link
Author

ManishaRiyana commented Oct 13, 2021 via email

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

2 participants