[support] How to prevent routing header option from being used

[Romain KUNTZ]

Hi Brian,

On 2008/10/10, at 20:25, Millar, Brian H. wrote:
> My Home link was 2201:3:6:0::/56
> My MR link was 2201:3:6:200::/56
> MR Home Address is 2201:3:6::20.
> This normally works fine.
>
> When I added your patches I got a status 132, which usually means I
> messed up the config.
>
> I then changed my HaServedPrefix to 2201:3:6::/48, and then it works.

Status 132 is fired by the HA when the HoA og the MR does not match  
the prefix configured with HaServedPrefix. The manpages tells a bit  
more about the motivation for this option.

Could you give more information about the topology and prefixes you  
use in your testbed? Without those information it's hard to tell what  
could be the reason of this status 132.

> When I try to initiate a connection from the MR now it takes about 10
> seconds before the HA responds to the syn packet. The tcpdump shows my
> packet going back through the tunnel, just a bit delayed.

Could you send the tcpdump trace? Is there anything else that is sent  
between the syn and the reply?

> Would you expect this configuration change be required?
> I've read where people have identified both types of addressing  
> schemes
> for NEMOv6, but haven't found a preference for one over the other  
> until
> now.

What addressing schemes are you talking about? The one when when the  
MR derives its HoA from its MNP?

Regards,
romain