[support] About the architecture of the MIPv6 daemon [Second Part]

[manish Jamwal]

Hi Angel
Some information related to movement detection when Mobile Host(MH) move in
IPv4/IPv6 Foreign link(FL)

 When MH moves to FL and its egress interface becomes enabled. Mips code in
MH listens for Router Advertisement message, if it does not receives Router
Advertisement message in FL, it gets timeout and send Router Solicitation
message (that will request the router to generate the Router Advertisement
message immediately rather than at there next scheduled time), and MH wait
for some time interval for Router Advertisement message before repeating the
same procedure of sending Router Solicitation message. Meanwhile after send
Router Solicitation message, mip daemon will also check the presence of DHCP
server on the Egress interface link of MH by sending the DHCP discover
message and wait for DHCP offer packet. If the DHCP server is running on the
FL, it gets the ipv4 address from DHCP server. And then mips code maps ipv4
address to ipv6 address, which is further used as CoA. Mips daemon sets the
default route on MH.
Regards
Manish Jamwal

On Mon, Mar 9, 2009 at 9:18 PM, Angel Bartomeu Bonillo <
angelbartomeu at gmail.com> wrote:

> First of all, I need to thank to those who replied to my first question (*Arnaud
> Ebalard,** **manish Jamwal and **Romain KUNTZ)* on the thread at
> http://ml.nautilus6.org/pipermail/support/2009-February/000616.html . I
> had problems with my email and I was forced to register again with this
> other address since I was somehow unable to receive any message from the
> list. Hence I will try to continue the thread I once started from here.
>
> As for being more specific about my needs (Answering to Arnaud Ebalard's
> question), I am building a mobile node for a vehicular network that must be
> able to interact with different routing protocols that will be running in
> the mobile node. The node may have Internet access through different access
> networks i.e. UMTS, GPRS, WIFI an so on. So my intention is to use NEPL to
> manage the multiple CoA once acquired on the different links available.
>
> I have been going around the code of the mip6d (NEMO and MCoA patched) and
> though I have found many interesting things but, could anybody tell me based
> on which events the daemon make the decision of starting a handover and
> destroying the tunnel in one interface to redirect the traffic to another
> tunnel on other interface?.
>
> I have found so far that one of these events is the status of the
> interfaces. As I have seen the code register a listener by netlink to get
> the changes in the interfaces. Does the code take any other thing into
> account, like router advertisement timer out or something like that?
>
>
> Thanks in advance.
>
>
> _______________________________________________
> Support mailing list
> Support at ml.nautilus6.org
> http://ml.nautilus6.org/mailman/listinfo/support
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ml.nautilus6.org/pipermail/support/attachments/20090310/8171109d/attachment-0002.htm