Hi Sebastian,
[EMAIL PROTECTED] wrote:
Firstly, I want to ask is it theoretical possible to use the Alternate Care-of
address option in mobile-ipv6 binding updates for registrations behind a
IP-nat router?
The option would carry the IP-Address behind the nat-router because the
nat-router will change the source address of the binding update.
The standard says that it can used when the Care-of Address cannot be used as
a "topologicaly correct source address".
Are you talking about an IPv6 Router doing NAT? I am not sure what you
plan to do, but the notion of NAT is deprecated in IPv6.
More generally, the Alternate-CoA option can be used to store the CoA
that will be registered to the Home Agent. The HA picks up the CoA in
the alternate-coa option if present, otherwise in the source address of
the packet.
Secondly I want to ask what is the task of the "HaServedPrefix" - option in
the nemo - HA configuration?
I have read the manual but I didn't realy understand what is meaning by:
"if the MRs derive their Home Addresses from their Mobile Network Prefixes,
in stead of one of the home link prefixes"
In my opinion the MR gets it's home-prefix form a router-advertisment or from
the config-file.
In my configuration I used the following addresses:
Home-Network Prefix: 2001:0020::/64
Mobile-Network Präfix: 2001:0021::/64
Foreign Network-Prefixes: 2001:0010::/64
2001:0012::/64
2001:0013::/64
HaServedPrefix on HA: 2001:2001:0020::/28
Is this correct?
If the HoA of your MR is derived from the Home Link Prefix, then
HaServedPrefix is set to the Home Link Prefix. In your case:
HaServedPrefix 2001:0020::/64;
And last I have a routing problem in my testbed.
When the MR is at home, I can't ping the MNNs from a foreign network.
The reason is that the MR is only forwarding packages to the Home-Network and
to the Mobile-Network (in that networks where it is connected to). The MR
self can ping everything because it has a default route to the HA.
When the MR moves into a foreign network everything works fine.
To make it work when it is in the home-network I must set up manually
following route on the MR after starting the nemd:
ip -6 add route from MOBILE_NETWORK via HA dev eth0
and "ip -6 route show" shows amongst others :
default from 2001:21::/64 via 2001:20::1 dev eth0
When the MR is in a foreign network, the daemon makes itself such from-routes
via the tunnel-interface.
Is the hand-made route OK? Or is there a mistake in my configuration?
There is no mistake in your configuration, and the hand-made route
should not be necessary. Actually this is a known bug: when the MR is at
home, forwarded packets are not correctly routed by the MR. I had a look
at this problem few weeks ago, but I must admit that I could not solve
it properly yet. If I have news about that, I'll post it here.
Regards,
--
Romain KUNTZ
[EMAIL PROTECTED]
_______________________________________________
mipl mailing list
[email protected]
http://www.mobile-ipv6.org/cgi-bin/mailman/listinfo/mipl
