Hi All,
A further question concerning the movement detection:
Our MIPv6 test system acts as HA and tests the MIPL 2.0 MN.
Our HA test system implements the "eager binding", that is
Step1) It first sends a couple of MipRtAdv with prefixA (home network),
Step2) then it sends a couple of RtAdv with prefixB (visited network)
=> and MIPL 2.0 MN detects movement and starts Binding Update procedure
So far so good!
Now, during this test, our goal is to make MIPL 2.0 MN execute the returning
home procedure.
Step3) So the HA test system sends another couple of RtAdv, again with prefixA
(home network).
That should make the MIPL 2.0 MN start the returning home procedure.
And it does it! But only if the RTAdv does not contain any mip-specific
information(HAFlag,Advertisement Interval, Home Agent Information).
If mip-specific information is sent by our test system, then MIPL 2.0 MN does
not start the returning home procedure.
As Home address and Home agent address are configured in mip6d.conf, MIPL 2.0
MN does not need the mip-specific information of RTAdv.
Question: Is there anything wrong in our RtAdv (pasted here below) or has
anyone had similar experience?
Thanks for your advice, Sebastian
No. Time Source Destination Protocol Info
55 28.805038 fe80::ff:fe00:a1a1 ff02::1 ICMPv6 Router
advertisement
Frame 55 (118 bytes on wire, 118 bytes captured)
Arrival Time: Mar 27, 2006 13:28:43.709922000
Time delta from previous packet: 1.017267000 seconds
Time since reference or first frame: 28.805038000 seconds
Frame Number: 55
Packet Length: 118 bytes
Capture Length: 118 bytes
Protocols in frame: eth:ipv6:icmpv6
Ethernet II, Src: 00:00:00_00:a1:a1 (00:00:00:00:a1:a1), Dst:
IPv6-Neighbor-Discovery_00:00:00:01 (33:33:00:00:00:01)
Destination: IPv6-Neighbor-Discovery_00:00:00:01 (33:33:00:00:00:01)
Source: 00:00:00_00:a1:a1 (00:00:00:00:a1:a1)
Type: IPv6 (0x86dd)
Internet Protocol Version 6
Version: 6
Traffic class: 0x00
Flowlabel: 0x00000
Payload length: 64
Next header: ICMPv6 (0x3a)
Hop limit: 255
Source address: fe80::ff:fe00:a1a1 (fe80::ff:fe00:a1a1)
Destination address: ff02::1 (ff02::1)
Internet Control Message Protocol v6
Type: 134 (Router advertisement)
Code: 0
Checksum: 0x37a5 [correct]
Cur hop limit: 255
Flags: 0x20
0... .... = Not managed
.0.. .... = Not other
..1. .... = Home Agent
...0 0... = Router preference: Medium
Router lifetime: 65535
Reachable time: 0
Retrans time: 0
ICMPv6 options
Type: 3 (Prefix information)
Length: 32 bytes (4)
Prefix length: 64
Flags: 0xe0
1... .... = Onlink
.1.. .... = Auto
..1. .... = Router Address
...0 .... = Not site prefix
Valid lifetime: 0x0000001e
Preferred lifetime: 0x0000000a
Prefix: 2001:660:5503:276a:0:ff:fe00:a1a1
ICMPv6 options
Type: 7 (Advertisement Interval)
Length: 8 bytes (1)
Advertisement Interval: 3000
ICMPv6 options
Type: 8 (Home Agent Information)
Length: 8 bytes (1)
Home Agent Preference: 10
Home Agent Lifetime: 600
0000 33 33 00 00 00 01 00 00 00 00 a1 a1 86 dd 60 00 33............`.
0010 00 00 00 40 3a ff fe 80 00 00 00 00 00 00 00 00 ...@:...........
0020 00 ff fe 00 a1 a1 ff 02 00 00 00 00 00 00 00 00 ................
0030 00 00 00 00 00 01 86 00 37 a5 ff 20 ff ff 00 00 ........7.. ....
0040 00 00 00 00 00 00 03 04 40 e0 00 00 00 1e 00 00 [EMAIL PROTECTED]
0050 00 0a 00 00 00 00 20 01 06 60 55 03 27 6a 00 00 ...... ..`U.'j..
0060 00 ff fe 00 a1 a1 07 01 00 00 00 00 0b b8 08 01 ................
0070 00 00 00 0a 02 58 .....X
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Nuno Sénica
> Sent: 17 February 2006 19:08
> To: Greg Daley
> Cc: [email protected]
> Subject: Re: [mipl] How to make the MN to detect a movement?
>
> Dear Greg
>
> Thanks for your complete answer.
>
> Does anyone knows if version 2 follows the same procedure?
> If so, is there a way to force Eager Bindings within MIPL 2.0 ?
>
> Thanks
>
>
> ----- Original Message -----
> From: "Greg Daley" <[EMAIL PROTECTED]>
> To: "Nuno Sénica" <[EMAIL PROTECTED]>
> Cc: <[email protected]>
> Sent: Friday, February 17, 2006 2:38 AM
> Subject: Re: [mipl] How to make the MN to detect a movement?
>
>
> Hi Nuno and Sebastian,
>
> Things may be different in MIPL2, but here's how I
> remember things from MIPL1. Please speak up if I'm wrong,
> or out of date.
>
> In accordance with RFC3775, the MIPL implementation tracks
> the time since the advertisement of an RA, and compares it
> to any advertised lifetime in the RA.
>
> If that interval has passed, the MN removes the router's
> configuration tests for received RAs which meet this requirement.
>
> If there are no received RAs at the time, the next RA will
> create avalid entry, and the prefix information options
> will be used by ND to create new addresses (which will be used as
> Care-of-addresses).
>
> Movement has been detected.
>
> Please also note that in most environments, there will be no
> accelerated MIPv6 RA interval (in fact MIPL1 didn't handle
> movement detection so well when the RA rate was 20/second),
> and most routers do not advertise the Advertisement Interval.
> For RFC2461 rates, the best duration for handover detection
> is 4 seconds after the last RA reception on the old link...
>
> Routers not advertising these options cause even more problems,
> but I think that ND times them out after a while (I think perhaps
> MIPL1 also had a built in timer indicating that if no Adv Interval
> option was on the RA, after 6 seconds if I remember rightly).
>
> Please note that an alternative mechanism existed in MIPL1.X
> which allowed "eager bindings". That is, reception of an RA
> with different prefixes indicated a change immediately.
> Please also note that while this gives good performance, there
> are valid configurations in RFC2461 which can cause problems with
> such systems (for example arriving on links with two differently
> configured routers). Several procedures are under (slow?) development
> in the DNA working group.
>
> This is all of course a simplification of the procedure.
>
> I hope it helps either of you
>
> Greg.
>
> Nuno Sénica wrote:
> > Hi
> >
> > The question you made is really important and there's
> another I'd like
> > to add ..
> >
> > When the MN receives a single Visited Prefix RA does MIPL detect any
> > movement or it just waits for the Home Prefix Router to
> expire and then
> > noticing that he has a new router added by the new RA
> (Visited Prefix)
> > it detects the movement ?
> >
> > If someone could explain the complete chain for a movement detection
> > would be perfect.
> >
> > Thanks
> > Nuno
> >
> > ----- Original Message ----- From: "Sebastian Mueller"
> > <[EMAIL PROTECTED]>
> > To: <[email protected]>
> > Sent: Thursday, February 16, 2006 12:45 PM
> > Subject: [mipl] How to make the MN to detect a movement?
> >
> >
> > Hi All,
> >
> > Situation: Testing a MN
> > Question: How to make the MN to detect a movement?
> > - Send RouterAdvertisment(HomePrefix) with Advertisement
> Interval option
> > to MN
> > - Stop sending RouterAdvertisment(HomePrefix) to MN
> > - Send RouterAdvertisment(VisitedPrefix) with Advertisement Interval
> > option to MN
> > - Continue to send RouterAdvertisment(VisitedPrefix) to MN
> > - MN starts DAD
> >
> > Is this enough to make the MN to detect a movement?
> >
> > Thanks for your advice,
> >
> > Sebastian
> >
> > _______________________________________________
> > mipl mailing list
> > [email protected]
> > http://www.mobile-ipv6.org/cgi-bin/mailman/listinfo/mipl
> >
> >
> > _______________________________________________
> > mipl mailing list
> > [email protected]
> > http://www.mobile-ipv6.org/cgi-bin/mailman/listinfo/mipl
>
>
>
>
> _______________________________________________
> mipl mailing list
> [email protected]
> http://www.mobile-ipv6.org/cgi-bin/mailman/listinfo/mipl
>
>
> _______________________________________________
> mipl mailing list
> [email protected]
> http://www.mobile-ipv6.org/cgi-bin/mailman/listinfo/mipl
>
_______________________________________________
mipl mailing list
[email protected]
http://www.mobile-ipv6.org/cgi-bin/mailman/listinfo/mipl
