-
Notifications
You must be signed in to change notification settings - Fork 40
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
Error in beacon send() #10
Comments
The first thing that comes to my mind is that the -i parameter is to specify your can interface(s) and not your network interface. It should be something like -i can0 or -i vcan0. If you specify an ip address with -l you should make sure that one of your interfaces (e.g. wlan0) has that ip address assigned. Is that the case? |
I'm running it on a board with legitimate can interfaces |
hello. with usbtin working properly: sudo socketcand -i slcan0 -l 192.168.66.1 the same result with |
Same thing for me when using |
and again using a pi, pican2 and socketcand -i can0 |
Did any one got this issue solved ? |
I'm sorry that this hasn't been maintained. Have you tried using this fork here? I noticed some commits with regards to the beacon handling. |
Please check your target board's ip address configuration. If you havn't config the bcast it will report that 'Error in beacon send()' due to the broadcast address is not valid.
Solution:
And can found those desc strings from wireshark:
|
when i run it like this : socketcand -v -i wlan0 -p 29536 -l 192.168.16.112 ,it report "Error in beacon send()" ,what does this mean ? i run it on my laptop by the way . Is this a bug ?
The text was updated successfully, but these errors were encountered: