[support] Destination unreachable from HA on BU???

[Mattias Blomqvist]

Hi,

On Thu, Mar 26, 2009 at 4:41 PM, Arnaud Ebalard <arno at natisbad.org> wrote:
> Hi,
>
> Mattias Blomqvist <mattias.blomqvist at gmail.com> writes:
>> .....
>
> You could recompile it with an higher value if you really need
> that.

Ok.

>
>> 2)
>> If mip6d is running when the tunnel interface comes up or is started
>> before the tunnel has received a CoA by stateless autoconfig it will
>> use the same address for HoA and CoA.
>
> What do you mean by "use the same address for HoA and CoA"? Can you
> clarify?
>
>> Since it is configured to use a tunnel interface (with tunnel set to
>> enabled) it is always in a foreign net.
>> Should it really use the same address for HoA and CoA when it is in a
>> foreign net?
>> The problem is that even if a RA is received within seconds after the
>> tunnel interface is brought up, mip6d seems to ignore it and continues
>> to use the same address for HoA and CoA.
>> Any ideas?
>
> I may be missing your point but did you specified different interfaces
> with the lower preference value (i.e. higher priority) given to another
> interface like the tunnel one. In the case below, eth0 will be preferred
> over any tunnel interface because those have higher pref values:

I have only one interface defined and it is defined as a tunnel
interface. So no preference values.
The output from mip6d is (I know the time on the MN isn't set so the
timestamps have the wrong date and time):
Fri Jan 11 04:18:37 mn_move: in foreign net
...
Fri Jan 11 04:18:37 mh_send: sending MH type 5
from xxxx:xxxx:0:1300:0:0:0:1
to xxxx:xxxx:0:0:0:0:0:1
Fri Jan 11 04:18:37 mh_send: local CoA xxxx:xxxx:0:1300:0:0:0:1
Fri Jan 11 04:18:37 bul_update_timer: Updating timer
== BUL_ENTRY ==
Home address    xxxx:xxxx:0:1300:0:0:0:1
Care-of address xxxx:xxxx:0:1300:0:0:0:1
CN address      xxxx:xxxx:0:0:0:0:0:1
 lifetime = 262140,  delay = 1000
 flags: IP6_MH_BU_HOME IP6_MH_BU_ACK
...
etc.
xxxx:xxxx is the same for every address above.
This BU will obviously not work. The real problem is that it continues
to use the same address for CoA and HoA even after a RA resulting in
autoconf of a correct CoA has been received. The only way to correct
this problem is to restart mip6d after the tunnel interface have
received a RA so it has a useable CoA.

After restart:
Fri Jan 11 04:32:21 mn_move: in foreign net
...
Fri Jan 11 04:32:21 mh_send: sending MH type 5
from xxxx:xxxx:0:1300:0:0:0:1
to xxxx:xxxx:0:0:0:0:0:1
Fri Jan 11 04:32:21 mh_send: local CoA yyyy:yyyy:0:0:0:0:0:13
Fri Jan 11 04:32:21 bul_update_timer: Updating timer
== BUL_ENTRY ==
Home address    xxxx:xxxx:0:1300:0:0:0:1
Care-of address yyyy:yyyy:0:0:0:0:0:13
CN address      xxxx:xxxx:0:0:0:0:0:1
 lifetime = 262140,  delay = 1500
 flags: IP6_MH_BU_HOME IP6_MH_BU_ACK



BR,
Mattias