[hipl-users] Re: HIP mobility testings
- From: Simon Schuetz <simon.schuetz@xxxxxxxxxxxxx>
- To: HIPL Users <hipl-users@xxxxxxxxxxxxx>
- Date: 08 Mar 2004 19:57:45 +0100
Got a workaround for the problem:
The intention was to prevent any possible data delivery using the link
local addresses, that's why I shut down the interfaces instead of just
removing the IPs.
What I now did is the following:
- delete all routes using 2nd interface
- delete the IP on 2nd interface
- do a hipsetup and send data
- then I deleted all routing table entries that use the first interface
- then I delete the IP on first interface
- then I setup the routes, that will be used if 2nd interface becomes
available (this was not possible in the previous scenario, cause you
can't setup routing table entries for an interface which down)
- afterwards I added the new IP to the 2nd interface
- HIP REA packets were transmitted immediately
- data can flow
It's a workaround. But I don't think that - in reality - the routes are
setup before the IP is available.
-----
Simon
On Mon, 2004-03-08 at 19:00, Simon Schuetz wrote:
> Hi,
> has anybody tested HIP Mobility in a different way than proposed in the
> HOWTO?
> I'm experiencing problems using the following setup:
> 3 machines: Server (S), Router (R), and a Client (C).
> S and R are connected via one ethernet cable, using static IP6
> addresses.
> C and R are connected via two ethernet cables, IP6 addresses are
> configured such that each connection is a different network.
>
> 1st scenario:
> - shutting down one of C's interfaces
> - completing a hipsetup
> - connecting C with S via HITs
> - send data
> - shutting down C's active interface
> - starting the other interface
> - send data
>
> 2nd scenario:
> - shutting down one of C's interfaces
> - completing a hipsetup
> - connecting C with S via HITs
> - send data
> - unplug ethernet cable
> - delete current IP
> - add new IP
> - plugin ethernet cable
> - send data
>
> Both testings did not work. The fact is, that no HIP REA packets arrive
> at the server side. Either they are not sent when bringing up the
> interfaces or they are sent before they can be routed to the correct
> destination. The requests arrive at the server-side, but the server
> responds to the old IP that is no longer valid.
>
> Suggestions and ideas are welcome.
>
> Thanks
> Simon
>
>
>
>
>
Other related posts:
