[Nfd-dev] generatation of NDN-like packets with Scapy

[Salvatore Signorello]

Hi Junxiao,

pretty interesting configuration option, this will add yet more value to 
the next daemon release.
In the meantime, could you please point me to the place(source code 
files) where the automatic registration of the NICs is managed? If you 
knew it, this would save me some time and I would really appreciate your 
direction.

Thanks once more,
best,
Salvatore



On 01/08/2016 01:20 PM, Junxiao Shi wrote:
>
> Hi Salvatore
>
> The configuration option you are looking for is “multicast face 
> blacklist”.
>
> This is currently unimplemented; watch #1712 
> <http://redmine.named-data.net/issues/1712> for progress.
>
> Yours, Junxiao
>
>
> *From: *Salvatore Signorello <mailto:salvatore.signorello at uni.lu>
> *Sent: *Thursday, January 7, 2016 05:18
> *To: *Junxiao Shi <mailto:shijunxiao at email.arizona.edu>
> *Cc: *<nfd-dev at lists.cs.ucla.edu> <mailto:nfd-dev at lists.cs.ucla.edu>
> *Subject: *Re: [Nfd-dev] generatation of NDN-like packets with Scapy
>
> ndnpoke is still serving the Interest issued by ndnpeek. I think that 
> the reason is that both daemons register all the existing network 
> interfaces at boot, so a face for veth1 is created and linked for each 
> daemon. When nfd1 forwards to the program thanks to the rule set by 
> nfdc the Interest goes through veth1, so both nfd2 and my program get 
> the Interest packet.
>
> Even if I unregister that face from nfd2 using nfdc (btw, how to 
> manipulate nfd2's FIB using nfdc? the client.conf trick seems to not 
> work with this utility and nfdc always modifies nfd1's FIB), the 
> daemon after a while rescans a list of interfaces it holds and 
> registers it back again. What could I do to stop such behavior? Is 
> there any configuration related to such thing?
>
> Best,
> Salvatore
>

-- 
Salvatore Signorello
PhD student @ SecanLab

Interdisciplinary Centre for Security, Reliability and Trust
SnT, University of Luxembourg
http://wwwen.uni.lu/snt/people/salvatore_signorello

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