[hipl-users] Re: Mobilty test

  • From: Miika Komu <miika@xxxxxx>
  • To: hipl-users@xxxxxxxxxxxxx
  • Date: Tue, 28 Aug 2007 17:58:15 +0300 (EEST)

On Mon, 27 Aug 2007, Fco. Javier Melero wrote:

Hi,

so you have "sticky" default routes even without HIP? So when you move your host between different networks, the old routes don't get deleted automatically? Did I understand correctly?

Have you tried tuning the /proc/sys/net/ipv6/* variables?

If e.g. doing /proc/sys/net/ipv6/route/flush or something similar helps during IPv6 handovers, we can surely add it to hipd code. Could you experiment with the proc variable because I don't currently have multiple radvd running here.

It seems like mobile ipv6 is also tuning the proc files:

http://gnist.org/~lars/doc/Mobile-IPv6-HOWTO/Mobile-IPv6-HOWTO.html#MIPv6

Thanks.

Hi Miika,

I'm sorry for taking so long. I've been a couple weeks off, but now I'm back again (damn it!).

You are completely right. The old routes are what makes it fail in all sceneries. I've sent you a file where you can see ip address and routing tables, hipd log and traffic capture. And just to compare I've done the same for mipl. As you could see mipl make addresses and routes management automatically and so there´s no need for manual deletion. Do you think that sort of management would be possible for hipl?

Greetings


Miika Komu escribió:
On Tue, 7 Aug 2007, Fco. Javier Melero wrote:

Hi,

sorry for the late response.

Hi Miika,

There are no IPv4 addresses involved at all. Right now I´m trying with IPv6 only networks. Interfamily handovers would be a really interesting feature but I´m not on it at the moment.

Samu Varjonen or Yaqub Kamran is going to implement interfamily handovers. Some of the code is ready already.

Here there are two files attached: hipd debug log and a traffic capture on the MN side. They had been taken while moving from network A to B. The first HIP_UPDATE was triggered automatically as soon as the new ip was available. It had the correct IPs but was sended through the old router, so it fails. A few seconds later I deleted the old ip and that triggered a new successful HIP_UPDATE.

This seems to a routing failure and hipd does not manage routing. Does the route to the old router stick in your system after you move to the new network? Please check this with "ip route -6" or "route -6".


--
=========================================================
Fco. Javier Melero de la Torre

Universidad Carlos III de Madrid
Servicio de Informática y Comunicaciones
Area de Seguridad y Comunicaciones
(https://asyc.uc3m.es)

e-mail: javier@xxxxxxxxxx
phone: (+34) 916.249.980, (+34) 918.561.341
fax:   (+34) 916.249.430
=========================================================



--
Miika Komu                                       http://www.iki.fi/miika/

Other related posts: