From: DougAtHome (dcalton@fuse.net)
Date: Wed Feb 12 2003 - 20:16:03 GMT-3
Thanks for the explanation. I can't test with wireless at this time - my
lab budget has had it for now, I'm afraid! Thanks also for the MIP client
link. I will look at it more closely later. As I struggle with this
(including my bone-headed mask mistake), I wonder how many scenarios are on
the lab where you cannot realistically test the configs given the lab setup.
Guess for these items, you have to sight check as best you can. I suppose
that these items are generally small point value anyway, but still, every
point helps.
----- Original Message -----
From: "P729" <p729@cox.net>
To: "Doug Calton" <dcalton@fuse.net>; "ccielab" <ccielab@groupstudy.com>
Sent: Wednesday, February 12, 2003 5:26 PM
Subject: Re: Problem getting local mobility to work
> IIRC, when you enable LAM, host routes will begin to populate the RT as
"M"
> derived routes. It is these routes that you would redistribute into an IGP
> to extend "mobility area". (Please let me know if I'm all wet on this)
>
> Are you able to test with wireless? Essentially, wireless roaming is a
> layer-2 handoff; LAM uses ARP/RARP as a sort of registration/heartbeat
> process. It'd be interesting to see how the two interact... My guess would
> be it would support "nomadic" roaming (stop, move, start) and not
seamless,
> non-stop roaming (say for VoIP). MIP clients are supposed to be able to
hand
> off seamlessly, ostensibly through interaction with the agents and perhaps
> some preemptive or anticipatory measures. Then again, some of the latter
is
> being incorporated directly into some access points...
>
> In case you want to pursue it, Birdstep (www.birdstep.com) is the only MIP
> client I know of.
>
> Regards,
>
> Mas Kato
> https://ecardfile.com/id/mkato
>
> ----- Original Message -----
> From: "Doug Calton" <dcalton@fuse.net>
> To: "P729" <p729@cox.net>; "ccielab" <ccielab@groupstudy.com>
> Sent: Wednesday, February 12, 2003 4:40 AM
> Subject: Re: Problem getting local mobility to work
>
>
> Thanks - I am trying LAM, not MIP. AFAIK, there are no clients for MIP
> available, so I have never been able to really test MIP. Anyway, as to
your
> note that with LAM, I need to configure the ip mobile arp and redistribute
> commands on the home network as well, I am surprized, but I will try it.
As
> for the ip route mobile, I am unclear if this is needed for LAM or not.
If
> it is not required, I wonder what the redistribute is distributing.
Again,
> I will test out later today and post results on the newsgroup. Thanks for
> the explanation.
>
> ----- Original Message -----
> From: "P729" <p729@cox.net>
> To: "DougAtHome" <dcalton@fuse.net>; "ccielab" <ccielab@groupstudy.com>
> Sent: Tuesday, February 11, 2003 9:06 PM
> Subject: Re: Problem getting local mobility to work
>
>
> > First of all, you may want to sort out what you're really trying to
> > accomplish: Local Area Mobility (LAM) or Mobile IP (MIP). There appears
to
> > be fragments of each in your sample config.
> >
> > The 'ip mobile arp' interface command and the 'redistribute mobile'
> routing
> > process command in Rtr5 enable LAM on Rtr5. You'll need complementary
> > commands on Rtr2 and I believe you'll need to make the subnets
contiguous
> > (change to /24 masks or re-address one or the other).
> >
> > The 'router mobile' global command enables MIP, but the rest of a MIP
> > configuration appears to be missing (home and foreign agents, etc.).
You'd
> > also need a MIP client on your host(s) or transparent proxies (like
> Aironet
> > 350s with the latest code).
> >
> > Regards,
> >
> > Mas Kato
> > https://ecardfile.com/id/mkato
> >
> > ----- Original Message -----
> > From: "DougAtHome" <dcalton@fuse.net>
> > To: "ccielab" <ccielab@groupstudy.com>
> > Sent: Tuesday, February 11, 2003 5:33 AM
> > Subject: Problem getting local mobility to work
> >
> >
> > I have been trying to get mobile IP to work in a local network. For
> > purposes
> > of this discussion, the topology is like so:
> >
> > VLAN11 (170.10.11.0/26) -- Rtr2 -----Frame Relay --Rtr5 -- VLAN34
> > (170.10.10.1/26)
> >
> > Rtr2's VLAN I/F is EIGRP, which redistributes into OSPF (and OSPF into
> > EIGRP),
> > while the FR ntwk is Area 0 OSPF. VLAN 34 is in area 2.
> >
> > Full routing in the network is available, no bugs or issues.
> >
> > I configured a PC with an IP addr of 170.10.11.5/26 (gateway
170.10.11.1,
> > which is the Rtr2 I/F), and move it to VLAN 34, but it does not start up
> > Router Mobile, nor can I ping anywhere out of the PC. I have installed
> the
> > commands as I understand from Cisco documentation, but no soap. Does
any
> > one
> > have a working config or a link showing this with an example?
> >
> > Following is my current config of Rtr5, if needed. TIA!
> >
> > hostname Rtr5
> > enable secret 5 $1$16B7$XA9fx4lFw2T3sLiXSzjqy1
> > clock timezone EST -5
> > clock summer-time EDT recurring
> > ip subnet-zero
> > no ip domain-lookup
> > ip audit notify log
> > ip audit po max-events 100
> > ip ssh time-out 120
> > ip ssh authentication-retries 3
> > call rsvp-sync
> > interface Loopback0
> > ip address 170.10.5.1 255.255.255.0
> > ip ospf network point-to-point
> > interface Ethernet0/0
> > ip address 170.10.10.2 255.255.255.192
> > ip mobile arp access-group 10
> > ip ospf authentication
> > ip ospf authentication-key xxxxxx
> > ip ospf message-digest-key 1 md5 xxxxxxxx
> > half-duplex
> > interface Serial0/0
> > ip address 170.10.8.5 255.255.255.240
> > encapsulation frame-relay
> > ip ospf message-digest-key 1 md5 xxxxxxx
> > ip ospf network point-to-multipoint
> > no fair-queue
> > frame-relay interface-dlci 52
> > frame-relay interface-dlci 53
> > no frame-relay inverse-arp
> > interface Ethernet0/1
> > no ip address
> > shutdown
> > half-duplex
> > router mobile
> > distance 80
> > router ospf 1
> > log-adjacency-changes
> > area 0 authentication message-digest
> > area 0 range 170.10.8.0 255.255.255.0
> > area 2 range 170.10.10.0 255.255.255.0 cost 54
> > area 2 virtual-link 170.10.7.1 message-digest-key 1 md5 xxxxxxx
> > redistribute mobile metric 54 subnets
> > network 170.10.5.1 0.0.0.0 area 2
> > network 170.10.8.5 0.0.0.0 area 0
> > network 170.10.10.2 0.0.0.0 area 2
> > ip classless
> > ip http server
> > access-list 10 permit 170.10.11.0 0.0.0.192
> > dial-peer cor custom
> > line con 0
> > session-timeout 60
> > exec-timeout 60 0
> > password xxxxx
> > login
> > line aux 0
> > line vty 0 4
> > session-timeout 60
> > exec-timeout 60 0
> > password xxxxx
> > login
> > line vty 5 15
> > login
> > ntp authentication-key 1 md5 xxxxxxxx
> > ntp authenticate
> > ntp trusted-key 1
> > ntp clock-period 17208130
> > ntp server 170.10.9.1
> > end
> > .
.
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:20 GMT-3