[Nfd-dev] Many Multicast Ethernet Groups per NIC

NAVES Raphael raphael.naves at thalesgroup.com
Thu Jan 7 00:30:58 PST 2021


Dear Davide,

The idea of having several multicast groups is that even if my nodes are always physically connected in practice (= on the same switch), sometimes I want my Interests to be received/processed by only a subset of the nodes in that segment. It may be used for instance to emulate that a node becomes disconnected of the network even if it is still physically connected.

The creation of multiple VLANs is a very good idea, and it is exactly the kind of isolation that I was looking for. Thank you for your help.

Raphaël

-----Message d'origine-----
De : Davide Pesavento <davidepesa at gmail.com> 
Envoyé : jeudi 7 janvier 2021 00:10
À : NAVES Raphael <raphael.naves at thalesgroup.com>
Cc : nfd-dev at lists.cs.ucla.edu
Objet : Re: [Nfd-dev] Many Multicast Ethernet Groups per NIC

Hi Raphaël,

Could you tell us a bit more about your use case? Why do you want to use several Ethernet multicast groups?

If you're trying to achieve some sort of isolation at layer 2, I think you're better off using VLANs. You can create multiple software VLAN interfaces on top of your Ethernet device with something like:

    sudo ip link add link eth0 name foo42 type vlan id 42
    sudo ip link add link eth0 name foo43 type vlan id 43
    etc...

and NFD should create one multicast face for each of these VLAN interfaces. Then you don't need different multicast groups.

Best,
Davide

On Wed, Jan 6, 2021 at 8:46 AM NAVES Raphael via Nfd-dev <nfd-dev at lists.cs.ucla.edu> wrote:
>
> Dear all,
>
>
>
> I am setting up a NDN network over Ethernet Faces. I have created both unicast and multicast Ethernet Faces to ensure the connectivity between my NDN nodes.
>
>
>
> However, I am wondering if it is possible to create several multicast groups (= multicast Ethernet Faces) per NIC, using the original configuration file or the nfdc tool? At this time, I am only able to create one multicast Ethernet Face per Ethernet port by using the associated field in the nfd.conf file (à “mcast” set to “yes” in the Ethernet section).
>
>
>
> Thanks in advance
>
>
>
> Best
>
>
>
> Raphaël
>
>
>
>
>
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev


More information about the Nfd-dev mailing list