Bug #2473
Updated by Junxiao Shi almost 10 years ago
The I just noticed that the UDP face timeout specified in the nfd config file and the value used don't don’t agree. I have 600 seconds specified in the config file but faces actually expire at 1200 seconds. The message in the log file says 600 seconds. I don’t have an easy way to check to see if this has been fixed in newer versions. This is the released version of nfd that we run on the Testbed. It is not causing any problems, just an inconsistency. ``` $ grep idle_timeout /etc/ndn/nfd.conf idle_timeout 600 ; idle time (seconds) before closing a UDP unicast face $ nfd-status -f | grep 10.0.2.1 faceid=343 remote=udp4://10.0.2.1:6363 local=udp4://10.0.2.2:6363 expires=1112s counters={in={2i 0d 108B} out={192i 2d 18059B}} non-local on-demand point-to-point ndnops@ndnops:~$ grep 10.0.2.1 /var/log/ndn/nfd.log | grep 343 1422989686.487219 INFO: [FaceTable] Added face id=343 remote=udp4://10.0.2.1:6363 local=udp4://10.0.2.2:6363 1422990886.487276 INFO: [UdpFace] [id:343,uri:udp4://10.0.2.1:6363] Idle for more than 600 seconds, closing 1422990886.487436 INFO: [UdpFace] [id:343,uri:udp4://10.0.2.1:6363] Close tunnel 1422990886.490994 INFO: [FaceTable] Removed face id=343 remote=udp4://10.0.2.1:6363 local=udp4://10.0.2.2:6363 ndnops@ndnops:~$ nfd-status -v General NFD status: nfdId=/localhost/daemons/nfd/KEY/ksk-1406409442387/ID-CERT version=0.2.0-88-gc5173de startTime=20150203T170240.606000 currentTime=20150203T191649.046000 uptime=8048 seconds nNameTreeEntries=1113 nFibEntries=65 nPitEntries=865 nMeasurementsEntries=83 nCsEntries=8192 nInInterests=3695849 nOutInterests=962078 nInDatas=56719 nOutDatas=56949 ```