Dear Antoine and Zarrar, Here I get the same issue with Zarrar. Have you got the issue fixed and is that possible pass me the solution as well?
Thanks. Regards, Raymond -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Antoine Boutet Sent: Monday, May 29, 2006 4:13 PM To: zarrar yousaf Cc: [email protected] Subject: [mipl] RE : MN cant ping CN in Visited Network and VT bc commanddoes not work Hello Zarrar, Sorry, I was out friday. > Hello Antoine, > Although i have posted this issue on the MIPL mailing list but i would certainly value your comments as I am > following the same steps and configurations as laid out in (www.ipt.etsi.org/mini_howto.htm). the only thing > different is that i am using site local addresses rather than global addresses as in your mini howto. Ok > I decided not to get tempted into using knoppix because I wanted to learn Linux the hard way :-)....and i did > successfully upgraded all my nodes to kernel version 2.6.15.7 (kernel.org) Ok > Here is the problem I have > I have a functional IPv6 network and the CN and the MN can ping each other when the MN is in the Home Network. > When the MN moves to the foreign network the pinging beween MN and CN stops. (My CN is also located on the > same Foreign Network.). > The CN states "Destination unreachable" and the MN states "Invalid argument". > When I plug the MN back into the Home Network, the pinging between CN and MN resumes normally as before. > When I start the mip6d the ip6tnl1 does come up on my MN and when the MN goes into a Foreign network, it gets a > new IPv6 address which is consistent, but then why does the pinging between CN and MN stops? > Also the Virtual Terminal (VT) bc command simply does not work. If the ping stop that means the binding process failed so the bc command (VT) have no content. radvd must be running on HA and mip6d must be running on MN and HA before the mouvement. To locate where is the problem between MN and HA your can fire up ethereal on MN and check which element doesn't work. When MN get a new address, it must send BU to HA and HA must reply with a BA to finish the binding process. Send your configuration files. > I am using site local addresses (fec0:106:xxx::xx) in my standalone testbed. > All my nodes (MN, CN, HA, R) are using kernel version 2.6.15.7 (from kernel.org) and I am using > mipv6-2.0.1-linux-2.6.15.patch.gz and mip6-2.0.1. > I have gone over my configurations over and over and over again but now I am clueless. > I would appreciate certainly appreciate your help in giving me a stable test bed. You have almost finished ... -------- Message d'origine-------- De: zarrar yousaf [mailto:[EMAIL PROTECTED] Date: ven. 26/05/2006 18:37 À: Antoine Boutet Objet : MN cant ping CN in Visited Network and VT bc command does not work Hello Antoine, Although i have posted this issue on the MIPL mailing list but i would certainly value your comments as I am following the same steps and configurations as laid out in (www.ipt.etsi.org/mini_howto.htm). the only thing different is that i am using site local addresses rather than global addresses as in your mini howto. I decided not to get tempted into using knoppix because I wanted to learn Linux the hard way :-)....and i did successfully upgraded all my nodes to kernel version 2.6.15.7 (kernel.org) Here is the problem I have I have a functional IPv6 network and the CN and the MN can ping each other when the MN is in the Home Network. When the MN moves to the foreign network the pinging beween MN and CN stops. (My CN is also located on the same Foreign Network.). The CN states "Destination unreachable" and the MN states "Invalid argument". When I plug the MN back into the Home Network, the pinging between CN and MN resumes normally as before. When I start the mip6d the ip6tnl1 does come up on my MN and when the MN goes into a Foreign network, it gets a new IPv6 address which is consistent, but then why does the pinging between CN and MN stops? Also the Virtual Terminal (VT) bc command simply does not work. I am using site local addresses (fec0:106:xxx::xx) in my standalone testbed. All my nodes (MN, CN, HA, R) are using kernel version 2.6.15.7 (from kernel.org) and I am using mipv6-2.0.1-linux-2.6.15.patch.gz and mip6-2.0.1. I have gone over my configurations over and over and over again but now I am clueless. I would appreciate certainly appreciate your help in giving me a stable test bed. Thanks Zarrar Enter the Windows Live Mail beta sweepstakes Upgrade today _________________________________________________________________ Enter the Windows Live Mail beta sweepstakes http://www.imagine-msn.com/minisites/sweepstakes/mail/register.aspx _______________________________________________ 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
