<div dir="ltr">All,<div><br></div><div>To add some context... The test case of cat5/RF paths between nodes matches our packaging of "Device to Device Linking (DtDLink)" to connect between radios and bands (2Ghz, 3Ghz, 5Ghz) over cat5 at a tower or cell site with coverage areas on multiple/separated channels. We have sites with 2 nodes on the same channel-band in use (2 sector antenna coverage areas). There are sometimes limitations of usable channels (or simply cost) at a given site. </div><div><br></div><div>In the future, maybe ~1 year, we expect to incorporate some of the Mikrotik devices and I believe these devices have dual band capabilities. If so, the test case would become 2 ~equal RF paths between devices. Route flapping would become more of an issue. I'd be concerned if the current proposed patch will bypass hysteresis logic and create more problems to solve. The choice of which path to advertise becomes less clear.</div><div><br></div><div>Joe AE6XE </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jan 7, 2017 at 2:16 AM, Conrad Lara <span dir="ltr"><<a href="mailto:ipstealer@cox.net" target="_blank">ipstealer@cox.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thank you for the correction on the Git repo location.<br>
<br>
I have compiled the latest master<br>
Version: <a href="http://olsr.org" rel="noreferrer" target="_blank">olsr.org</a> - pre-0.9.6-git_5ee1d70-hash_<wbr>ecb831632bf30f993cce28d483e93d<wbr>1a (built on 2017-01-07 01:55:21 on node97)<br>
<br>
I can duplicate the issue on master using the exact same setup and config file that I used on 0.6.6.1 that was not able to duplicate the flaw.<br>
<br>
This appears to me to have become an issue sometime after 0.6.6.1.<br>
<br>
Here it is on 5ee1d70801aad04f0ce51f4ecf9767<wbr>1b5f5c15a9<br>
<br>
Node 61:<br>
Links<br>
Local IP Remote IP Hysteresis LinkCost<br>
172.29.175.61 172.28.175.97 0.00 (1.000/0.000) INFINITE<br>
172.31.175.61 172.31.175.97 0.00 (1.000/1.000) 1.000<br>
172.29.175.61 172.29.175.97 0.00 (1.000/0.000) INFINITE<br>
<br>
<br>
Node 97:<br>
Links<br>
Local IP Remote IP Hysteresis LinkCost<br>
172.31.175.97 172.31.175.61 0.00 (1.000/1.000) 1.000<br>
172.29.175.97 172.29.175.61 0.00 (1.000/1.000) 0.100<br>
172.28.175.97 172.29.175.61 0.00 (1.000/1.000) 0.100<br>
<br>
Best Regards<br>
Conrad Lara<br>
<br>
---- Ferry Huberts <<a href="mailto:mailings@hupie.com">mailings@hupie.com</a>> wrote:<br>
> <a href="https://github.com/OLSR/olsrd.git" rel="noreferrer" target="_blank">https://github.com/OLSR/olsrd.<wbr>git</a><br>
><br>
> On 06/01/17 22:44, Conrad Lara wrote:<br>
> ><br>
> > ---- Ferry Huberts <<a href="mailto:mailings@hupie.com">mailings@hupie.com</a>> wrote:<br>
> >><br>
> >><br>
> >> On 06/01/17 21:41, Conrad Lara wrote:<br>
> >>>>> Ubuntu 14.04 running stock available <a href="http://olsr.org" rel="noreferrer" target="_blank">olsr.org</a> -<br>
> >>>>> 0.6.6.1-git_0000000-hash_<wbr>41d32a614ae55e881b7c0456c8e3ed<wbr>54 (built<br>
> >>>>> on 2013-10-26 05:10:52 on toyol)<br>
> >>>>><br>
> >>>><br>
> >>>> That olsrd is very very old.<br>
> >>>><br>
> >>>> Use master.<br>
> >>>><br>
> >>><br>
> >>> I agree it is an old version and will give the latest mainline a<br>
> >>> test, but if this issue only occurs in master I would believe that<br>
> >>> would make this a regression flaw in hello message parsing and<br>
> >>> shouldn't we instead look at placing the code there instead of<br>
> >>> changing how we broadcast hello's by removing data that has<br>
> >>> historically been broadcasted over the network?<br>
> >>><br>
> >><br>
> >><br>
> >> Once you are able to reproduce it on master and with that same setup NOT<br>
> >> on 0.6 then I will look into bisecting it when I'm also able to confirm<br>
> >> that.<br>
> ><br>
> ><br>
> > I believe the OLSR Git repo's may be experiencing some public access issues right now (or they have moved and my notes about the location are no longer accurate) as I am unable to access them from multiple networks to obtain the latest master branch for testing.<br>
> ><br>
> > Per: <a href="http://olsr.org/git/?p=olsrd.git;a=summary" rel="noreferrer" target="_blank">http://olsr.org/git/?p=olsrd.<wbr>git;a=summary</a><br>
> ><br>
> > git clone git://<a href="http://olsr.org/olsrd.git" rel="noreferrer" target="_blank">olsr.org/olsrd.git</a><br>
> > git clone <a href="http://olsr.org/git/olsrd.git" rel="noreferrer" target="_blank">http://olsr.org/git/olsrd.git</a><br>
> ><br>
> > cmlara@node97:~/olsrd$ git clone <a href="http://olsr.org/git/olsrd.git" rel="noreferrer" target="_blank">http://olsr.org/git/olsrd.git</a><br>
> > Cloning into 'olsrd'...<br>
> > fatal: unable to access '<a href="http://olsr.org/git/olsrd.git/" rel="noreferrer" target="_blank">http://olsr.org/git/olsrd.<wbr>git/</a>': The requested URL returned error: 403<br>
> ><br>
> > cmlara@node97:~/olsrd$ git clone git://<a href="http://olsr.org/olsrd.git" rel="noreferrer" target="_blank">olsr.org/olsrd.git</a><br>
> > Cloning into 'olsrd'...<br>
> > fatal: unable to connect to <a href="http://olsr.org" rel="noreferrer" target="_blank">olsr.org</a>:<br>
> > <a href="http://olsr.org" rel="noreferrer" target="_blank">olsr.org</a>[0: 193.238.157.30]: errno=Connection timed out<br>
> > <a href="http://olsr.org" rel="noreferrer" target="_blank">olsr.org</a>[1: 2a02:60:1:1::c]: errno=Connection timed out<br>
> ><br>
> ><br>
> > <a href="http://www.olsr.org" rel="noreferrer" target="_blank">http://www.olsr.org</a> has the following error preventing me from double checking the main page for the git repo address.<br>
> ><br>
> > "A database query error has occurred. This may indicate a bug in the software."<br>
> ><br>
<span class="HOEnZb"><font color="#888888">><br>
> --<br>
> Ferry Huberts<br>
<br>
<br>
--<br>
Olsr-dev mailing list<br>
<a href="mailto:Olsr-dev@lists.olsr.org">Olsr-dev@lists.olsr.org</a><br>
<a href="https://lists.olsr.org/mailman/listinfo/olsr-dev" rel="noreferrer" target="_blank">https://lists.olsr.org/<wbr>mailman/listinfo/olsr-dev</a></font></span></blockquote></div><br></div>