Re: NHRP protocol modifications and clarifications

[Bruce Cole <[e-mail]>]

> I think I understand what you don't see now.  I am not saying that:
> "the clients share the same IP address and interface".

Your earlier comment:

> What about the case when you have 2 or more NHCs which are co-resident with 
> their NHS?  You can't figure out for whom the packet was sent in this case 
> without burdening all NHCs to check to their database.

led me to believe you were now referring to sharing of an IP address.
If you are segregating NHRP traffic amongst separate IP addresses, then I
don't understand this question.

> I am saying that in order to demux the traffic, when two or more Next Hop 
> Clients (NHC) are physically co-located in the same box with an NHS then 
> they must have DIFFERENT IP addresses NOT a shared IP address.  How else 
> would you demux the client messages to their appropriate destination?

As I wrote originally:

    By looking at the various fields which
    you need to look at anyways, (NHRP packet type, network layer addresses,
    request ID, etc.) one can already determine what to do with the packet.


> There are a number of error conditions for which you just cannot test 
> without a demux mechanism.  If you get an error message, how do you intuit 
> for whom it was sent?...

This also was answered.