From Navdeep.Uniyal at neclab.eu Mon Feb 22 05:26:31 2016 From: Navdeep.Uniyal at neclab.eu (Navdeep Uniyal) Date: Mon, 22 Feb 2016 13:26:31 +0000 Subject: [Mini-NDN] Minindn Install error Message-ID: <15421E67B274CD4AB5F6AEA46A684C370384CEEF@Hydra.office.hd> Hi All, I am facing issues while running minindn after fresh install: On checking the nfd-status, I am getting below mentioned error: ERROR: error while connecting to the forwarder (No such file or directory) Then on Mininet CLI> a nfd-start ( this worked with no errors) After this, on checking nfd-status -b, I got the following error: Address family not supported by protocol In order to resolve this, I disabled IpV6 address in nfd.conf And now I am getting the following error: 1456146897.968430 INFO: [StrategyChoice] setDefaultStrategy /localhost/nfd/strategy/best-route/%FD%04 1456146897.968833 INFO: [InternalForwarderTransport] [id=0,local=internal://,remote=internal://] Creating transport 1456146897.968917 INFO: [FaceTable] Added face id=1 remote=internal:// local=internal:// 1456146897.969463 WARNING: [CommandValidator] Wildcard identity is intended for demo purpose only and SHOULD NOT be used in production environment 1456146897.969500 INFO: [CommandValidator] Giving privilege "faces" to identity wildcard 1456146897.969529 INFO: [CommandValidator] Giving privilege "fib" to identity wildcard 1456146897.969558 INFO: [CommandValidator] Giving privilege "strategy-choice" to identity wildcard 1456146897.969759 INFO: [StrategyChoice] changeStrategy(/ndn/broadcast) from /localhost/nfd/strategy/best-route/%FD%04 to /localhost/nfd/strategy/multicast/%FD%01 1456146897.970062 INFO: [StrategyChoice] changeStrategy(/localhost) from /localhost/nfd/strategy/best-route/%FD%04 to /localhost/nfd/strategy/multicast/%FD%01 1456146897.970340 INFO: [StrategyChoice] changeStrategy(/localhost/nfd) from /localhost/nfd/strategy/multicast/%FD%01 to /localhost/nfd/strategy/best-route/%FD%04 1456146897.970628 INFO: [TablesConfigSection] Setting CS max packets to 65536 1456146897.970979 INFO: [MulticastUdpTransport] [id=0,local=udp4://1.0.0.78:56363,remote=udp4://224.0.23.170:56363] Creating transport 1456146897.971054 INFO: [FaceTable] Added face id=256 remote=udp4://224.0.23.170:56363 local=udp4://1.0.0.78:56363 1456146897.971157 INFO: [MulticastUdpTransport] [id=0,local=udp4://1.0.0.70:56363,remote=udp4://224.0.23.170:56363] Creating transport 1456146897.971226 INFO: [FaceTable] Added face id=257 remote=udp4://224.0.23.170:56363 local=udp4://1.0.0.70:56363 1456146897.971315 INFO: [MulticastUdpTransport] [id=0,local=udp4://1.0.0.50:56363,remote=udp4://224.0.23.170:56363] Creating transport 1456146897.971383 INFO: [FaceTable] Added face id=258 remote=udp4://224.0.23.170:56363 local=udp4://1.0.0.50:56363 1456146897.971462 INFO: [EthernetTransport] [id=0,local=dev://neu-eth0,remote=ether://[01:00:5e:00:17:aa]] Creating transport 1456146897.983192 INFO: [FaceTable] Added face id=259 remote=ether://[01:00:5e:00:17:aa] local=dev://neu-eth0 1456146897.983264 INFO: [EthernetTransport] [id=0,local=dev://neu-eth2,remote=ether://[01:00:5e:00:17:aa]] Creating transport 1456146897.995094 INFO: [FaceTable] Added face id=260 remote=ether://[01:00:5e:00:17:aa] local=dev://neu-eth2 1456146897.995166 INFO: [EthernetTransport] [id=0,local=dev://neu-eth1,remote=ether://[01:00:5e:00:17:aa]] Creating transport 1456146898.007089 INFO: [FaceTable] Added face id=261 remote=ether://[01:00:5e:00:17:aa] local=dev://neu-eth1 1456146898.007160 WARNING: [CommandValidator] Wildcard identity is intended for demo purpose only and SHOULD NOT be used in production environment 1456146898.007191 INFO: [CommandValidator] Giving privilege "faces" to identity wildcard 1456146898.007274 INFO: [CommandValidator] Giving privilege "fib" to identity wildcard 1456146898.007321 INFO: [CommandValidator] Giving privilege "strategy-choice" to identity wildcard 1456146898.007462 INFO: [InternalForwarderTransport] [id=0,local=null://,remote=null://] Creating transport 1456146898.007514 INFO: [FaceTable] Added face id=255 remote=null:// local=null:// 1456146898.010224 INFO: [InternalForwarderTransport] [id=0,local=contentstore://,remote=contentstore://] Creating transport 1456146898.010280 INFO: [FaceTable] Added face id=254 remote=contentstore:// local=contentstore:// 1456146898.012151 INFO: [PrivilegeHelper] dropped to effective uid=0 gid=0 1456146898.013472 INFO: [AutoPrefixPropagator] Load auto_prefix_propagate section in rib section 1456146898.013665 INFO: [AutoPrefixPropagator] Load auto_prefix_propagate section in rib section 1456146898.013715 INFO: [RibManager] Listening on: /localhost/nfd/rib 1456146898.017241 INFO: [RibManager] Start monitoring face create/destroy events 1456146898.019405 INFO: [UnixStreamTransport] [id=0,local=unix:///run/nfd.sock,remote=fd://31] Creating transport 1456146898.019482 INFO: [FaceTable] Added face id=262 remote=fd://31 local=unix:///run/nfd.sock 1456146898.025726 INFO: [AutoPrefixPropagator] local registration only for /localhost/nfd/rib ERROR: error while connecting to the forwarder (No such file or directory) Please help in resolving the issue. (* I used ./install -mrfti to install minindn and there were no errors) Regards, Navdeep Uniyal -------------- next part -------------- An HTML attachment was scrubbed... URL: From agawande at memphis.edu Mon Feb 22 07:14:43 2016 From: agawande at memphis.edu (Ashlesh Gawande (agawande)) Date: Mon, 22 Feb 2016 15:14:43 +0000 Subject: [Mini-NDN] Minindn Install error Message-ID: Can you try to run NFD without mini-NDN? Also might need to run in background: a nfd-start & Ashlesh On Feb 22, 2016 7:27 AM, Navdeep Uniyal wrote: Hi All, I am facing issues while running minindn after fresh install: On checking the nfd-status, I am getting below mentioned error: ERROR: error while connecting to the forwarder (No such file or directory) Then on Mininet CLI> a nfd-start ( this worked with no errors) After this, on checking nfd-status ?b, I got the following error: Address family not supported by protocol In order to resolve this, I disabled IpV6 address in nfd.conf And now I am getting the following error: 1456146897.968430 INFO: [StrategyChoice] setDefaultStrategy /localhost/nfd/strategy/best-route/%FD%04 1456146897.968833 INFO: [InternalForwarderTransport] [id=0,local=internal://,remote=internal://] Creating transport 1456146897.968917 INFO: [FaceTable] Added face id=1 remote=internal:// local=internal:// 1456146897.969463 WARNING: [CommandValidator] Wildcard identity is intended for demo purpose only and SHOULD NOT be used in production environment 1456146897.969500 INFO: [CommandValidator] Giving privilege "faces" to identity wildcard 1456146897.969529 INFO: [CommandValidator] Giving privilege "fib" to identity wildcard 1456146897.969558 INFO: [CommandValidator] Giving privilege "strategy-choice" to identity wildcard 1456146897.969759 INFO: [StrategyChoice] changeStrategy(/ndn/broadcast) from /localhost/nfd/strategy/best-route/%FD%04 to /localhost/nfd/strategy/multicast/%FD%01 1456146897.970062 INFO: [StrategyChoice] changeStrategy(/localhost) from /localhost/nfd/strategy/best-route/%FD%04 to /localhost/nfd/strategy/multicast/%FD%01 1456146897.970340 INFO: [StrategyChoice] changeStrategy(/localhost/nfd) from /localhost/nfd/strategy/multicast/%FD%01 to /localhost/nfd/strategy/best-route/%FD%04 1456146897.970628 INFO: [TablesConfigSection] Setting CS max packets to 65536 1456146897.970979 INFO: [MulticastUdpTransport] [id=0,local=udp4://1.0.0.78:56363,remote=udp4://224.0.23.170:56363] Creating transport 1456146897.971054 INFO: [FaceTable] Added face id=256 remote=udp4://224.0.23.170:56363 local=udp4://1.0.0.78:56363 1456146897.971157 INFO: [MulticastUdpTransport] [id=0,local=udp4://1.0.0.70:56363,remote=udp4://224.0.23.170:56363] Creating transport 1456146897.971226 INFO: [FaceTable] Added face id=257 remote=udp4://224.0.23.170:56363 local=udp4://1.0.0.70:56363 1456146897.971315 INFO: [MulticastUdpTransport] [id=0,local=udp4://1.0.0.50:56363,remote=udp4://224.0.23.170:56363] Creating transport 1456146897.971383 INFO: [FaceTable] Added face id=258 remote=udp4://224.0.23.170:56363 local=udp4://1.0.0.50:56363 1456146897.971462 INFO: [EthernetTransport] [id=0,local=dev://neu-eth0,remote=ether://[01:00:5e:00:17:aa]] Creating transport 1456146897.983192 INFO: [FaceTable] Added face id=259 remote=ether://[01:00:5e:00:17:aa] local=dev://neu-eth0 1456146897.983264 INFO: [EthernetTransport] [id=0,local=dev://neu-eth2,remote=ether://[01:00:5e:00:17:aa]] Creating transport 1456146897.995094 INFO: [FaceTable] Added face id=260 remote=ether://[01:00:5e:00:17:aa] local=dev://neu-eth2 1456146897.995166 INFO: [EthernetTransport] [id=0,local=dev://neu-eth1,remote=ether://[01:00:5e:00:17:aa]] Creating transport 1456146898.007089 INFO: [FaceTable] Added face id=261 remote=ether://[01:00:5e:00:17:aa] local=dev://neu-eth1 1456146898.007160 WARNING: [CommandValidator] Wildcard identity is intended for demo purpose only and SHOULD NOT be used in production environment 1456146898.007191 INFO: [CommandValidator] Giving privilege "faces" to identity wildcard 1456146898.007274 INFO: [CommandValidator] Giving privilege "fib" to identity wildcard 1456146898.007321 INFO: [CommandValidator] Giving privilege "strategy-choice" to identity wildcard 1456146898.007462 INFO: [InternalForwarderTransport] [id=0,local=null://,remote=null://] Creating transport 1456146898.007514 INFO: [FaceTable] Added face id=255 remote=null:// local=null:// 1456146898.010224 INFO: [InternalForwarderTransport] [id=0,local=contentstore://,remote=contentstore://] Creating transport 1456146898.010280 INFO: [FaceTable] Added face id=254 remote=contentstore:// local=contentstore:// 1456146898.012151 INFO: [PrivilegeHelper] dropped to effective uid=0 gid=0 1456146898.013472 INFO: [AutoPrefixPropagator] Load auto_prefix_propagate section in rib section 1456146898.013665 INFO: [AutoPrefixPropagator] Load auto_prefix_propagate section in rib section 1456146898.013715 INFO: [RibManager] Listening on: /localhost/nfd/rib 1456146898.017241 INFO: [RibManager] Start monitoring face create/destroy events 1456146898.019405 INFO: [UnixStreamTransport] [id=0,local=unix:///run/nfd.sock,remote=fd://31] Creating transport 1456146898.019482 INFO: [FaceTable] Added face id=262 remote=fd://31 local=unix:///run/nfd.sock 1456146898.025726 INFO: [AutoPrefixPropagator] local registration only for /localhost/nfd/rib ERROR: error while connecting to the forwarder (No such file or directory) Please help in resolving the issue. (* I used ./install ?mrfti to install minindn and there were no errors) Regards, Navdeep Uniyal -------------- next part -------------- An HTML attachment was scrubbed... URL: From Navdeep.Uniyal at neclab.eu Mon Feb 22 07:54:53 2016 From: Navdeep.Uniyal at neclab.eu (Navdeep Uniyal) Date: Mon, 22 Feb 2016 15:54:53 +0000 Subject: [Mini-NDN] Minindn Install error In-Reply-To: References: Message-ID: <15421E67B274CD4AB5F6AEA46A684C370384D722@Hydra.office.hd> Hi Ashlesh, I tried both the ways, without minindn, NFS is running fine as I can see the nfd-status whereas with minindn, it is giving me error : ERROR: error while connecting to the forwarder (No such file or directory)? Regards, Navdeep Uniyal From: Ashlesh Gawande (agawande) [mailto:agawande at memphis.edu] Sent: Montag, 22. Februar 2016 16:15 To: Navdeep Uniyal Cc: mini-ndn at lists.cs.ucla.edu Subject: Re: [Mini-NDN] Minindn Install error Can you try to run NFD without mini-NDN? Also might need to run in background: a nfd-start & Ashlesh On Feb 22, 2016 7:27 AM, Navdeep Uniyal > wrote: Hi All, I am facing issues while running minindn after fresh install: On checking the nfd-status, I am getting below mentioned error: ERROR: error while connecting to the forwarder (No such file or directory) Then on Mininet CLI> a nfd-start ( this worked with no errors) After this, on checking nfd-status ?b, I got the following error: Address family not supported by protocol In order to resolve this, I disabled IpV6 address in nfd.conf And now I am getting the following error: 1456146897.968430 INFO: [StrategyChoice] setDefaultStrategy /localhost/nfd/strategy/best-route/%FD%04 1456146897.968833 INFO: [InternalForwarderTransport] [id=0,local=internal://,remote=internal://] Creating transport 1456146897.968917 INFO: [FaceTable] Added face id=1 remote=internal:// local=internal:// 1456146897.969463 WARNING: [CommandValidator] Wildcard identity is intended for demo purpose only and SHOULD NOT be used in production environment 1456146897.969500 INFO: [CommandValidator] Giving privilege "faces" to identity wildcard 1456146897.969529 INFO: [CommandValidator] Giving privilege "fib" to identity wildcard 1456146897.969558 INFO: [CommandValidator] Giving privilege "strategy-choice" to identity wildcard 1456146897.969759 INFO: [StrategyChoice] changeStrategy(/ndn/broadcast) from /localhost/nfd/strategy/best-route/%FD%04 to /localhost/nfd/strategy/multicast/%FD%01 1456146897.970062 INFO: [StrategyChoice] changeStrategy(/localhost) from /localhost/nfd/strategy/best-route/%FD%04 to /localhost/nfd/strategy/multicast/%FD%01 1456146897.970340 INFO: [StrategyChoice] changeStrategy(/localhost/nfd) from /localhost/nfd/strategy/multicast/%FD%01 to /localhost/nfd/strategy/best-route/%FD%04 1456146897.970628 INFO: [TablesConfigSection] Setting CS max packets to 65536 1456146897.970979 INFO: [MulticastUdpTransport] [id=0,local=udp4://1.0.0.78:56363,remote=udp4://224.0.23.170:56363] Creating transport 1456146897.971054 INFO: [FaceTable] Added face id=256 remote=udp4://224.0.23.170:56363 local=udp4://1.0.0.78:56363 1456146897.971157 INFO: [MulticastUdpTransport] [id=0,local=udp4://1.0.0.70:56363,remote=udp4://224.0.23.170:56363] Creating transport 1456146897.971226 INFO: [FaceTable] Added face id=257 remote=udp4://224.0.23.170:56363 local=udp4://1.0.0.70:56363 1456146897.971315 INFO: [MulticastUdpTransport] [id=0,local=udp4://1.0.0.50:56363,remote=udp4://224.0.23.170:56363] Creating transport 1456146897.971383 INFO: [FaceTable] Added face id=258 remote=udp4://224.0.23.170:56363 local=udp4://1.0.0.50:56363 1456146897.971462 INFO: [EthernetTransport] [id=0,local=dev://neu-eth0,remote=ether://[01:00:5e:00:17:aa]] Creating transport 1456146897.983192 INFO: [FaceTable] Added face id=259 remote=ether://[01:00:5e:00:17:aa] local=dev://neu-eth0 1456146897.983264 INFO: [EthernetTransport] [id=0,local=dev://neu-eth2,remote=ether://[01:00:5e:00:17:aa]] Creating transport 1456146897.995094 INFO: [FaceTable] Added face id=260 remote=ether://[01:00:5e:00:17:aa] local=dev://neu-eth2 1456146897.995166 INFO: [EthernetTransport] [id=0,local=dev://neu-eth1,remote=ether://[01:00:5e:00:17:aa]] Creating transport 1456146898.007089 INFO: [FaceTable] Added face id=261 remote=ether://[01:00:5e:00:17:aa] local=dev://neu-eth1 1456146898.007160 WARNING: [CommandValidator] Wildcard identity is intended for demo purpose only and SHOULD NOT be used in production environment 1456146898.007191 INFO: [CommandValidator] Giving privilege "faces" to identity wildcard 1456146898.007274 INFO: [CommandValidator] Giving privilege "fib" to identity wildcard 1456146898.007321 INFO: [CommandValidator] Giving privilege "strategy-choice" to identity wildcard 1456146898.007462 INFO: [InternalForwarderTransport] [id=0,local=null://,remote=null://] Creating transport 1456146898.007514 INFO: [FaceTable] Added face id=255 remote=null:// local=null:// 1456146898.010224 INFO: [InternalForwarderTransport] [id=0,local=contentstore://,remote=contentstore://] Creating transport 1456146898.010280 INFO: [FaceTable] Added face id=254 remote=contentstore:// local=contentstore:// 1456146898.012151 INFO: [PrivilegeHelper] dropped to effective uid=0 gid=0 1456146898.013472 INFO: [AutoPrefixPropagator] Load auto_prefix_propagate section in rib section 1456146898.013665 INFO: [AutoPrefixPropagator] Load auto_prefix_propagate section in rib section 1456146898.013715 INFO: [RibManager] Listening on: /localhost/nfd/rib 1456146898.017241 INFO: [RibManager] Start monitoring face create/destroy events 1456146898.019405 INFO: [UnixStreamTransport] [id=0,local=unix:///run/nfd.sock,remote=fd://31] Creating transport 1456146898.019482 INFO: [FaceTable] Added face id=262 remote=fd://31 local=unix:///run/nfd.sock 1456146898.025726 INFO: [AutoPrefixPropagator] local registration only for /localhost/nfd/rib ERROR: error while connecting to the forwarder (No such file or directory) Please help in resolving the issue. (* I used ./install ?mrfti to install minindn and there were no errors) Regards, Navdeep Uniyal -------------- next part -------------- An HTML attachment was scrubbed... URL: From vslehman at memphis.edu Mon Feb 22 09:18:04 2016 From: vslehman at memphis.edu (Vince Lehman (vslehman)) Date: Mon, 22 Feb 2016 17:18:04 +0000 Subject: [Mini-NDN] Minindn Install error In-Reply-To: <15421E67B274CD4AB5F6AEA46A684C370384D722@Hydra.office.hd> References: <15421E67B274CD4AB5F6AEA46A684C370384D722@Hydra.office.hd> Message-ID: Hi Navdeep, Could you try running Mini-NDN with a minimal topology? You can save the following configuration as ?debug.topo? and run the topology using the command ?sudo minindn debug.topo?: [nodes] debug: _ nfd-log-level=DEBUG [links] Once the ?mininet>? prompt appears, can you provide the following information in an email to help us diagnose the issue? * Issue the command "debug nfd-status -b? on the Mini-NDN command line and send the output; * Attach the file "/tmp/debug/debug.log?; and, * In a separate terminal window, while Mini-NDN is still running, issue the following commands and send the output: * ps aux | grep "nfd ?config" * ls /var/run/ | grep debug -- Vince Lehman On Feb 22, 2016, at 9:54 AM, Navdeep Uniyal > wrote: Hi Ashlesh, I tried both the ways, without minindn, NFS is running fine as I can see the nfd-status whereas with minindn, it is giving me error : ERROR: error while connecting to the forwarder (No such file or directory)? Regards, Navdeep Uniyal From: Ashlesh Gawande (agawande) [mailto:agawande at memphis.edu] Sent: Montag, 22. Februar 2016 16:15 To: Navdeep Uniyal Cc: mini-ndn at lists.cs.ucla.edu Subject: Re: [Mini-NDN] Minindn Install error Can you try to run NFD without mini-NDN? Also might need to run in background: a nfd-start & Ashlesh On Feb 22, 2016 7:27 AM, Navdeep Uniyal > wrote: Hi All, I am facing issues while running minindn after fresh install: On checking the nfd-status, I am getting below mentioned error: ERROR: error while connecting to the forwarder (No such file or directory) Then on Mininet CLI> a nfd-start ( this worked with no errors) After this, on checking nfd-status ?b, I got the following error: Address family not supported by protocol In order to resolve this, I disabled IpV6 address in nfd.conf And now I am getting the following error: 1456146897.968430 INFO: [StrategyChoice] setDefaultStrategy /localhost/nfd/strategy/best-route/%FD%04 1456146897.968833 INFO: [InternalForwarderTransport] [id=0,local=internal://,remote=internal://] Creating transport 1456146897.968917 INFO: [FaceTable] Added face id=1 remote=internal:// local=internal:// 1456146897.969463 WARNING: [CommandValidator] Wildcard identity is intended for demo purpose only and SHOULD NOT be used in production environment 1456146897.969500 INFO: [CommandValidator] Giving privilege "faces" to identity wildcard 1456146897.969529 INFO: [CommandValidator] Giving privilege "fib" to identity wildcard 1456146897.969558 INFO: [CommandValidator] Giving privilege "strategy-choice" to identity wildcard 1456146897.969759 INFO: [StrategyChoice] changeStrategy(/ndn/broadcast) from /localhost/nfd/strategy/best-route/%FD%04 to /localhost/nfd/strategy/multicast/%FD%01 1456146897.970062 INFO: [StrategyChoice] changeStrategy(/localhost) from /localhost/nfd/strategy/best-route/%FD%04 to /localhost/nfd/strategy/multicast/%FD%01 1456146897.970340 INFO: [StrategyChoice] changeStrategy(/localhost/nfd) from /localhost/nfd/strategy/multicast/%FD%01 to /localhost/nfd/strategy/best-route/%FD%04 1456146897.970628 INFO: [TablesConfigSection] Setting CS max packets to 65536 1456146897.970979 INFO: [MulticastUdpTransport] [id=0,local=udp4://1.0.0.78:56363,remote=udp4://224.0.23.170:56363] Creating transport 1456146897.971054 INFO: [FaceTable] Added face id=256 remote=udp4://224.0.23.170:56363 local=udp4://1.0.0.78:56363 1456146897.971157 INFO: [MulticastUdpTransport] [id=0,local=udp4://1.0.0.70:56363,remote=udp4://224.0.23.170:56363] Creating transport 1456146897.971226 INFO: [FaceTable] Added face id=257 remote=udp4://224.0.23.170:56363 local=udp4://1.0.0.70:56363 1456146897.971315 INFO: [MulticastUdpTransport] [id=0,local=udp4://1.0.0.50:56363,remote=udp4://224.0.23.170:56363] Creating transport 1456146897.971383 INFO: [FaceTable] Added face id=258 remote=udp4://224.0.23.170:56363 local=udp4://1.0.0.50:56363 1456146897.971462 INFO: [EthernetTransport] [id=0,local=dev://neu-eth0,remote=ether://[01:00:5e:00:17:aa]] Creating transport 1456146897.983192 INFO: [FaceTable] Added face id=259 remote=ether://[01:00:5e:00:17:aa] local=dev://neu-eth0 1456146897.983264 INFO: [EthernetTransport] [id=0,local=dev://neu-eth2,remote=ether://[01:00:5e:00:17:aa]] Creating transport 1456146897.995094 INFO: [FaceTable] Added face id=260 remote=ether://[01:00:5e:00:17:aa] local=dev://neu-eth2 1456146897.995166 INFO: [EthernetTransport] [id=0,local=dev://neu-eth1,remote=ether://[01:00:5e:00:17:aa]] Creating transport 1456146898.007089 INFO: [FaceTable] Added face id=261 remote=ether://[01:00:5e:00:17:aa] local=dev://neu-eth1 1456146898.007160 WARNING: [CommandValidator] Wildcard identity is intended for demo purpose only and SHOULD NOT be used in production environment 1456146898.007191 INFO: [CommandValidator] Giving privilege "faces" to identity wildcard 1456146898.007274 INFO: [CommandValidator] Giving privilege "fib" to identity wildcard 1456146898.007321 INFO: [CommandValidator] Giving privilege "strategy-choice" to identity wildcard 1456146898.007462 INFO: [InternalForwarderTransport] [id=0,local=null://,remote=null://] Creating transport 1456146898.007514 INFO: [FaceTable] Added face id=255 remote=null:// local=null:// 1456146898.010224 INFO: [InternalForwarderTransport] [id=0,local=contentstore://,remote=contentstore://] Creating transport 1456146898.010280 INFO: [FaceTable] Added face id=254 remote=contentstore:// local=contentstore:// 1456146898.012151 INFO: [PrivilegeHelper] dropped to effective uid=0 gid=0 1456146898.013472 INFO: [AutoPrefixPropagator] Load auto_prefix_propagate section in rib section 1456146898.013665 INFO: [AutoPrefixPropagator] Load auto_prefix_propagate section in rib section 1456146898.013715 INFO: [RibManager] Listening on: /localhost/nfd/rib 1456146898.017241 INFO: [RibManager] Start monitoring face create/destroy events 1456146898.019405 INFO: [UnixStreamTransport] [id=0,local=unix:///run/nfd.sock,remote=fd://31] Creating transport 1456146898.019482 INFO: [FaceTable] Added face id=262 remote=fd://31 local=unix:///run/nfd.sock 1456146898.025726 INFO: [AutoPrefixPropagator] local registration only for /localhost/nfd/rib ERROR: error while connecting to the forwarder (No such file or directory) Please help in resolving the issue. (* I used ./install ?mrfti to install minindn and there were no errors) Regards, Navdeep Uniyal _______________________________________________ Mini-NDN mailing list Mini-NDN at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn -------------- next part -------------- An HTML attachment was scrubbed... URL: From pdpa at st-andrews.ac.uk Sun Feb 28 16:09:07 2016 From: pdpa at st-andrews.ac.uk (Percy Perez Aruni) Date: Mon, 29 Feb 2016 00:09:07 +0000 Subject: [Mini-NDN] Consumer is not receiving the data (MiniNdn) Message-ID: Hi dear MiniNdn team I am interested in using MiniNdn for an initial basic experiment between three nodes: a consumer , a forwarder and a producer. It is highly possible that I am missing something, but the consumer is not receiving the data from the producer. Could I ask for some advice of how this could be achieved by using MiniNdn? *Some details below:* 1.- Topology: c <-> f <-> p where c = consumer, f = forwarder, p =producer 2.- ExperimentClass: from ndn.experiments.experiment import Experiment class Experiment1(Experiment): def __init__(self,args): Experiment.__init__(self, args) def run(self): if host.name == "p": host.cmd("echo test1 | ndnpoke /ndn/edu/p &") if host.name == "c": print host.cmd("ndnpeek -p /ndn/edu/p") Experiment.register("peek-poke", Experiment1) 3.- Running as root: #./install.sh -i; minindn --experiment=peek-poke --ctime=20 ndn_utils/topologies/three-nodes.conf 4.- "NLSR has successfully converged" Thank you in advance for your time and help Regards Percy -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuoyang at email.arizona.edu Sun Feb 28 20:46:15 2016 From: shuoyang at email.arizona.edu (Shuo Yang) Date: Sun, 28 Feb 2016 21:46:15 -0700 Subject: [Mini-NDN] Consumer is not receiving the data (MiniNdn) In-Reply-To: References: Message-ID: Hi Percy, It seems that you should write the script in this way: 1from ndn.experiments.experiment import Experiment 2 3class Experiment1(Experiment): 4 def __init__(self,args): 5 Experiment.__init__(self, args) 6 def run(self): 7 for host in self.net.hosts: 8 if host.name == "p": 9 host.cmd("echo test1 | ndnpoke /ndn/edu/producer &") 10 11 for host in self.net.hosts: 12 if host.name == "c": 13 print host.cmd("ndnpeek -p /ndn/edu/producer") 14 15Experiment.register("peek-poke", Experiment1) At least yours is working on my side. I'm using Mini-ndn 0.1.1 Best luck! Shuo On Sun, Feb 28, 2016 at 5:09 PM, Percy Perez Aruni wrote: > Hi dear MiniNdn team > > I am interested in using MiniNdn for an initial basic experiment between > three nodes: a consumer , a forwarder and a producer. It is highly > possible that I am missing something, but the consumer is not receiving > the data from the producer. > > Could I ask for some advice of how this could be achieved by using > MiniNdn? > > > > *Some details below:* > > 1.- Topology: c <-> f <-> p > > where c = consumer, f = forwarder, p =producer > > 2.- ExperimentClass: > > from ndn.experiments.experiment import Experiment > > class Experiment1(Experiment): > def __init__(self,args): > Experiment.__init__(self, args) > def run(self): > if host.name == "p": > host.cmd("echo test1 | ndnpoke /ndn/edu/p &") > if host.name == "c": > print host.cmd("ndnpeek -p /ndn/edu/p") > Experiment.register("peek-poke", Experiment1) > > 3.- Running as root: > > #./install.sh -i; minindn --experiment=peek-poke --ctime=20 > ndn_utils/topologies/three-nodes.conf > > 4.- "NLSR has successfully converged" > > > Thank you in advance for your time and help > > Regards > Percy > > _______________________________________________ > Mini-NDN mailing list > Mini-NDN at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Navdeep.Uniyal at neclab.eu Mon Feb 29 05:52:42 2016 From: Navdeep.Uniyal at neclab.eu (Navdeep Uniyal) Date: Mon, 29 Feb 2016 13:52:42 +0000 Subject: [Mini-NDN] NLSR Error Message-ID: <15421E67B274CD4AB5F6AEA46A684C370384D9B1@Hydra.office.hd> Hi everyone, I am using minindn to run my experiments, I am finding few errors in the NLSR log. Due to which packet loss is occurring. Below is the snippet of the error and attached is the log file. Please if someone can help resolving the issue. 20160229054020045 DEBUG: [HelloProtocol] Interest Received for Name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hb 20160229054020045 DEBUG: [HelloProtocol] Neighbor: /ndn/edu/%C1.Router/cs/hb 20160229054020049 DEBUG: [HelloProtocol] Sending out data for name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hb 20160229054020533 DEBUG: [HelloProtocol] Interest Received for Name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hc 20160229054020533 DEBUG: [HelloProtocol] Neighbor: /ndn/edu/%C1.Router/cs/hc 20160229054020535 DEBUG: [HelloProtocol] Sending out data for name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hc 20160229054111562 FATAL: [Main] ERROR: error while receiving data from socket (End of file) 20160229054111562 DEBUG: [Fib] Fib::clean called Regards, Navdeep Uniyal -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: nlsr.log Type: application/octet-stream Size: 924612 bytes Desc: nlsr.log URL: From vslehman at memphis.edu Mon Feb 29 07:47:50 2016 From: vslehman at memphis.edu (Vince Lehman (vslehman)) Date: Mon, 29 Feb 2016 15:47:50 +0000 Subject: [Mini-NDN] NLSR Error In-Reply-To: <15421E67B274CD4AB5F6AEA46A684C370384D9B1@Hydra.office.hd> References: <15421E67B274CD4AB5F6AEA46A684C370384D9B1@Hydra.office.hd> Message-ID: Hi Navdeep, This error is usually caused by the NFD process on the node terminating; NLSR is unable to receive data from NFD?s Unix socket. Can you check or share NFD?s log to see the reason for the process? termination? It could be something wrong with the configuration or if you are using ctl^c to kill a process on the Mini-NDN command-line, this can sometimes kill NFD processes also. -- Vince Lehman On Feb 29, 2016, at 7:52 AM, Navdeep Uniyal > wrote: Hi everyone, I am using minindn to run my experiments, I am finding few errors in the NLSR log. Due to which packet loss is occurring. Below is the snippet of the error and attached is the log file. Please if someone can help resolving the issue. 20160229054020045 DEBUG: [HelloProtocol] Interest Received for Name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hb 20160229054020045 DEBUG: [HelloProtocol] Neighbor: /ndn/edu/%C1.Router/cs/hb 20160229054020049 DEBUG: [HelloProtocol] Sending out data for name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hb 20160229054020533 DEBUG: [HelloProtocol] Interest Received for Name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hc 20160229054020533 DEBUG: [HelloProtocol] Neighbor: /ndn/edu/%C1.Router/cs/hc 20160229054020535 DEBUG: [HelloProtocol] Sending out data for name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hc 20160229054111562 FATAL: [Main] ERROR: error while receiving data from socket (End of file) 20160229054111562 DEBUG: [Fib] Fib::clean called Regards, Navdeep Uniyal _______________________________________________ Mini-NDN mailing list Mini-NDN at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn -------------- next part -------------- An HTML attachment was scrubbed... URL: From vslehman at memphis.edu Mon Feb 29 08:13:06 2016 From: vslehman at memphis.edu (Vince Lehman (vslehman)) Date: Mon, 29 Feb 2016 16:13:06 +0000 Subject: [Mini-NDN] Consumer is not receiving the data (MiniNdn) In-Reply-To: References: Message-ID: <9E9D4A36-B6C2-4D4F-A40C-2F73BCC20981@memphis.edu> Hi Percy, Is the script you included your entire experiment script? If not, could you please attach the full code? Right now the experiment you attached will fail with a Python error due to an undefined variable, host. You can access a specific host using the method that Shuo used: for host in self.net.hosts: if host.name == ?p?: host.cmd("echo test1 | ndnpoke /ndn/edu/producer &?) Or you can access a specific node using the self.net object: self.net['p'].cmd("echo test1 | ndnpoke /ndn/edu/p &") -- Vince Lehman On Feb 28, 2016, at 10:46 PM, Shuo Yang > wrote: Hi Percy, It seems that you should write the script in this way: 1from ndn.experiments.experiment import Experiment 2 3class Experiment1(Experiment): 4 def __init__(self,args): 5 Experiment.__init__(self, args) 6 def run(self): 7 for host in self.net.hosts: 8 if host.name == "p": 9 host.cmd("echo test1 | ndnpoke /ndn/edu/producer &") 10 11 for host in self.net.hosts: 12 if host.name == "c": 13 print host.cmd("ndnpeek -p /ndn/edu/producer") 14 15Experiment.register("peek-poke", Experiment1) At least yours is working on my side. I'm using Mini-ndn 0.1.1 Best luck! Shuo On Sun, Feb 28, 2016 at 5:09 PM, Percy Perez Aruni > wrote: Hi dear MiniNdn team I am interested in using MiniNdn for an initial basic experiment between three nodes: a consumer , a forwarder and a producer. It is highly possible that I am missing something, but the consumer is not receiving the data from the producer. Could I ask for some advice of how this could be achieved by using MiniNdn? Some details below: 1.- Topology: c <-> f <-> p where c = consumer, f = forwarder, p =producer 2.- ExperimentClass: from ndn.experiments.experiment import Experiment class Experiment1(Experiment): def __init__(self,args): Experiment.__init__(self, args) def run(self): if host.name == "p": host.cmd("echo test1 | ndnpoke /ndn/edu/p &") if host.name == "c": print host.cmd("ndnpeek -p /ndn/edu/p") Experiment.register("peek-poke", Experiment1) 3.- Running as root: #./install.sh -i; minindn --experiment=peek-poke --ctime=20 ndn_utils/topologies/three-nodes.conf 4.- "NLSR has successfully converged" Thank you in advance for your time and help Regards Percy _______________________________________________ Mini-NDN mailing list Mini-NDN at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn _______________________________________________ Mini-NDN mailing list Mini-NDN at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn -------------- next part -------------- An HTML attachment was scrubbed... URL: From pdpa at st-andrews.ac.uk Mon Feb 29 16:25:59 2016 From: pdpa at st-andrews.ac.uk (Percy Perez Aruni) Date: Tue, 1 Mar 2016 00:25:59 +0000 Subject: [Mini-NDN] {Disarmed} Re: Consumer is not receiving the data (MiniNdn) In-Reply-To: References: Message-ID: Hi dear Shuo and Vince Thank you both for replying my last email. I just re-installed minindn (./install.sh -mrfti) and the script is working now. Unfortunately I can not explain why this was necessary. Regarding your comments: >>> Is the script you included your entire experiment script? If not, could you please attach the full code? Yes, it is the entire script. If you do not mind, could I ask the following please: 1.- How can I use MiniNdn to collect data traffic for each and between nodes? For example, I would like to collect data traffic for the forwarder, like which face has received the interest or data and when? 2.- To register static routes from a ExperimentClass, could MiniNdn use the host.name instead of IP addresses? for example: self.net['p'].cmd("nfdc register /ndn/edu/store1 tcp:// 1.0.0.3:6363 &") Thank you again for your comments. Regards Percy On 29 February 2016 at 04:46, Shuo Yang wrote: > Hi Percy, > > It seems that you should write the script in this way: > > 1from ndn.experiments.experiment import Experiment > > 2 > > 3class Experiment1(Experiment): > > > > 4 def __init__(self,args): > > > > 5 Experiment.__init__(self, args) > > > > 6 def run(self): > > > > 7 for host in self.net.hosts: > > > > 8 if host.name == "p": > > > > 9 host.cmd("echo test1 | ndnpoke /ndn/edu/producer &") > > > > 10 > > > > 11 for host in self.net.hosts: > > > > 12 if host.name == "c": > > > > 13 print host.cmd("ndnpeek -p /ndn/edu/producer") > > > > 14 > > 15Experiment.register("peek-poke", Experiment1) > > At least yours is working on my side. I'm using Mini-ndn 0.1.1 > > > Best luck! > > Shuo > > On Sun, Feb 28, 2016 at 5:09 PM, Percy Perez Aruni > wrote: > >> Hi dear MiniNdn team >> >> I am interested in using MiniNdn for an initial basic experiment between >> three nodes: a consumer , a forwarder and a producer. It is highly >> possible that I am missing something, but the consumer is not receiving >> the data from the producer. >> >> Could I ask for some advice of how this could be achieved by using >> MiniNdn? >> >> >> >> *Some details below:* >> >> 1.- Topology: c <-> f <-> p >> >> where c = consumer, f = forwarder, p =producer >> >> 2.- ExperimentClass: >> >> from ndn.experiments.experiment import Experiment >> >> class Experiment1(Experiment): >> def __init__(self,args): >> Experiment.__init__(self, args) >> def run(self): >> if host.name == "p": >> host.cmd("echo test1 | ndnpoke /ndn/edu/p &") >> if host.name == "c": >> print host.cmd("ndnpeek -p /ndn/edu/p") >> Experiment.register("peek-poke", Experiment1) >> >> 3.- Running as root: >> >> #./install.sh -i; minindn --experiment=peek-poke --ctime=20 >> ndn_utils/topologies/three-nodes.conf >> >> 4.- "NLSR has successfully converged" >> >> >> Thank you in advance for your time and help >> >> Regards >> Percy >> >> _______________________________________________ >> Mini-NDN mailing list >> Mini-NDN at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: