[Nfd-dev] [Operators] Spurious traffic to CSU/BYU hubs?

[Dehart, John]

All:

I think this was due to a misconfiguration of nfd-autoreg.
When the BYU node was added it did not get added to the nfd-autoreg Blacklist for REMAP.
So, REMAP was sending ndnrtc Interests to BYU as if BYU was a local host.
I’ve corrected the config, restarted nfd and Jeff will retry his setup.

John

On Mar 29, 2015, at 3:56 PM, Lan Wang (lanwang) <lanwang at memphis.edu<mailto:lanwang at memphis.edu>> wrote:

Jeff,

Can you give a little more information?

- name prefix used by the ndncon producer?

- strategy used by the name prefix?

- was the spurious traffic present before the test?


Lan

On Mar 29, 2015, at 11:09 AM, "Burke, Jeff" <jburke at remap.ucla.edu<mailto:jburke at remap.ucla.edu>> wrote:


Hi,

On ndnmap I am consistently seeing spurious traffic to the CSU hub. Can
someone explain why?

Steps to reproduce:

- Start ndncon publisher with route via REMAP node (ndnradio example
emailed about earlier).
- Start ndncon consumer with route via CAIDA or UA (haven't tried others
though using CSU as the consumer hub works)

Results on ndnmap:

- See ~500-1000 kb/sec traffic bidirectional from consumer to publisher.
(e.g., CAIDA-UCLA-REMAP or REMAP-UA)
- But, also see 100-250 kb/sec traffic  from REMAP-CSU, REMAP-BYU-CSU.
(note that traffic is asymmetric)

Screenshot attached for consumer via CAIDA hub case.

Thanks,
Jeff

<Screenshot 2015-03-29 09.07.12.png>_______________________________________________
Operators mailing list
Operators at lists.named-data.net<mailto:Operators at lists.named-data.net>
http://lists.named-data.net/mailman/listinfo/operators

_______________________________________________
Operators mailing list
Operators at lists.named-data.net<mailto:Operators at lists.named-data.net>
http://lists.named-data.net/mailman/listinfo/operators

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20150329/a94da8d9/attachment.html>