|
Hi, all I am now tyring to make a mipv6 testbed using mipl 2.0.1.
The topology is as the following : http://myurl.com.tw/cj0a PAR's addresses are 2001::1 and 2005::2 NAR's addresses are 2000::1 and 2005::1 MN's address is 2001::211:d8ff:fe39:798d HA's address is 2001::290:ccff:fe0e:268a I have some question for MIPL.
There are three main problems.
First, after MN changed its subnet, we use it to ping other device like HA , NAR and PAR. We found whether it executed mip6d will not will affect the result, and we cannot assure it is normal. Second, when the MN handover from Home subnet to Visited subnet, it cannot
send the Bing updates to HA correctly although the whole network is OK.
Third, when the MN back to Home subnet, HA didn't answer DAD probe!
I am unable to confirm whether there is dependence in these questions. We tested our network topology with these scenarios, and the results are as
followings:
1. We don’t execute mip6d on MN.
a) when MN changed its subnet, it pinged PAR and NAR : ##################################################################### PING 2001::1(2001::1) 56 data bytes From 2001::211:d8ff:fe39:798d icmp_seq=0 Destination unreachable: Address unreachable From 2001::211:d8ff:fe39:798d icmp_seq=1 Destination unreachable: Address unreachable ##################################################################### -> Result :With the message above, we found that MN cannot detect PAR. #####################################################################
PING 2000::1(2000::1) 56 data bytes 64 bytes from 2000::1: icmp_seq=10 ttl=255 time=5.33 ms ##################################################################### -> Result : MN cannot detect PAR but NAR after handoff.
We caught some packet by ethereal and found that MN pinged PAR with the HoA (2001::211:d8ff:fe39:798d). while MN pinged NAR with CoA (2000::211:d8ff:fe39:798d). This difference results that why MN can pinged NAR but not PAR. b) When MN changed its subnet, whether HA executes mip6d or not, HA
pinged MN (2000::211d8ff:fe39:798d). We got the message shows that : Destination
unreachable, Address Unreachable.
2. Both HA and MN execute mip6d
a) after MN change its subnet, it pinged other device: ##################################################################### [EMAIL PROTECTED] ~]# ping6 2000::1 (NAR) connect: Operation not permitted [EMAIL PROTECTED] ~]# ping6 2001::1 (PAR) connect: Operation not permitted [EMAIL PROTECTED] ~]# ping6 2001::290:ccff:fe0e:268a (HA) connect: Operation not permitted ##################################################################### -> Result : We found that under this circumstances , MN cannot execute ping6. b) After MN change its subnet, HA pinged MN
(2001::211:d8ff:fe39:798d ):
On HA , it still cannot detect MN, the message shows : Destination unreachable, Address Unreachable. ��-> result : MN cannot send BU successfully when both HA and MN execute mip6d. c) After MN change its subnet, HA pinged MN
(2000::211:d8ff:fe39:798d ):
HA pinged MN successfully. -> Result : compare with 1.(b), whether successful ping will depends on whether MN executing mip6d. 3. Both HA and MN execute mip6d , after MN changedits subnet , MN turned off mip6d: a) MN pinged HA : ##################################################################### [EMAIL PROTECTED] ~]# ping6 2001::290:ccff:fe0e:268a PING 2001::290:ccff:fe0e:268a(2001::290:ccff:fe0e:268a) 56 data bytes 64 bytes from 2001::290:ccff:fe0e:268a: icmp_seq=0 ttl=62 time=2.52 ms 64 bytes from 2001::290:ccff:fe0e:268a: icmp_seq=1 ttl=62 time=2.52 ms ##################################################################### -> Result : based on the test above, whether successful ping will
depends on whether MN executing mip6d. is this normal ?
b) HA pinged MN (2000::211:d8ff:fe39:798d ) :
HA detected MN. About the second quesion, I will offer relevant information as much as possible. I applied the 2.0.1 patches on a 2.6.15.11 kernel and the patch applied without any warnings I also enabled the following options in the kernel CONFIG_EXPERIMENTAL=y
CONFIG_SYSVIPC=y CONFIG_PROC_FS=y CONFIG_NET=y CONFIG_INET=y CONFIG_IPV6=y CONFIG_IPV6_MIP6=y CONFIG_XFRM=y CONFIG_XFRM_USER=y CONFIG_XFRM_ENHANCEMENT=y CONFIG_IPV6_TUNNEL=y CONFIG_IPV6_ADVANCED_ROUTER=y CONFIG_IPV6_MULTIPLE_TABLES=y CONFIG_IPV6_SUBTREES=y CONFIG_ARPD=y CONFIG_INET6_ESP=y CONFIG_NET_KEY=y CONFIG_NET_KEY_MIGRATE=y ##These options are the same INSTALL_kernel file. CONFIG_EXT3_FS=y CONFIG_8139TOO=y CONFIG_VIA_RHINE=y CONFIG_USB_EHCI_HCD=y ##These options are additional. Our MN's address is 2001::211:d8ff:fe39:798d
Our HA's address is 2001::290:ccff:fe0e:268a - mip6d.conf for MN
NodeConfig MN;
DebugLevel 10; MnDiscardHaParamProb enabled; Interface "eth0"; MnRouterProbes 1; MnHomeLink "eth0" { HomeAgentAddress 2001::290:ccff:fe0e:268a; HomeAddress 2001::211:d8ff:fe39:798d/64; } ## ## IPsec configuration ## UseMnHaIPsec enabled; IPsecPolicySet { HomeAgentAddress 2001::290:ccff:fe0e:268a; HomeAddress 2001::211:d8ff:fe39:798d/64; IPsecPolicy HomeRegBinding
UseESP;
IPsecPolicy MobPfxDisc UseESP; IPsecPolicy TunnelMh UseESP; } - mip6d.conf for HA
NodeConfig HA;
DebugLevel 10; Interface "eth0"; ## ## IPsec configuration ## UseMnHaIPsec enabled; KeyMngMobCapability disabled; IPsecPolicySet { HomeAgentAddress 2001::290:ccff:fe0e:268a; HomeAddress 2001::211:d8ff:fe39:798d/64; IPsecPolicy HomeRegBinding
UseESP;
IPsecPolicy MobPfxDisc UseESP; IPsecPolicy TunnelMh UseESP; } Because we use two routers(6wind) as R and AR, we didn't setup
radvd.conf.
Results: When connected on Visited subnet, MN builds its global address successfully. We use ethereal to found that MN does not send any BU to HA. See the following logs:
[EMAIL PROTECTED] ~]# mip6d
mip6d[30577]: MIPL Mobile IPv6 for Linux v2.0.1 started (Mobile Node) main: MIPL Mobile IPv6 for Linux started in debug mode, not detaching from terminal conf_show: config_file = /usr/local/etc/mip6d.conf conf_show: mip6_entity = 1 conf_show: debug_level = 10 conf_show: PolicyModulePath = [internal] conf_show: DefaultBindingAclPolicy = 0 conf_show: NonVolatileBindingCache = disabled conf_show: KeyMngMobCapability = disabled conf_show: UseMnHaIPsec = enabled conf_show: MnMaxHaBindingLife = 262140 conf_show: MnMaxCnBindingLife = 420 conf_show: MnRouterProbes = 1 conf_show: MnRouterProbeTimeout = 0.000000 conf_show: InitialBindackTimeoutFirstReg = 1.500000 conf_show: InitialBindackTimeoutReReg = 1.000000 conf_show: UseCnBuAck = disabled conf_show: DoRouteOptimizationMN = enabled conf_show: MnUseAllInterfaces = disabled conf_show: MnDiscardHaParamProb = enabled conf_show: SendMobPfxSols = enabled conf_show: SendMobPfxAdvs = enabled conf_show: SendUnsolMobPfxAdvs = enabled conf_show: MaxMobPfxAdvInterval = 86400 conf_show: MinMobPfxAdvInterval = 600 conf_show: HaMaxBindingLife = 262140 conf_show: DoRouteOptimizationCN = enabled xfrm_cn_init: Adding policies and states for CN xfrm_mn_init: Adding policies and states for MN conf_home_addr_info: HoA address 2001:0:0:0:211:d8ff:fe39:798d conf_home_addr_info: HA address 2001:0:0:0:290:ccff:fe0e:268a __tunnel_add: created tunnel ip6tnl1 (8) from 2001:0:0:0:211:d8ff:fe39:798d to 2001:0:0:0:290:ccff:fe0e:268a user count 1 conf_home_addr_info: Home address 2001:0:0:0:211:d8ff:fe39:798d flag_hoa: set HoA 2001:0:0:0:211:d8ff:fe39:798d/128 iif 8 flags 10 preferred_time 4294967295 valid_time 4294967295 conf_home_addr_info: Added new home_addr_info successfully __md_discover_router: discover link on iface eth0 (2) md_change_default_router: add new router fe80:0:0:0:209:c0ff:fe30:4036 on interface eth0 (2) mn_addr_do_dad: DAD succeeded! mn_addr_do_dad: DAD succeeded! mn_move: 1535 mn_move: in home net mv_hoa: move HoA 2001:0:0:0:211:d8ff:fe39:798d/64 from iface 8 to 2 mn_send_home_bu: 686 mn_get_home_lifetime: CoA lifetime 2591998 s, HoA lifetime 2591981 s, BU lifetime 262140 s mn_ro_pol_add: Adding default RO triggering policies for all Correspondent Nodesprocess_first_home_bu: New bule for HA bul_add: Adding bule == BUL_ENTRY == Home address 2001:0:0:0:211:d8ff:fe39:798d Care-of address 2000:0:0:0:211:d8ff:fe39:798d CN address 2001:0:0:0:290:ccff:fe0e:268a lifetime = 262140, delay = 1500 flags: IP6_MH_BU_HOME IP6_MH_BU_ACK IP6_MH_BU_LLOCAL mn_send_home_bu: New bule for HA <----------------- about BU mh_send: sending MH type 5 from 2001:0:0:0:211:d8ff:fe39:798d to 2001:0:0:0:290:ccff:fe0e:268a mh_send: local CoA 2000:0:0:0:211:d8ff:fe39:798d mh_send: sendmsg: Resource temporarily unavailable mn_send_bu_msg: mh_send failed ret: -1 <----------------- about BU bul_update_timer: Updating timer == BUL_ENTRY == Home address 2001:0:0:0:211:d8ff:fe39:798d Care-of address 2000:0:0:0:211:d8ff:fe39:798d CN address 2001:0:0:0:290:ccff:fe0e:268a lifetime = 262140, delay = 1500 flags: IP6_MH_BU_HOME IP6_MH_BU_ACK IP6_MH_BU_LLOCAL dump_migrate: ifindex 8 dump_migrate: hoa 2001:0:0:0:211:d8ff:fe39:798d dump_migrate: ha 2001:0:0:0:290:ccff:fe0e:268a dump_migrate: ipsec ESP dump_migrate: ifindex 8 dump_migrate: hoa 2001:0:0:0:211:d8ff:fe39:798d dump_migrate: ha 2001:0:0:0:290:ccff:fe0e:268a dump_migrate: ocoa 2001:0:0:0:211:d8ff:fe39:798d dump_migrate: ncoa 2000:0:0:0:211:d8ff:fe39:798d dump_migrate: ipsec ESP tunnel_mod: modifying tunnel 8 end points with from 2000:0:0:0:211:d8ff:fe39:798d to 2001:0:0:0:290:ccff:fe0e:268a __tunnel_mod: modified tunnel iface ip6tnl1 (8)from 2000:0:0:0:211:d8ff:fe39:798d to 2001:0:0:0:290:ccff:fe0e:268a bu_resend: Bul resend [0x8075e98] type 0 mn_get_home_lifetime: CoA lifetime 2591996 s, HoA lifetime 2591980 s, BU lifetime 262140 s mh_send: sending MH type 5 from 2001:0:0:0:211:d8ff:fe39:798d to 2001:0:0:0:290:ccff:fe0e:268a mh_send: local CoA 2000:0:0:0:211:d8ff:fe39:798d mh_send: sendmsg: Resource temporarily unavailable mn_send_bu_msg: mh_send failed ret: -1 bul_update_timer: Updating timer == BUL_ENTRY == .............. and MN shows the same message on monitor repeatedly.
We once suspected the question was about linux distribution, but, we had ever tested on Fedora and Debian, then the result was the same. We once suspected the question was about mip6d.conf, but, we didn't know how to modification it, because we configured the following test bed according to HowTo. About the third question.... MN can move to foreign network without any problems, but after backing to home network, the error message "mn_addr_do_dad: HA didn't answer DAD probe!" appeared. Thanks for your help.
|
_______________________________________________ mipl mailing list [email protected] http://www.mobile-ipv6.org/cgi-bin/mailman/listinfo/mipl
