NFD-Windows provides Windows builds of Named Data Networking software.
NFD-Windows includes the following packages:
NFD-Windows packages are free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. NFD-Windows is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
Extract the ZIP archive to an empty folder. It's recommended to choose a path without whitespaces.
Open Command Prompt, CD to the folder.
Start NFD with
START bin\nfd.exe --config etc\ndn\nfd.conf.
Start ndnping server with
START bin\ndnpingserver.exe ndn:/localhost/demo.
Start ndnping client with
bin\ndnping.exe -c 4 /localhost/demo.
If everything works fine, you should get "content from /localhost/demo" messages.
Which archive should I download?
Each archive is a different build, and is named after the UTC datetime upon build completion. You may start with the most recent build. If that doesn't work, go back to an eariler build.
What Windows versions are supported?
I'm able to run the packages on Windows 10, both 32-bit and 64-bit.
Can I use the packages on my laptop / tablet / server?
Yes and no. See disclaimer in "download" section.
What's the functional difference of these programs and their linux builds?
ndnsec-*wrapper scripts are deleted.
ndn-autoconfigtool is deleted.
ndnpingwon't print statistics if terminated with CTRL+C.
How are the packages built?
Can I build them myself?
Absolutely. Download source code and build script from NFD-Windows repository. You'll need a Ubuntu 14.04 virtual machine with at least 3GB memory and 8GB disk space.
Are the packages tested?
Did you run the unit tests?
No. They are disabled.
Why do I have to execute
Program looks for NDN KeyChain at
$HOME represents user's home directory.
But Windows exports home directory as
Why do you offer ZIP archives for downloads, rather than TAR.XZ which is more compact?
Extracting files from a ZIP archive is natively supported by Windows.
Why are EXE files so big?
They are compiled in debug mode so it's easier to debug, and linked statically so you don't need to register DLLs.
How to debug these programs?
gdb from Mingw-w64, and use
gdb to debug the program.
Debug symbols are already included in the EXE files.
I found a bug. How can I report it?
Write me an email. See my academic homepage for email address.
It would be helpful if you can include the following in your email:
gdb, if it's a crash (see "how to debug" question)