[aodvv2-discuss] Re: Changes to -10 draft for gateway

  • From: John Dowdell <john.dowdell486@xxxxxxxxx>
  • To: AODVv2 Discuss <aodvv2-discuss@xxxxxxxxxxxxx>
  • Date: Wed, 22 Jul 2015 12:11:05 +0200

Stan

Your point is well made. I believe the thrust of the discussion in the meeting
was that the IAR should not advertise the whole 0.0.0.0 network but advertise
the bits it does serve, and that the method of so doing was not specified just
now.

You could look at this by saying the physical box that attaches the AODVv2
network to the other network consists of two functions; an AODVv2 compliant
router that looks just like all the others and maybe even has a subnet hanging
off it with client devices, and a router that attaches to some other network
that runs a different routing protocol. The interface connecting the two
routers must be configured so that it does not overlap with the address space
of the AODVv2 network.

How does that work for you?

John


On 22 Jul 2015, at 11:08, Justin Dean <bebemaster@xxxxxxxxx> wrote:

I don't think it's an issue as the node would no longer be "within" the
AODVv2 network. A host route injection by whatever mechanism would be a fine
way of letting the IAR know that this node is no longer in the network and
then it could reply as normal.

Justin

On Wed, Jul 22, 2015 at 10:55 AM, Stan Ratliff <ratliffstan@xxxxxxxxx
<mailto:ratliffstan@xxxxxxxxx>> wrote:
John,

I took this off-list & unicasted, because I'm not interested in stirring the
pot. But, I'm concerned about the proposed text;


The IAR MUST respond to RREQ on behalf of all Internet destinations,
i.e., destinations not on the configured 191.0.2.0/24
<http://191.0.2.0/24> subnet. The IAR
MUST be configured so that it does not respond to RREQ for addresses
within the AODVv2 manet (here, 191.0.2.0/24 <http://191.0.2.0/24>).



This means that the IAR can *never* be the neighbor that helps you discover a
route *within* the AODVv2 network - It's like an AODV instance that says "Oh,
you can get to the Internet through me, but to a node in the MANET?!? What?!?
I know NOTHING! I see NOTHING!" ;-) And, what if you get into a mobility
scenario where you have something like:


Bulk of AODVv2 net -------------- IAR ------------ One lone straggler who
turned left when he should've turned right
|
|
|
Internet

In that scenario, none of the "bulk" nodes can find the straggler, and the
straggler can't find anything other than the Internet. Or am I missing
something?

Regards,
Stan


Other related posts: