[Ns-bugs] [Bug 407] OLSR is missing HNA support

[code@nsnam.ece.gatech.edu]

http://www.nsnam.org/bugzilla/show_bug.cgi?id=407





--- Comment #16 from suresh.lalith at gmail.com  2010-01-28 07:04:43 EDT ---
(In reply to comment #15)
> > So the idea is to generate HNA messages for all routing table entries which
> > have a non-OLSR interface as the interface field?
> > 
> > For example, take the following scenario:
> > 
> >   172.16.1.0/24   172.16.2.0/24   172.16.3.0/24
> > A<------------->B<------------->C<------------>D
> >      OLSR            non-OLSR        non-OLSR
> > 
> > 
> > So B should announce 172.16.2.0/24 and 172.16.3.0/24 automatically right?
> > 
> 
> I don't know how B knows about 172.16.3.0/24 automatically.  I would assume
> that in this case, B would automatically associate 172.16.2.0/24 and the user
> would have to specify 172.16.3.0/24 as an additional associated network to B. 
> I would probably not make it a programming error for the user to also manually
> specify 172.16.2.0/24 despite it being autogenerated.

I was wondering if B eventually learns about 172.16.3.0/24, should it announce
172.16.3.0/24 automatically?

But I think it's safer if we ensure that the user himself specify all the
associations (no auto-generation of HNA messages) using a method like
AddAssociation(). If required, we could later add another method that would
autmoatically add associations using AddAssociation() itself? Let me know so I
can update the patch. :)

And thanks for your time!

-- 
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.