-
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
gnrc_slip: Fixes #3137
gnrc_slip: Fixes #3137
Conversation
looks sane to me, but I dont have the time to test it today. Hopefully very soon... |
Had you time to test @haukepetersen? |
Ping? |
I checked out this PR, rebased it on master and got the following error when compiling for the
Seems like you forgot to add the application folder to the includes? |
Also: I don't observe this error:
(the warnings are long fixed btw). |
How do I use the slip interface in practice? The tunslip program in dist/tools/ is still used as the PC side, just like Contiki? |
@gebart yes you need to use USEMODULE += ng_slip
CFLAGS = -DNG_NETIF_NUMOF=2 |
Oh and you need to copy the
|
Addressed offline comments |
@@ -155,7 +162,8 @@ static void _slip_receive(ng_slip_dev_t *dev, size_t bytes) | |||
ng_pktbuf_hold(pkt, ng_netreg_num(pkt->type, NG_NETREG_DEMUX_CTX_ALL) - 1); | |||
|
|||
while (sendto != NULL) { | |||
DEBUG("slip: sending pkt %p to PID %u\n", pkt, sendto->pid); | |||
DEBUG("slip: sending pkt %p to PID %" PRIkernel_pid "\n", (void *)pkt, | |||
sendto->pid); | |||
ng_netapi_receive(sendto->pid, pkt); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how about ng_netapi_dispatch_receive()
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because this PR is older than this feature ;-)
Changes look good to me, and I can compile for the stm32f[3|4]discovery boards. I further tried to get the slip stuff running with the ng_networking example (just copied over the slip_params.h file and adjusted it accordingly), but no success here. After bootup, the slip interface only has this global IPv6 address Also I was wondering how slip goes together with the neighbor cache, as the slip interface does not have link layer addressing? |
22ff790
to
f011e05
Compare
Rebased to current master and addressed comments. |
Might be an issue with the neighbor discovery. Never tested it with a link-layer layer without addresses.
The neighbor cache should not become involved here. The neighbor cache is involved with Address Resolution, but since SLIP does not has any addressing, there is no Address Resolution needed. It might however be possible, that IPv6 never is able to determine the next hop. As I've said: I never really tested next hop determination with without link-layer addresses ;-). |
Let's just merge this for now and focus on debugging this later (since I'm still not having a suitable board/UART adapter to test this properly myself). |
Tested it myself today. It's the ND. It can't handle address less link-layers. Will fix tomorrow. |
ping @authmillenon |
Waiting for review. |
Wait... Did I fix ND? |
also: Needs rebase |
345f06a
to
2cf8f10
Compare
Rebased. Fix to ND I will do in a seperate PR. |
See #3628 |
2cf8f10
to
86f8ecd
Compare
Rebased to current master. |
And fixed some issues missed on rebase. |
@haukepetersen, to me it looks that this is ready to merge and fix the other problems in separate PRs. Do you agree? |
ACK, just kicked Travis... |
Fixed |
re-ACK when squashed. |
a64babe
to
8609678
Compare
Squashed. |
I found some bugs in SLIP while testing #2457. This PR fixes them in bulk.