[Olsr-dev] OLSRv2 and SMF agent integration
Oytun Yapar
(spam-protected)
Fri Sep 24 14:42:59 CEST 2021
As I understand, since I have one MTR, there will be one domain then.
Henning Rogge <(spam-protected)>, 24 Eyl 2021 Cum, 13:28 tarihinde şunu
yazdı:
> Domains was my name to differentiate the different Topologies of
> Multi-Topology-Routing... the problem is that OLSRv2 already uses the
> name "Topology".
>
> So unless you plan to use MTR, you only have a single NHDP "Domain"
>
> Henning
>
> On Fri, Sep 24, 2021 at 12:27 PM Oytun Yapar <(spam-protected)> wrote:
> >
> > Hi Henning,
> >
> > Also I am trying to understand the NHDP domain concept. Does each
> interface (each network) mean a different domain?
> >
> > Regards.
> > Oytun Yapar
> >
> > Oytun Yapar <(spam-protected)>, 23 Eyl 2021 Per, 16:05 tarihinde
> şunu yazdı:
> >>
> >> Hi Henning,
> >>
> >> I will check it. Thank you.
> >>
> >> Regards.
> >> Oytun Yapar
> >>
> >> Henning Rogge <(spam-protected)>, 23 Eyl 2021 Per, 15:17 tarihinde
> şunu yazdı:
> >>>
> >>> Hi,
> >>>
> >>> nhdp_link struct contains a field called "remote_mac". I think that is
> >>> what you are looking for.
> >>>
> >>> Henning Rogge
> >>>
> >>> On Thu, Sep 23, 2021 at 1:40 PM Oytun Yapar <(spam-protected)>
> wrote:
> >>> >
> >>> > Hello,
> >>> >
> >>> > I am trying to integrate the Simple Multicast Forwarding (SMF)
> implementation of NRL to OONF/OLSRv2. This integration requires, sharing of
> MAC addresses of the neighbours and MAC addresses of relayers to SMF. As I
> checked from the source code, I could find the neighbor MAC information
> from NHDP part of the code. I am not sure about the MAC information of the
> relayers. Do you have any suggestions?
> >>> >
> >>> > Regards.
> >>> > Oytun Yapar
> >>> > --
> >>> > Olsr-dev mailing list
> >>> > (spam-protected)
> >>> > https://lists.olsr.org/mailman/listinfo/olsr-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20210924/9fdbb71b/attachment.htm>
More information about the Olsr-dev
mailing list