-
Notifications
You must be signed in to change notification settings - Fork 63
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
fetch command is not working for ndn #384
Comments
I think this problem is about how this is peek command interest received at relay:
interest has chunk number and found in CS and here is for fetch:
original URI without chunk number and cannot be found on CS for some reason fetch is not sending interest with some chunk number prefix and decides to send the main URI. I couldn't find what is the NDN specification for sending stream requests but I came up with 2 ways to handle this:
I think the first one should be the case since you have already done the same exception for CCNTLV: ccn-lite/src/ccnl-utils/src/ccn-lite-fetch.c Lines 270 to 281 in da0d9de
the only change is to add NDN suite to the |
Description
ccn-lite-fetch
command is not working for ndn as expected while you can get individual named objects usingpeek
with-n
flag, there is no way to get stream of objects withfetch
Steps to reproduce the issue
ccn-lite-produce
and create a named object stream out of a video file (or any file) with size 2048 (or any size. max 4096)ccn-lite-peek -s ndn2013 -n1 -u a.b.c.d\port URI
will successfully receive named object from relay.ccn-lite-fetch -s ndn2013 -u a.b.c.d\port URI
will fail.Expected results
receive NDO stream with
ccn-lite-fetch
relay
-v debug
for successfulccn-lite-peek
:peek
-v trace
for successfulccn-lite-peek
:Actual results
relay cant find NDO in CS and tries to find it in (possibly) other nodes by re-transmitting, will exist after default 7 re-transmits.
relay
-v debug
for unsuccessfulccn-lite-fetch
:fetch
-v trace
for unsuccessfulccn-lite-fetch
:Versions
Operating system: Linux
Build environment: GCC 9
The text was updated successfully, but these errors were encountered: