-
Notifications
You must be signed in to change notification settings - Fork 2k
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
native: txtsnd stops working on OS X after TX/TX one packet #1331
Comments
The problem apparently is that the sigio_child blocks the signal. |
Note to self: Maybe it makes more sense to proxy the interrupt communication via UNIX sockets. |
Is this still the case with the new native network implementation? (#2776) |
@LudwigOrtmann how should I test this? If all takes in terms of hardware is a Mac, I could do that, but I'm in the dark as to how to proceed for the rest of it ;) |
In theory: In practice: |
Can any OSX user report about the state of this issue? @emmanuelsearch, @kYc0o, @adjih, @thomaseichinger? |
|
I have no idea. ;) |
My PR for native UART driver (#4443), which also updates |
So we can close this? @Yonezawa-T2 did you confirm that this issue is not present anymore? |
#4443 is not yet merged. |
Ok let's wait for it, but still I don't know how to setup a tap interface on OSX to test this |
#4443 branch:
So #4443 branch can receive more than one packet. |
#4443 is merged, does this mean this issue is solved? |
I'm testing now |
But I cannot make work a tap interface :/ a common problem on Mac OSX... @Yonezawa-T2 how have you configured a tap interface on Mac OSX? I know there are some libraries but maybe there's an easier way to do it. My two errors are: In RIOT:
In OSX terminal:
|
You need 3rd party TunTap software. |
Ok let's try with that one |
The issue is gone, we can close this |
On Mac, the default application does not function correctly with 2 nodes connected by tapsetup-osx.sh
After setting up as specified in examples/default/README.md, message sending between the two nodes with txtsnd stops working after the first packet is received (message is apparently sent, but not received).
The text was updated successfully, but these errors were encountered: