[Mini-NDN] Add a Hop count to interest/data packet - unrecognized field 84 cannot be ignored

Aman Maldar amanmaldar at gmail.com
Tue Oct 9 16:49:56 PDT 2018


Hello Ashlesh. Thank you for the information.

I didn't do that early. After doing the clean build, I could start the
topology now. But I am getting the error when I run ndnping application.
Same error.
I will write the steps below that I did.

Short Question - I am able to start the topology now. But I am getting same
error now after running ndnping and ndnpingserver
----------------------------------------------------------------------------

*Long Question-*

*Following are the stpes I did

Edited the latest ndn-cxx package to incorporate HopCountTagField as given
on the link below.
ref -
https://www.lists.cs.ucla.edu/pipermail/ndnsim/2016-December/003254.html

All the directories have the latest code. NFD Version 0.6.2.

Note:
https://github.com/named-data-ndnSIM/ndnSIM/commit/73df9f587e1c16c4f67a0053fe29b68f523ff138

I am not working on apps/ndn-consumer.cpp. I have modified the code in
Forwarder.cpp to print the hopCountTag. I will test this using ndnping
application.

void
Forwarder::onIncomingData(Face& inFace, const Data& data)
{
.
.
  //changes for hop count tag
  auto hopCountTag = data.getTag<lp::HopCountTag>();
  if (hopCountTag != nullptr) {
    hopCount = *hopCountTag;
  }
  NFD_LOG_DEBUG("Hop count: " << hopCount);


*steps continue...

stopped the NFD
> nfd-stop

>cd mini-ndn/ndn-cxx/

sudo ./waf clean
sudo ./waf configure --with-examples (I want to use ndnping application -
Is it correct?)

sudo ./waf build
sudo ./waf install

>cd mini-ndn/NLSR

sudo ./waf clean
sudo ./waf build
sudo ./waf install

>cd mini-ndn/ChronoSync

sudo ./waf clean
sudo ./waf build
sudo ./waf install

>cd mini-ndn/NFD

sudo ./waf clean
sudo ./waf build
sudo ./waf install

Edited
mini-ndn/src/nlsr.py

- self.node.cmd("export
NDN_LOG=nlsr.*={}".format(self.node.nlsrParameters.get("nlsr-log-level",
"DEBUG")))
+ self.node.cmd("export NDN_LOG=*=TRACE")

// start NFD with logging
> sudo nfd &> nfd.log &


//starting the topology (Earlier it was failing with the error)
> sudo minindn           // Topology is successfully started.

mini-ndn> d ndnpingserver /ndn/d-site/d -x 1000000 &> /home/lenovo/ser.txt &
mini-ndn> a ndnping /ndn/d-site/d -c 1 -n 1111
PING /ndn/d-site/d
ERROR: unrecognized field 901 cannot be ignored
mini-ndn> a ndnping /ndn/d-site/d -c 2 -n 44444
 PING /ndn/d-site/d
ERROR: unrecognized field 901 cannot be ignored

------------------------------------------------------------------------------

Please find the logs here. What am I missing?
https://www.dropbox.com/sh/e0oggrf2zrg7o4q/AAD8oWBgqfT_IxISwqNc2jDda?dl=0





On Tue, Oct 9, 2018 at 12:50 PM Ashlesh Gawande (agawande) <
agawande at memphis.edu> wrote:

> Can you try getting all the logs by modifying
>
>
> https://github.com/named-data/mini-ndn/blob/6f7a64fc75065191035141e3a8c33e149bef27f9/ndn/nlsr.py#L56
>
> to:
>
> export NDN_LOG=*=TRACE
>
> to figure out how/where the error happens?
>
>
> Have you already tried a clean build of ChronoSync and NLSR after updating
> ndn-cxx?
>
>
> Ashlesh
> ------------------------------
> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Aman
> Maldar <amanmaldar at gmail.com>
> *Sent:* Tuesday, October 9, 2018 12:53:16 AM
> *To:* mini-ndn at lists.cs.ucla.edu; nfd-dev at lists.cs.ucla.edu; Alex
> Afanasyev
> *Subject:* Re: [Mini-NDN] Add a Hop count to interest/data packet -
> unrecognized field 84 cannot be ignored
>
> Hello. I would really appreciate if someone can comment about these errors
> and the use case I am working on.
>
> Here is an update. I went through few more threads and I now understand
> the field type. I am using it as 901.
> ref -
> https://lo.calho.st/networks/adding-custom-packet-fields-to-packets-in-ndnsim-2-3-without-forking-the-entire-repository/
>
> However I am still getting the same error when I run minindn.
>
> ERROR: unrecognized field 901 cannot be ignored1539063705.210205 FATAL:
> [nlsr.NlsrRunner] ERROR: unrecognized field 901 cannot be ignored
>
> Furthermore, I want to understand if this use case is possible.
> - First forwarder adds the timestamp to the interest packet and the I
> print this timestamp when the packet reaches the producer.
> - Can I achieve this using NDNLP, creating custom field ?
>
> Thanks
>
>
> On Mon, Oct 8, 2018 at 5:40 PM Aman Maldar <amanmaldar at gmail.com> wrote:
>
> Hello All,
>
> I am following the steps mentioned here,
> https://www.lists.cs.ucla.edu/pipermail/ndnsim/2016-December/003254.html
>
> After making the changes, I compiled, build and installed ndn-cxx package
> and then NFD package. It worked well. There are no errors.
> Then I restarted nfd.
> (Meanwhile I had to to "sudo ldconfig" to fix issues)
>
> Question - I am getting following error when I start the default minindn
> topology. This is the field that is added as instructed.
>
> [FULL LOG Pasted below - See the error at the end]
>
> lenovo at lenovo-VirtualBox:~/mini-ndn/NFD$ sudo minindn
> Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
> *** Creating network
> *** Adding controller
> *** Adding hosts:
> a b c d
> *** Adding switches:
>
> *** Adding links:
> (10ms delay) (10ms delay) (a, b) (250000ms delay) (250000ms delay) (a, c)
> (10ms delay) (10ms delay) (b, d)
> *** Configuring hosts
> a b c d
> Setup time: 0
> *** Starting controller
> c0
> *** Starting 0 switches
>
> Starting NFD on nodes
> Starting NLSR on nodes
> NLSR on host a is not running. Printing log file and exiting...
> 1539034267.078456 DEBUG: [nlsr.update.PrefixUpdateProcessor] Setting
> dispatcher to capture Interests for: /localhost/nlsr/prefix-update
> 1539034267.079388 DEBUG: [nlsr.Nlsr] Canonized URI: udp://1.0.0.2 to:
> udp4://1.0.0.2:6363
> 1539034267.079405 DEBUG: [nlsr.Nlsr] Canonized URI: udp://1.0.0.6 to:
> udp4://1.0.0.6:6363
> 1539034267.079407 DEBUG: [nlsr.Nlsr] Initializing Nlsr
> 1539034267.079418 DEBUG: [nlsr.SequencingManager] Seq File Name:
> /tmp/minindn/a/log/nlsrSeqNo.txt
> 1539034267.079825 DEBUG: [nlsr.SequencingManager] ----SequencingManager----
> 1539034267.079838 DEBUG: [nlsr.SequencingManager] Adj LSA seq no: 677
> 1539034267.079844 DEBUG: [nlsr.SequencingManager] Cor LSA Seq no: 0
> 1539034267.079846 DEBUG: [nlsr.SequencingManager] Name LSA Seq no: 654
> 1539034267.079869 DEBUG: [nlsr.SyncLogicHandler] Creating Sync Logic
> object. Sync Prefix: /localhop/ndn/nlsr/sync/%FD%05
> 1539034267.083099 INFO: [nlsr.ConfParameter] Router Name: /%C1.Router/cs/a
> 1539034267.083119 INFO: [nlsr.ConfParameter] Site Name: /a-site
> 1539034267.083122 INFO: [nlsr.ConfParameter] Network: /ndn
> 1539034267.083124 INFO: [nlsr.ConfParameter] Router Prefix:
> /ndn/a-site/%C1.Router/cs/a
> 1539034267.083126 INFO: [nlsr.ConfParameter] ChronoSync sync Prefix:
> /localhop/ndn/nlsr/sync/%FD%05
> 1539034267.083128 INFO: [nlsr.ConfParameter] ChronoSync LSA prefix:
> /localhop/ndn/nlsr/LSA
> 1539034267.083130 INFO: [nlsr.ConfParameter] Hello Interest retry number: 3
> 1539034267.083133 INFO: [nlsr.ConfParameter] Hello Interest resend second:
> 1
> 1539034267.083135 INFO: [nlsr.ConfParameter] Info Interest interval: 60
> 1539034267.083136 INFO: [nlsr.ConfParameter] LSA refresh time: 1800
> 1539034267.083138 INFO: [nlsr.ConfParameter] FIB Entry refresh time: 3600
> 1539034267.083140 INFO: [nlsr.ConfParameter] LSA Interest lifetime: 4
> seconds
> 1539034267.083171 INFO: [nlsr.ConfParameter] Router dead interval: 3600
> 1539034267.083172 INFO: [nlsr.ConfParameter] Max Faces Per Prefix: 3
> 1539034267.083174 INFO: [nlsr.ConfParameter] Hyperbolic Routing: 0
> 1539034267.083177 INFO: [nlsr.ConfParameter] Hyp R: 0.5
> 1539034267.083189 INFO: [nlsr.ConfParameter] Hyp Angle 0: 2.64159
> 1539034267.083192 INFO: [nlsr.ConfParameter] Seq Directory:
> /tmp/minindn/a/log
> 1539034267.083194 INFO: [nlsr.ConfParameter] Adjacency LSA build
> interval:  5
> 1539034267.083198 INFO: [nlsr.ConfParameter] First Hello Interest
> interval: 10
> 1539034267.083199 INFO: [nlsr.ConfParameter] Routing calculation
> interval:  15
> 1539034267.083205 DEBUG: [nlsr.AdjacencyList] -------Adjacency List--------
> 1539034267.083213 DEBUG: [nlsr.Adjacent] Adjacent:
> /ndn/b-site/%C1.Router/cs/b
>  Connecting FaceUri: udp4://1.0.0.2:6363
>  Link cost: 10
>  Status: 0
>  Interest Timed Out: 0
>
> 1539034267.083220 DEBUG: [nlsr.Adjacent] Adjacent:
> /ndn/c-site/%C1.Router/cs/c
>  Connecting FaceUri: udp4://1.0.0.6:6363
>  Link cost: 250000
>  Status: 0
>  Interest Timed Out: 0
>
> 1539034267.083225 DEBUG: [nlsr.Nlsr] Name prefix list: {
> /ndn/a-site/a
> Sources:
>
> }
>
> 1539034267.083230 DEBUG: [nlsr.Nlsr] Initializing Key ...
> Router's Identity /ndn/a-site/%C1.Router/cs/a does not exist. NLSR is
> running without security (Only for testing, should not be used in
> production.) If security is enabled NLSR will not converge.
> 1539034267.102884 WARNING: [nlsr.Nlsr] ERROR: Router's Identity
> /ndn/a-site/%C1.Router/cs/a does not existNLSR is running without security.
> If security is enabled NLSR will not converge.
> 1539034267.105658 DEBUG: [nlsr.Nlsr] Default NLSR identity:
> /ndn/a-site/%C1.Router/cs/a/nlsr
> 1539034267.105675 DEBUG: [nlsr.Nlsr] Setting interest filter for Hello
> interest: /ndn/a-site/%C1.Router/cs/a/nlsr/INFO
> 1539034267.106771 DEBUG: [nlsr.Nlsr] Setting interest filter for
> LsaPrefix: /localhop/ndn/nlsr/LSA
> 1539034267.107371 DEBUG: [nlsr.Nlsr] Enabling incoming face id indication
> for local face.
> 1539034267.108174 DEBUG: [nlsr.SequencingManager] ----SequencingManager----
> 1539034267.108185 DEBUG: [nlsr.SequencingManager] Adj LSA seq no: 677
> 1539034267.108188 DEBUG: [nlsr.SequencingManager] Cor LSA Seq no: 0
> 1539034267.108190 DEBUG: [nlsr.SequencingManager] Name LSA Seq no: 655
> 1539034267.108282 DEBUG: [nlsr.Lsdb] New Name LSA
> 1539034267.108287 DEBUG: [nlsr.Lsdb] Adding Name Lsa
> 1539034267.108290 DEBUG: [nlsr.Lsa] LSA of type NAME:
> -Origin Router: /ndn/a-site/%C1.Router/cs/a
> -Sequence Number: 655
> -Expiration Point: 1539037867108168863 nanoseconds since Jan 1, 1970
> --Names:
> ---Name 0: /ndn/a-site/a
> name_lsa_end
> 1539034267.111955 DEBUG: [nlsr.HelloProtocol] Scheduling HELLO Interests
> in 10 seconds
> ERROR: unrecognized field 84 cannot be ignored
> 1539034267.113698 FATAL: [nlsr.NlsrRunner] ERROR: unrecognized field 84
> cannot be ignored
> 1539034267.113733 DEBUG: [nlsr.route.Fib] Fib::clean called
>
> *** Stopping 1 controllers
> c0
> *** Stopping 3 links
> ...
> *** Stopping 0 switches
>
> *** Stopping 4 hosts
> a b c d
> *** Done
>
> Thank you for your time and help.
> --
> *Regards,*
> * Mr. Maldar Aman M.*
> *University of Massachusetts, Lowell*
>
>
>
> --
> *Regards,*
> * Mr. Maldar Aman M.*
> *University of Massachusetts, Lowell*
>


-- 
*Regards,*
*Mr. Maldar Aman M.*
*University of Massachusetts, Lowell*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20181009/6410ef00/attachment-0001.html>


More information about the Mini-NDN mailing list