https://www.open-mesh.org/https://www.open-mesh.org/favicon.ico?16699090422011-10-20T05:28:42ZOpen Meshbatman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=1862011-10-20T05:28:42ZAnonymous
<ul></ul><p>I update to the latest version 2011.3.1</p> batman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=1872011-10-20T06:09:35ZAnonymous
<ul></ul><p>li langfeng wrote:</p>
<blockquote>
<p>I update to the latest version 2011.3.1</p>
</blockquote>
<p>Does it mean that this also happens with 2011.3.1 or that this is fixed with 2011.3.1?</p> batman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=1882011-10-20T08:05:31ZAnonymous
<ul></ul><p>Sven Eckelmann wrote:</p>
<blockquote>
<p>li langfeng wrote:</p>
<blockquote>
<p>I update to the latest version 2011.3.1</p>
</blockquote>
<p>Does it mean that this also happens with 2011.3.1 or that this is fixed with 2011.3.1?</p>
</blockquote>
<p>yes! 2011.3.1 The same is true!</p> batman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=1892011-10-20T08:12:00ZAntonio Quartulli
<ul></ul><p>Hello, is the debug ON? to funther investigate the problem we would need some nice output from the nodes in order to understand what is going on.</p>
<p>First of all what does "unstable communication" mean? PC1 ping to AP3 works for a bunch of seconds then stops and then works again?</p> batman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=1902011-10-20T09:03:12ZSimon Wunderlichsw@simonwunderlich.de
<ul></ul><p>Can you exclude problems on the WiFi layer? You can check this by:</p>
<ul>
<li>have a look in "batctl o" if all nodes are in the table</li>
<li>assign an IP address on ath0 (e.g. 192.168.2.1-3), and try to ping this one respectively.</li>
</ul> batman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=1912011-10-20T09:31:15ZAnonymous
<ul></ul><p>Simon Wunderlich wrote:</p>
<blockquote>
<p>Can you exclude problems on the WiFi layer? You can check this by:</p>
<ul>
<li>have a look in "batctl o" if all nodes are in the table</li>
<li>assign an IP address on ath0 (e.g. 192.168.2.1-3), and try to ping this one respectively.</li>
</ul>
</blockquote>
<p>I did not open debug, I should how to provide the more detailed information to you.<br />All AP first open open the power supply, PC1 to AP1,AP2,AP3 are normal, when we AP1 people will shut off the power to turn on the power, PC1 can only to AP1,AP2, completely unable to AP3 (not is not stable, it is completely unable to connect), the problem can be repeated every time.</p> batman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=1922011-10-20T09:35:48ZAntonio Quartulli
<ul></ul><p>li langfeng wrote:</p>
<blockquote>
<p>I did not open debug, I should how to provide the more detailed information to you.</p>
</blockquote>
<p>Please, can you provide us the output of "batctl o" "batctl tg" and "batctl tl" either before turning off AP1 and after?</p>
<blockquote>
<p>All AP first open open the power supply, PC1 to AP1,AP2,AP3 are normal, when we AP1 people will shut off the power to turn on the power, PC1 can only to AP1,AP2, completely unable to AP3 (not is not stable, it is completely unable to connect), the problem can be repeated every time.</p>
</blockquote>
<p>Ok, thanks for the detail</p> batman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=1932011-10-20T09:38:08ZAntonio Quartulli
<ul></ul><p>Another question: What devices are those? (Please tell us the full name of the devices)</p> batman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=1942011-10-20T09:38:55ZAnonymous
<ul></ul><p>AP1 ping to <abbr title="IP">AP3</abbr> not connected,AP1 brtctl tr to <abbr title="MAC">AP3</abbr> connection to normal</p> batman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=1952011-10-20T09:42:00ZAnonymous
<ul></ul><p>Antonio Quartulli wrote:</p>
<blockquote>
<p>Another question: What devices are those? (Please tell us the full name of the devices)</p>
</blockquote>
<p>AP:AR730+AR5414,openwrt backfire 10.03.1-rc6,r28443+madwifi(ahdemo)</p> batman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=1962011-10-20T09:43:27ZAnonymous
<ul></ul><p>li langfeng wrote:</p>
<blockquote>
<p>Antonio Quartulli wrote:</p>
<blockquote>
<p>Another question: What devices are those? (Please tell us the full name of the devices)</p>
</blockquote>
<p>AP:AR730+AR5414,openwrt backfire 10.03.1-rc6,r28443+madwifi(ahdemo)</p>
</blockquote>
<p>sorry!<br />AR730=AR7130</p> batman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=1972011-10-20T14:05:49ZAntonio Quartulli
<ul></ul><p>Thank you. But, please, can you also provide the output of "batctl o", "batctl tg" and "batctl tl" either before and after the reboot of AP1?</p> batman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=1982011-10-21T03:35:28ZAnonymous
<ul><li><strong>File</strong> <a href="/attachments/93">batman.doc</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/93/batman.doc">batman.doc</a> added</li></ul><p>Antonio Quartulli wrote:</p>
<blockquote>
<p>Thank you. But, please, can you also provide the output of "batctl o", "batctl tg" and "batctl tl" either before and after the reboot of AP1?</p>
</blockquote>
<p>The attached file for green coating is after the reboot information,In the global MAC address table can be found in the missing part</p> batman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=1992011-10-23T19:46:42ZAntonio Quartulli
<ul><li><strong>File</strong> <i>0001-batman-adv-print-the-value-in-the-tt_global_entry-co.patch</i> added</li></ul><p>Hello, sorry for the delay. Your bug seems to be related to a bug we found this weekend. I'm attaching a patch which should help in this way. Can you please test it and tell us if it solves or not?</p> batman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=2002011-10-23T19:53:08ZAntonio Quartulli
<ul><li><strong>File</strong> deleted (<del><i>0001-batman-adv-print-the-value-in-the-tt_global_entry-co.patch</i></del>)</li></ul> batman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=2012011-10-23T19:53:27ZAntonio Quartulli
<ul><li><strong>File</strong> <a href="/attachments/95">0001-batman-adv-unify-hash_entry-field-position-in-tt_loc.patch</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/95/0001-batman-adv-unify-hash_entry-field-position-in-tt_loc.patch">0001-batman-adv-unify-hash_entry-field-position-in-tt_loc.patch</a> added</li></ul> batman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=2022011-10-30T08:05:07ZAnonymous
<ul></ul><p>I'm sorry, these days have gone out, I to download the latest source code, and the patch, this problem is gone, I found that the direct through from 2011.3.0 openwrt update to 2011.3.1 some file was not renewed.</p> batman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=2032011-10-30T15:52:40ZSimon Wunderlichsw@simonwunderlich.de
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>So the bug is gone? I'll mark the bug as resolved then.</p>
<p>Thanks for reporting.</p> batman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=2092011-11-01T10:39:01ZSimon Wunderlichsw@simonwunderlich.de
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul> batman-adv - Bug #154: Mesh link work abnormalitieshttps://www.open-mesh.org/issues/154?journal_id=10972017-02-11T08:27:11ZSven Eckelmann
<ul><li><strong>Target version</strong> set to <i>2012.0.0</i></li></ul>