<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Dear Rui,<br>
<br>
unfortunately, this issue has been very recently reported (see
here:
<a class="moz-txt-link-freetext" href="https://github.com/maxonthegit/netkit-uml-filesystem/issues/8">https://github.com/maxonthegit/netkit-uml-filesystem/issues/8</a>).<br>
<br>
In a previous email of mine, not appeared on the mailing list, I
have diagnosed the following:<br>
<br>
<blockquote type="cite"><tt>According to the logs, Zebra is unable
to insert a new route into the FIB:<br>
<br>
<blockquote type="cite">netlink-cmd error: invalid argument,
type=RTM_NEWROUTE (24), seq=6, pid=0</blockquote>
<br>
Failure to do so is confirmed by Zebra not marking the route
as a FIB route (missing '*'):<br>
<br>
<blockquote type="cite"><tt>O> 2001:690:866:300::/64
[110/1] via fe80::200:ff:fe00:3, eth1, 00:04:32</tt></blockquote>
<br>
I have just tried with an upgraded version of Quagga from the
Debian repository (0.99.18) and it seems to work fine.</tt></blockquote>
<br>
To some extent, this seems to be related with this report:
<a class="moz-txt-link-freetext" href="http://www.gossamer-threads.com/lists/quagga/dev/19226">http://www.gossamer-threads.com/lists/quagga/dev/19226</a> (and there
are other similar ones regarding blackhole routes too).<br>
<br>
For the moment there seems to be no better workaround than
upgrading Quagga in the Netkit filesystem.<br>
<br>
Regards,<br>
Massimo<br>
<br>
</tt><br>
On 09/19/2011 03:34 PM, Costa >> wrote:
<blockquote
cite="mid:CACS32yAC_Phf9bwoJHd8sfwMk4qO=QsBrdvTG=hakm90ahj8Pg@mail.gmail.com"
type="cite">Hi all,<br>
<br>
Has anyone used/tested IPv6 routing on netkit using the embedded <br>
Quagga routing deamons of the IPv6 routing protocols RIPng/OSPFv6?
<br>
<br>
From my (very limited) experience with netkit routing in IPv4 both
RIP <br>
and OSPF work fine, but in IPv6, both RIPng and OSPFv6 don't seem
<br>
to work properly. I don't get any routes on the kernel ipv6 tables
and <br>
ipv6 messages are not forwarded.<br>
<br>
I can see protocol signalling messages (hello messages, etc...) in
the <br>
virtual machine's networks if I do a tcpdump.<br>
If I do a telnet to the correspondent quagga deamon I can see that
the <br>
routing tables of the protocols themselves are ok. But somehow the
<br>
routing rules don't seem to be put in the kernel routing tables,
because<br>
a dump of the tables only shows directly connected networks.<br>
Any ideas on what is causing this?<br>
<br>
<br>
Best Regards,<br>
Rui Costa<br>
<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Netkit.users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Netkit.users@list.dia.uniroma3.it">Netkit.users@list.dia.uniroma3.it</a>
<a class="moz-txt-link-freetext" href="http://list.dia.uniroma3.it/mailman/listinfo/netkit.users">http://list.dia.uniroma3.it/mailman/listinfo/netkit.users</a>
</pre>
</blockquote>
</body>
</html>