[Nfd-dev] UDP face not being created to client end host

[Dehart, John]

I think I found the problem.
This node has some firewall rules.

John

On Aug 3, 2017, at 3:47 PM, Dehart, John <jdd at wustl.edu<mailto:jdd at wustl.edu>> wrote:


I get some initial ones for Testbed neighbors:

ndnops at ndn:/var/log/ndn$ grep -i "new peer" nfd.log
1501792940.296285 TRACE: [UdpChannel] [udp4://0.0.0.0:6363] New peer 200.239.93.10:6363
1501792947.979605 TRACE: [UdpChannel] [udp4://0.0.0.0:6363] New peer 193.147.51.186:6363
ndnops at ndn:/var/log/ndn$

But when I try to connect from a client I don’t see any.

Here are all the UdpChannel log messages:

ndnops at ndn:/var/log/ndn$ grep -i UdpChannel nfd.log
1501792936.274074 INFO: [UdpChannel] [udp4://0.0.0.0:6363] Creating channel
1501792936.274203 DEBUG: [UdpChannel] [udp4://0.0.0.0:6363] Started listening
1501792936.274213 INFO: [UdpChannel] [udp6://[::]:6363] Creating channel
1501792936.274321 DEBUG: [UdpChannel] [udp6://[::]:6363] Started listening
1501792940.296285 TRACE: [UdpChannel] [udp4://0.0.0.0:6363] New peer 200.239.93.10:6363
1501792947.979605 TRACE: [UdpChannel] [udp4://0.0.0.0:6363] New peer 193.147.51.186:6363
1501792968.813927 TRACE: [UdpChannel] [udp4://0.0.0.0:6363] Reusing existing face for 193.147.51.186:6363
1501792969.024214 TRACE: [UdpChannel] [udp4://0.0.0.0:6363] Reusing existing face for 200.239.93.10:6363
ndnops at ndn:/var/log/ndn$


John

On Aug 3, 2017, at 3:40 PM, Davide Pesavento <davide.pesavento at lip6.fr<mailto:davide.pesavento at lip6.fr>> wrote:

John,

If you enable TRACE logging for UdpChannel, do you see any messages starting with "New peer"?

Thanks,
Davide

On Thu, Aug 3, 2017, 4:24 PM Dehart, John <jdd at wustl.edu<mailto:jdd at wustl.edu>> wrote:

All:

I have an NDN Testbed node, COPELABS, (and possibly others) that isn’t creating a UDP face back toward
my client when I try to connect to it. I’ve tried from a couple of end hosts and the same thing happens.

When I run ndndump on COPELABS, I see ndn packets arriving from my client but
with DEBUG output from nfd those packets never show up in the log file.

If I change to use TCP, it works fine.

On COPELABS:
ndnops at ndn:~$ nfd --version
0.5.1-73-gbc7cb95
ndnops at ndn:~$


On my laptop:
jdd> nfd --version
0.5.1
jdd>

Any ideas on what could be causing this?

John

_______________________________________________
Nfd-dev mailing list
Nfd-dev at lists.cs.ucla.edu<mailto: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<mailto: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/20170803/d7c35dec/attachment.html>