<DIV>Hi</DIV>
<DIV> </DIV>
<DIV>The IPv6 address change fix you provided a couple a weeks back doesnt completely solve the IPv6 crash problem. Since you were very busy last month, i didnt bother to disturb you. I went thru the codes, added few conditions in the routing_table.c and neighbor_table.c and now it doesnt crash. Then i encountered this assert failure problem and tired replacing with the old olsr_delete_from_kernel(). </DIV>
<DIV> </DIV>
<DIV>But still i couldnt fully solve the problem when IPv6 address changes. In a nutshell, everything works fine when the preconfigured IPv6 address is used. But when IPv6 address is changed in some of the nodes, it behaves very strangely.</DIV>
<DIV> </DIV>
<DIV>1) Sometimes i could see all the routes in the routing table (route -A inet6), but when i ping6 the nodes, iam unable to reach them. I suspect the interface parameters are not properly attached to the routes. </DIV>
<DIV> </DIV>
<DIV>2) sometimes, the routes are updated only in part of the nodes and in other nodes they routes are not available. Iam confused why this happens</DIV>
<DIV> </DIV>
<DIV>I am uanble to conclude whats happening . But i beleive some changes in the src/unix/ifnet.c prog should solve this</DIV>
<DIV> </DIV>
<DIV>- Rob</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><BR><BR><B><I>Andreas Tønnesen <andreto@olsr.org></I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid"><BR>well... that was a stupid question :) In your version olsrd crashes when<BR>changing (IPv6)address so obviously they never get to the assert call.<BR>Never mind.<BR><BR>- Andreas<BR><BR>Andreas Tønnesen wrote:<BR>> One more thing - does the assertion only fail on nodes who have their<BR>> address changed?<BR>> <BR>> - Andreas<BR>> <BR>> Andreas Tønnesen wrote:<BR>> <BR>>> Hi,<BR>>><BR>>> The IPv6 address change crash is already fixed in CVS. But having the<BR>>> debuglevel 3 output from the assertion(compiled with -DDEBUG) would<BR>>> help tracing that the problem.<BR>>><BR>>> - Andreas<BR>>><BR>>> Robert Frank wrote:<BR>>><BR>>>> Hi<BR>>>> <BR>>>> I am also getting the assertion failed error when the IPv6 address of <BR>>>> the node changes. I have 10 nodes
. I
start the nodes with <BR>>>> preconfigured global Ipv6 address and then change the IPv6 address on <BR>>>> certain nodes (say 5 nodes). when updating the routing table...the <BR>>>> assertion failed error happens.<BR>>>> <BR>>>> I tried replacing the olsr_delete_routes_from_kernel() in the <BR>>>> process_routes.c with the simple link list traverse and delete <BR>>>> (similar to the one use upto 0.4.8 olsr_delete_routes_from_kernel()). <BR>>>> Then it works fine (assertion failed error doesnt happen).<BR>>>> <BR>>>> Also when the IPv6 address changes, the routing table is not formed <BR>>>> properly. I analysing whats happening on when the IPv6 address <BR>>>> changes and i will post a more detailed msg later. Hopefully some <BR>>>> changes in the ifnet.c program will do<BR>>>> <BR>>>> - Rob<BR>>>><BR>>>> */Andreas Tønnesen
<ANDRETO@OLSR.ORG>/* wrote:<BR>>>><BR>>>> Hi Philippe,<BR>>>><BR>>>> Could you provide the output with debug level 3 from when the <BR>>>> assertion<BR>>>> fails?<BR>>>><BR>>>> - Andreas<BR>>>><BR>>>> Philippe Vanhaesendonck wrote:<BR>>>> > Hi!<BR>>>> ><BR>>>> > We are running OLSR 0.4.9 on roughly 25 nodes in the Brussels <BR>>>> area.<BR>>>> ><BR>>>> > On one node, olsrd aborts on a regular base with the following<BR>>>> message:<BR>>>> > olsrd: src/process_routes.c: 318: olsr_delete_routes_from_kernel:<BR>>>> > Assertion `metric_counter' failed.<BR>>>> ><BR>>>> > Some facts:<BR>>>> ><BR>>>> > * I have not seen this on any other nodes (but we are only <BR>>>> running<BR>>>> > OLSR since a couple of days)<BR>>>&
gt; >
* The machine is an i386 BusyBox / uClibc base (Elan SC-400<BR>>>> processor)<BR>>>> > * It runs from a couple of minutes up to a couple of hours<BR>>>> > * We are using NLQ -- all nodes share the same config file<BR>>>> > * The routing is not stable -- that is it changes very fas t. <BR>>>> When<BR>>>> > you run olsr in debug mode (-d 1), it will scroll at high speed.<BR>>>> > This is probably due to the quality of the links, but we have<BR>>>> > substential number of changes in the routes)<BR>>>> ><BR>>>> > Hereunder the config file, a capture of the problem and a <BR>>>> dot-draw of<BR>>>> > the topology (the node having problem is bulles.bxl.rc)<BR>>>> ><BR>>>> > Any idea / suggestions?<BR>>>> ><BR>>>> > thank you in advance<BR>>>> ><BR>>>> > --<BR>>>> >
Phil<BR>>>> ><BR>>>> > ----------------------- Config file<BR>>>> > DebugLevel 0<BR>>>> > IpVersion 4<BR>>>> > ClearScreen yes<BR>>>> > Hna4<BR>>>> > {<BR>>>> > }<BR>>>> > Hna6<BR>>>> > {<BR>>>> > }<BR>>>> > AllowNoInt yes<BR>>>> > IpcConnect<BR>>>> > {<BR>>>> > MaxConnections 1<BR>>>> > Host 127.0.0.1<BR>>>> > Net 192.168.1.0 255.255.255.0<BR>>>> > Net 192.168.29.0 255.255.255.0<BR>>>> > }<BR>>>> > UseHysteresis no<BR>>>> > LinkQualityLevel 2<BR>>>> > LinkQualityWinSize 10<BR>>>> > Pollrate 0.05<BR>>>> > LoadPlugin "olsrd_httpinfo.so.0.1"<BR>>>> > {<BR>>>> > PlParam "port" "8080"<BR>>>> > PlParam "Net" "10.0.0.0 255.0.0.0"<BR>>>> > PlParam "Net
"
"192.168.1.0 255.255.255.0"<BR>>>> > PlParam "Net" "192.168.29.0 255.255.255.0"<BR>>>> > }<BR>>>> > Interface "wlan0"<BR>>>> > {<BR>>>> > }<BR>>>> ><BR>>>> > ----------------------- Example of problem<BR>>>> > # route<BR>>>> > Kernel IP routing table<BR>>>> > Destination Gateway Genmask Flags Metric Ref Use<BR>>>> > Iface<BR>>>> > 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0<BR>>>> > 10.0.0.0 * 255.0.0.0 U 0 0 0<BR>>>> > wlan0<BR>>>> > 127.0.0.0 * 255.0.0.0 U 0 0 0 lo<BR>>>> > default gw.bulles-dsl 0.0.0.0 UG 0 0 0 eth0<BR>>>> > # date; olsrd -d 0 -nofork ; date<BR>>>> > Tue May 17 12:01:35 CES 2005<BR>>>> ><BR>>>> > *** olsr.org - 0.4.9 ***<BR>>>> > Build date: Apr 15 2005<BR>>>> > http://www.olsr.org<BR>>>>
><BR>>>> > Parsing file: "/etc/olsrd.conf"<BR>>>> > Httpinfo olsrd plugin 0.1 by Andreas Tønnesen<BR>>>> > (HTTPINFO) listening on port: 8080<BR>>>> > olsrd: src/process_routes.c: 318: olsr_delete_routes_from_kernel:<BR>>>> Assertion<BR>>>> > `met ric_counter' failed.<BR>>>> > Aborted<BR>>>> > Tue May 17 12:20:16 CES 2005<BR>>>> > # route<BR>>>> > Kernel IP routing table<BR>>>> > Destination Gateway Genmask Flags Metric Ref Use<BR>>>> > Iface<BR>>>> > 10.200.163.254 soekris.bulles. 255.255.255.255 UGH 3 0 0<BR>>>> > wlan0<BR>>>> > 10.6.50.38 soekris.bulles. 255.255.255.255 UGH 2 0 0<BR>>>> > wlan0<BR>>>> > 10.6.13.115 madou.bxl.rc 255.255.255.255 UGH 2 0 0<BR>>>> > wlan0<BR>>>> > 10.9.165.194 madou.bxl.rc 255.255.255.255 UGH 3 0 0<BR>>>> >
wlan0<BR>>>> > 10.10.223.73 soekris.bulles. 255.255.255.255 UGH 2 0 0<BR>>>> > wlan0<BR>>>> > 10.11.11.12 soekris.bulles. 255.255.255.255 UGH 1 0 0<BR>>>> > wlan0<BR>>>> > 10.54.142.132 madou.bxl.rc 255.255.255.255 UGH 3 0 0<BR>>>> > wlan0<BR>>>> > 10.11.1.197 * 255.255.255.255 UH 3 0 0<BR>>>> > wlan0<BR>>>> > 10.8.8.217 madou.bxl.rc 255.255.255.255 UGH 3 0 0<BR>>>> > wlan0<BR>>>> > 10.54.142.133 * 255.255.255.255 UH 1 0 0<BR>>>> > wlan0<BR>>>> > 10.51.17 2.99 madou.bxl.rc 255.255.255.255 UGH 3 0 0<BR>>>> > wlan0<BR>>>> > 10.212.64.121 madou.bxl.rc 255.255.255.255 UGH 3 0 0<BR>>>> > wlan0<BR>>>> > 10.8.39.138 madou.bxl.rc 255.255.255.255 UGH 2 0 0<BR>>>> > wlan0<BR>>>> > 10.3.13.37 madou.bxl.rc 255.255.255.255 UGH 3 0 0<BR>>>> >
wlan0<BR>>>> > 10.9.167.26 madou.bxl.rc 255.255.255.255 UGH 4 0 0<BR>>>> > wlan0<BR>>>> > 10.199.156.169 madou.bxl.rc 255.255.255.255 UGH 3 0 0<BR>>>> > wlan0<BR>>>> > 10.9.175.120 madou.bxl.rc 255.255.255.255 UGH 3 0 0<BR>>>> > wlan0<BR>>>> > 10.9.166.198 madou.bxl.rc 255.255.255.255 UGH 5 0 0<BR>>>> > wlan0<BR>>>> > 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0<BR>>>> > 10.0.0.0 * 255.0.0.0 U 0 0 0<BR>>>> > wlan0<BR>>>> > 127.0.0.0 * 255.0.0.0 U 0 0 0 lo<BR>>>> > default gw.bulles-dsl 0.0.0.0 UG 0 0 0 eth0<BR>>>> ><BR>>>> ><BR>>>> ><BR>>>> ><BR>>>> ><BR>>>> <BR>>>> ------------------------------------------------------------------------<BR>>>> ><BR>>>> ><BR>>>> ><BR>>>> <BR>>>>
------------------------------------------------------------------------<BR>>>> > *> _______________________________________________<BR>>>> > olsr-users mailing list<BR>>>> > olsr-users@olsr.org<BR>>>> > https://www.olsr.org/mailman/listinfo/olsr-users<BR>>>><BR>>>> -- Andreas Tønnesen<BR>>>> http://www.olsr.org<BR>>>> _______________________________________________<BR>>>> olsr-users mailing list<BR>>>> olsr-users@olsr.org<BR>>>> https://www.olsr.org/mailman/listinfo/olsr-users<BR>>>> *<BR>>>><BR>>>> * *<BR>>>><BR>>>> ------------------------------------------------------------------------<BR>>>> *Yahoo! Mail<BR>>>> Stay connected, organized, and protected. Take the tour <BR>>>> <HTTP: mailtour.html tour.mail.yahoo.com>*<BR>>>><BR>>>> *<BR>>>> *<BR>>>>
------------------------------------------------------------------------<BR>>>> *<BR>>>> _______________________________________________<BR>>>> olsr-users mailing list<BR>>>> olsr-users@olsr.org<BR>>>> https://www.olsr.org/mailman/listinfo/olsr-users<BR>>>> *<BR>>><BR>>><BR>>><BR>> <BR><BR>-- <BR>Andreas Tønnesen<BR>http://www.olsr.org<BR>_______________________________________________<BR>olsr-users mailing list<BR>olsr-users@olsr.org<BR>https://www.olsr.org/mailman/listinfo/olsr-users<BR></BLOCKQUOTE><p>
<hr size=1>Yahoo! Mail<br>
Stay connected, organized, and protected. <a href="http://tour.mail.yahoo.com/mailtour.html">Take the tour</a>