Sorry, the problem has been resolved and it's not OLSR or Orinoco related, but rather IP related, even though I carefully checked configuration before.<br>You can disregard the previous message.<br><br>Sorry for the disturbing caused.
<br>Regards,<br>Florian<br><br><div><span class="gmail_quote">2007/11/27, Florian RODARY <<a href="mailto:florian.rodary@insa-lyon.fr">florian.rodary@insa-lyon.fr</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br><br>I'm facing a problem that appeared just today.<br>I'm dealing with a simple three nodes ad-hoc topology.<br>When running OLSRd for the first time on Orinoco-equipped nodes, nothing appears in the debugging output. I've found that running a tcpdump instance will cause instantly OLSRd to react and build the topology. It seems that switching promiscuous states will resolve the problem.
<br><br>This problem is strange since it worked well before. I don't think it's OLSR related, but rather Orinoco related since Tx excessive retries and Rx invalid frag counters in iwconfig are incremented before running tcpdump.
<br>Does anyone have any idea about that, or faced the same similar problem ?<br><br>Thanks in advance.<br>Regards,<br><span class="sg">Florian<br>
</span></blockquote></div><br>