[Ndn-interest] Issue with registerPrefix using .net code

[Adam Atencio]

Got it working now. Ndn windows program is now connecting to the linux nfd.
Issue was with the setting in the nfd.conf, at some point the port for the
connection got changed, reverted to default and that fixed the rest of the
issues.
Thanks for your help.

On Thu, Apr 16, 2020, 4:11 PM Adam Atencio <adamjatencio at gmail.com> wrote:

> Thanks for the help.
>
> Still getting the same error message. Traced it down in the code to the
> connectSocket function in socket-transport.cs.
>  it calls IPEndPoint with the right IP and port 6363. It then calls
> connect with Intel network type, stream , and TCP as inputs.
> I also verified that the linux system with the Nfd is listening on the
> port 6363, using netstat -tulpn
> I also see the initial connection request go out using wireshark along
> with 2 res ends of the same message, there is no response from the nfd.
> I think the issue is occurring before use of the use of the TLv message
> encoding.
> Is this maybe because the nfd is using the linux style of socket and the
> program is trying to connect with a windows style TCP? Is there a way to
> check or configure what style of socket is used by the nfd?
>
> Also before the last response I was working to convert the ndn-cpp for use
> in windows, i had some success at getting it to compile but still need to
> rework portions of the code. I posted the steps I tools so far up on the
> stack overflow site:
>
> https://stackoverflow.com/questions/61066561/converting-a-linux-library-project-into-a-library-project-usable-in-windows
>
>
> On Thu, Apr 16, 2020, 5:00 AM Thompson, Jeff <jefft0 at remap.ucla.edu>
> wrote:
>
>> Hello Adam,
>>
>> I updated NDN-DOT-NET to add support for wire format v0.3 .  To make it
>> send packets with wire format v0.3, put the following in your application’s
>> main method:
>>
>>     WireFormat.setDefaultWireFormat(Tlv0_3WireFormat.get());
>>
>> Alternatively, to change the default for all applications, in the
>> following line:
>>
>> https://github.com/named-data/ndn-dot-net/blob/master/src/net/named_data/jndn/encoding/TlvWireFormat.cs#L25
>>
>>
>>     public class TlvWireFormat : Tlv0_2WireFormat {
>>
>> change Tlv0_2WireFormat to Tlv0_3WireFormat and rebuild.
>>
>> Thanks,
>> - Jeff T
>>
>> From: Ndn-interest <ndn-interest-bounces at lists.cs.ucla.edu> on behalf of
>> Adam Atencio via Ndn-interest <ndn-interest at lists.cs.ucla.edu>
>> Reply-To: Adam Atencio <adamjatencio at gmail.com>
>> Date: Wednesday, April 1, 2020 at 13:48:00
>> To: "ndn-interest at lists.cs.ucla.edu" <ndn-interest at lists.cs.ucla.edu>
>> Subject: [Ndn-interest] Issue with registerPrefix using .net code
>>
>> I'm running the latest NFD on a virtual ubuntu 18.04 machine and running
>> the .NET build of the CPLs on a Windows 10 VM. When I attempt to make the
>> call to register the Prefix I get the following exception(I have removed my
>> IP address from the message):
>> A connection attempt failed because the connected party did not properly
>> respond after a period of time or established connection failed because
>> connected host has failed to respond. X.X.X.X:6363
>>
>> I checked that the port 6363 is open between the machines and that they
>> can ping each other. I have followed the basic setup instructions for the
>> NFD on the http://named-data.net/doc/NFD/current/INSTALL.html page, but
>> am wondering if there is a step I am missing that would allow the Prefix to
>> register?
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20200420/69a17493/attachment.html>