From navdeep.uniyal at neclab.eu Fri Sep 11 05:52:16 2015 From: navdeep.uniyal at neclab.eu (Navdeep Uniyal) Date: Fri, 11 Sep 2015 12:52:16 +0000 Subject: [Mini-NDN] Links not working Message-ID: <12DB5299AAAB1A40B17E72AB76FDA6D801050F78@Hydra.office.hd> Hello All, Pretty strange but suddenly I am facing problems with the link establishment in minindn, below is the snippet. Only few links are getting established while others are not. I tried a few different configurations but everytime I am facing similar problem: *** Adding hosts: ca ga ha hb hc sa sb *** Adding switches: *** Adding links: (5.00Mbit 0ms delay) (5.00Mbit 0ms delay) (ca, ga) (1.00Mbit 0ms delay) (1.00Mbit 0ms delay) (ga, ha) (1.00Mbit 0ms delay) (1.00Mbit 0ms delay) (ga, hb) (1.00Mbit 0ms delay) (1.00Mbit 0ms delay) (ga, hc) (1.00Mbit 0ms delay) (1.00Mbit 0ms delay) (ha, sa) (1.00Mbit 20ms delay) (1.00Mbit 20ms delay) (hb, sa) (1.00Mbit 20ms delay) (1.00Mbit 20ms delay) (hb, sb) (1.00Mbit 0ms delay) (1.00Mbit 0ms delay) (hc, sb) *** Configuring hosts ca ga ha hb hc sa sb Setup time: 14 *** Starting controller c0 *** Starting 0 switches *** Starting CLI: mininet> pingall *** Ping: testing ping reachability ca -> ga X X X X X ga -> ca ha hb hc X X ha -> X X X X sa X hb -> X X X X X sb hc -> X X X X X X sa -> X X X X X X sb -> X X X X X X *** Results: 83% dropped (7/42 received) Below is the configuration file I am using for my experiment: [nodes] ca: _ ga: _ ha: _ hb: _ hc: _ sa: _ sb: _ [links] ca:ga delay=0ms bw=5 ga:ha delay=0ms bw=1 ga:hb delay=0ms bw=1 ga:hc delay=0ms bw=1 ha:sa delay=0ms bw=1 hb:sb delay=20ms bw=1 hb:sa delay=20ms bw=1 hc:sb delay=0ms bw=1 Please if someone can explain and can help me what I might be doing wrong in establishing the connection. Best Regards, Navdeep Uniyal -------------- next part -------------- An HTML attachment was scrubbed... URL: From vslehman at memphis.edu Fri Sep 11 08:16:10 2015 From: vslehman at memphis.edu (Vince Lehman (vslehman)) Date: Fri, 11 Sep 2015 15:16:10 +0000 Subject: [Mini-NDN] Links not working In-Reply-To: <12DB5299AAAB1A40B17E72AB76FDA6D801050F78@Hydra.office.hd> References: <12DB5299AAAB1A40B17E72AB76FDA6D801050F78@Hydra.office.hd> Message-ID: Hi Navdeep, I believe the problem may be with the ?pingall" command and not with link establishment. The pingall command seems to report that certain nodes cannot ping their neighbors, but if you ping manually from the node using the neighbor?s IP address, you should receive a response. Can you try to ping from sa to hb manually using hb's IP address to confirm? -- Vince Lehman On Sep 11, 2015, at 7:52 AM, Navdeep Uniyal > wrote: Hello All, Pretty strange but suddenly I am facing problems with the link establishment in minindn, below is the snippet. Only few links are getting established while others are not. I tried a few different configurations but everytime I am facing similar problem: *** Adding hosts: ca ga ha hb hc sa sb *** Adding switches: *** Adding links: (5.00Mbit 0ms delay) (5.00Mbit 0ms delay) (ca, ga) (1.00Mbit 0ms delay) (1.00Mbit 0ms delay) (ga, ha) (1.00Mbit 0ms delay) (1.00Mbit 0ms delay) (ga, hb) (1.00Mbit 0ms delay) (1.00Mbit 0ms delay) (ga, hc) (1.00Mbit 0ms delay) (1.00Mbit 0ms delay) (ha, sa) (1.00Mbit 20ms delay) (1.00Mbit 20ms delay) (hb, sa) (1.00Mbit 20ms delay) (1.00Mbit 20ms delay) (hb, sb) (1.00Mbit 0ms delay) (1.00Mbit 0ms delay) (hc, sb) *** Configuring hosts ca ga ha hb hc sa sb Setup time: 14 *** Starting controller c0 *** Starting 0 switches *** Starting CLI: mininet> pingall *** Ping: testing ping reachability ca -> ga X X X X X ga -> ca ha hb hc X X ha -> X X X X sa X hb -> X X X X X sb hc -> X X X X X X sa -> X X X X X X sb -> X X X X X X *** Results: 83% dropped (7/42 received) Below is the configuration file I am using for my experiment: [nodes] ca: _ ga: _ ha: _ hb: _ hc: _ sa: _ sb: _ [links] ca:ga delay=0ms bw=5 ga:ha delay=0ms bw=1 ga:hb delay=0ms bw=1 ga:hc delay=0ms bw=1 ha:sa delay=0ms bw=1 hb:sb delay=20ms bw=1 hb:sa delay=20ms bw=1 hc:sb delay=0ms bw=1 Please if someone can explain and can help me what I might be doing wrong in establishing the connection. Best 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 navdeep.uniyal at neclab.eu Wed Sep 16 02:36:47 2015 From: navdeep.uniyal at neclab.eu (Navdeep Uniyal) Date: Wed, 16 Sep 2015 09:36:47 +0000 Subject: [Mini-NDN] Issue with Minindn code Message-ID: <12DB5299AAAB1A40B17E72AB76FDA6D801053037@Hydra.office.hd> Hello all, I found a bug in the minindn code while creating the topology for my experimentation. The issue is while setting up the link bandwidth in float value (for example I want to set 200kbps). The parsing of topology is getting error out and the topology is not getting set. On analyzing the issue, I found a small bug in the "conf_parser.py" file, line 118 of the code : if key in ['bw','jitter','max_queue_size']: value = int(value) instead of' 'int' it should be float as per my analysis. As on changing the type I found it working fine for me and the link bandwidth is getting set properly. if key in ['bw','jitter','max_queue_size']: value = float(value) I haven't tested the values for jitter, max_queue_size, It might cause issue with those, in that case separating the case for 'bw' could be considered. Please fix the changes, if you find it a valid bug. Best Regards, Navdeep Uniyal -------------- next part -------------- An HTML attachment was scrubbed... URL: