I'm trying to play around with this as well, and have reviewed various forum histories to determine why my config is failing. Like Grad Alfons Canon reported on 7/28/01, my attempts give me the "MobileIP: Interface # add ip.add.re.ss rejected" message. One point of confusion for me is the "care-of" address. Grad's example used the same I/F for foreign service and for the care-of address. Cisco's example uses a different I/F in a separate subnet. Without an accompanying ntwk diagram, it's hard to tell if this second I/F leads back to the central network or not. Finally Bill Creighton's above sample uses a different I/F on the SAME subnet. As described, one would presume that ANY I/F with an IP addr advertized into the network would be suitable (maybe even loopbacks), since the point is to allow the FA and HA to communicate and set up registration and subsequent tunneling. Does anyone know if there are specific mandates as to what the care-of I/F should be?
Second issue is client (MN) software. As I read it, the MN software is responsible for establishing registration with an advertising HA so that when the client roams it can request a session with the HA from the FA. Secondly, the client must support MD5 authentication with the HA, although presumably this is not necessary in the above configs, since SA keys are not established. Any info on what the client has to do to support this, if anything? Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=57348&t=52215 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
