[Nfd-dev] Mini NDN with NDN Traffic Generator

[Simon Edelhaus]

Hi All!

How would you guys compare NDN initiative to something like IPv17 ?

Is there  a slide deck comparing the 2 approaches?


-- ttfn
Simon Edelhaus
California 2015

On Wed, Jul 15, 2015 at 10:27 AM, Vince Lehman (vslehman) <
vslehman at memphis.edu> wrote:

>  Hi Navdeep,
>
>  When you are specifying the configuration file names for the NDN traffic
> server and client, are you using the full absolute path for the file?
> Mini-NDN sets the home folder for each node as /tmp/$nodeName. When
> executing a command as a specific node, the HOME variable will be set to
> that node’s home folder. So, using a relative path based on your home
> folder or based on the current directory will not work.
>
>  You should be able to use the full absolute path for the configuration
> files or copy the configuration files into the respective node’s home
> folder and use a relative path.
>
> --
>  Vince Lehman
>
>  On Jul 15, 2015, at 12:00 PM, Navdeep Uniyal <navdeep.uniyal at neclab.eu>
> wrote:
>
>   Hello
>
>
>
> I am experimenting traffic generation on MiniNDN, for this I am trying to
> use NDN Traffic generator
> https://github.com/named-data/ndn-traffic-generator. Has anyone tried it
> before, if yes please share your inputs as currently in Mininet CLI it is
> not recognizing the configuration file.
>
>
>
>
>
> Best Regards,
>
> Navdeep Uniyal
>
>
>  _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>
>
>
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20150715/bcad77d6/attachment.html>