[ndnSIM] Differences between NFD and NFD integrated with ndnSIM

[Junxiao Shi]

Hi Peter

According to Emulation Overview
<https://www.nsnam.org/docs/release/3.30/models/html/emulation-overview.html>,
ns-3 should be able to connect to a real network via FdNetDevice or
TapBridge.
Therefore, the limitation lies in ndnSIM not being able to support
<https://ndnsim.net/2.7/doxygen/ndn-stack-helper_8cpp_source.html#l00069>
any NetDevice other than PointToPointNetDevice.
Question for ndnSIM developers is that, why ndnSIM cannot support other
NetDevice types?

Direct Code Execution (DCE) would not allow you to connect to an external
host. It integrates an application into the ns-3 experiment, by dynamically
replacing its network-related syscalls with equivalent calls into ns-3
network stack.
In the past, I managed to run ccnd (predecessor of NFD) through DCE.
However, running real NFD in DCE would be difficult due to NFD's use of
pcap and netlink sockets.

Yours, Junxiao

On Tue, Oct 1, 2019 at 10:07 PM Spyridon (Spyros) Mastorakis <
mastorakis at cs.ucla.edu> wrote:

> Yes, this limitation is still there and is due to the way that ns-3
> operates. It might be possible to relax this assumption (to some extent
> which I am not aware of) if someone could look into the Direct Code
> Execution (DCE) mode of ns-3.
>
>
> On Oct 1, 2019, at 4:08 AM, Peter Maynard <pmaynard01 at qub.ac.uk> wrote:
>
> Is it still true that ndnSIM is unable to connect to an application
> running on an external host? (section 7.1 Current ndnSIM Limitations)
> If so, is that an NS-3 limitation or ndnSIM?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20191002/6600ff47/attachment.html>