[Olsr-users] ignore whether interface is wireless

[Lonnie Nunweiler]

It makes no difference what OLSR thinks about the devices (ethernet or
wireless).  It seems the driver is refusing to send out hellos in AP mode.
Client mode is fine.  I've been over and over the code and I do not have
the knowledge to fix it, so I have started to convert it all to the ath9k
driver, which does work fine.  In the long run it will be best.  The big
shame is the many hours spent on the failing driver.  It has to be
something silly, but I cannot find it.

Now I get to spend many hours to bring the enhancements into the ath9k.
Should be done in a few weeks.  A few guys are testing for me and they are
impatient to get the old features back.  At least OLSR works, which would
be a deal breaker for my users.

Thanks to all for the advice.


Lonnie Nunweiler
Gigabit Gecko Ltd

FREE Password Helper:   http://www.gigabit-gecko.com/
web: http://www.star-os.com/
store: http://cue-link.com/store/

On Mon, May 15, 2017 at 11:22 PM, Henning Rogge <(spam-protected)> wrote:

> Hi,
>
> I would also suggest NOT touching the "LQ level" parameter...
> switching off ETX is just stupid, especially because the "No ETX" and
> "ETX" Olsrd instances cannot talk with each other.
>
> Just let OLSR pretent that you ethernet is wireless and you will be fine.
>
> Henning
>
>
>
> On Thu, May 4, 2017 at 6:08 PM, Lonnie Nunweiler
> <(spam-protected)> wrote:
> > OK, tcpdump is my new friend.
> >
> > I was dumping at the AP and it all seemed OK.  It was only when I looked
> at
> > what was happening at the client that I saw what was going on.
> >
> > Conditions:
> >
> > AP: OLSR on.
> >
> > Client: OLSR off.  This is simply so that tcpdump will only be showing
> what
> > comes in to it.  With OLSR running the tcpdump is showing periodic sends,
> > BUT, and this is the kicker, there is NO traffic from the AP.
> >
> > When the AP is ath9k the client receives OLSR traffic from the AP.  When
> the
> > AP is the qcp driver the client receives nothing from the AP.  So the
> > problem is identified and now all I have to do is figure out why the qcp
> > driver does not send OLSR messasges.
> >
> > Thanks for the advice.  It is much appreciated.
> >
> > Lonnie
> >
> >
> >
> > Lonnie Nunweiler
> > Gigabit Gecko Ltd
> >
> > FREE Password Helper:   http://www.gigabit-gecko.com/
> > web: http://www.star-os.com/
> > store: http://cue-link.com/store/
> >
> > On Wed, May 3, 2017 at 2:16 AM, Lars Kruse <(spam-protected)> wrote:
> >>
> >> Hi Lonnie,
> >>
> >>
> >> Am Tue, 2 May 2017 22:16:26 -0700
> >> schrieb Lonnie Nunweiler <(spam-protected)>:
> >>
> >> > The AP seems to be receiving Hellos from its clients.  I'll add a
> >> > specific
> >> > debug and verify this.
> >>
> >> you can verify this easily via tcpdump:
> >>  tcpdump -npi eth0 port 698
> >> Every three seconds you should see at least one packet from every host
> >> attached
> >> to that interface.
> >>
> >> Regarding the output of the httpinfo plugin: I am only used to etx-based
> >> routing metrics (with their LQ and NLQ values) - thus I cannot tell, if
> >> your
> >> output indicates a problem or not.
> >>
> >> Cheers,
> >> Lars
> >
> >
> >
> > --
> > Olsr-users mailing list
> > (spam-protected)
> > https://lists.olsr.org/mailman/listinfo/olsr-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20170515/696ac590/attachment.html>