[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(usagi-users 03081) radvd problem: routes aren't deleted
- To: usagi-users@xxxxxxxxxxxxxx
- Subject: (usagi-users 03081) radvd problem: routes aren't deleted
- From: "Tobias Hof" <Tobias.Hof@xxxxxx>
- Date: Mon, 25 Oct 2004 20:38:12 +0200 (MEST)
- Reply-to: usagi-users@xxxxxxxxxxxxxx
Hi everybody,
I'm trying to update a MobileIPv6 platform.
I installed Fedora Core2 (kernel 2.6.6), and I added a 2.6.8 USAGI kernel
which I use normally.
On two boxes which serve as router I installed zebra 0.93a-3 (for opsfd
(IPv4) and ripngd(IPv6)) and radvd 0.7.2-7.
Now I noticed the following two problems:
1) When I plug the radvd client on the router which is supposed to be the HA
later on, it builds its stateless address and adds a default route towards
the router. When I move the radvd client to the link behind the second
router, I can see that a second stateless address is built and that the
first one disappears after several second (i.e.,for some time, he has two
stateless addresses)
Now the problem is that also the default route is supposed to be replaced by
a route to the new router, isn't it?
I can see that the default route has always a lifetime of two seconds
(doesn't change at all) and if I plug the machine to the second router, the
new default route has also a lifetime which seems to be fixed at 2s. The
lifetime of the old default route, however, goes down to zero but instead of
being removed, the timer is set to something over 2 000 000 (2 133 ???)
seconds and is counting down...
So I have to problems:
- Why is the timer of the default route not activated while the route is
valid and only when the route is not any more?
- Why is the route not erased after tha lifetime has expired but instead set
to over 2 millions?
2) Second issue:
How I can I make that the radvd client uses his temporary stateless address
(for a ping, e.g.) as source address instead of using his home address?
I tried to set /proc/sys/net/ipv6/conf/all/use/tempaddr=1, but it doesn't
seem to work...
Before, I used a 2.4 kernel and I didn't have this kind of problems... My
platform is built with VMWare 4.5.2, but I don't think that that is the
source of the problem...
It would be great of you if somebody could help me with this problem, as I
have no idea how to solve this!!
Best regards,
Tobias
I have the following in /proc/sys/net/ipv6/conf/all:
forwarding=0
accept_ra=1
accept_redirect=1
autoconf=1
temp_prefered_lft=10
temp-valid-lft=30
The radvd is configured with
..
AdvValidLifetime 30;
AdvPreferedLifetime 10;
..
--
Geschenkt: 3 Monate GMX ProMail + 3 Ausgaben der TV Movie mit DVD
++++ Jetzt anmelden und testen http://www.gmx.net/de/go/mail ++++