[Olsr-users] (no subject)

Lonnie Nunweiler (spam-protected)
Tue May 16 08:55:56 CEST 2017

There are no errors generated.  It all connects just to port 698.  All
devices are found and it seems to have full knowledge of them all.  In
client mode it has no issue and it all works.  In AP mode it refuses to
send the hellos, identified by seeing nothing with tcpdump at the client.

Not sure how to fix it.  My skill level is like advanced mechanic level.  I
can swap out an engine, but when something internal is awry I'm screwed.  I
have updated the driver through 3 revisions and I have updated the kernel
from 3.10.58 to 3.18.45.  I won't say it was easy but I did it and it
works.  If there was a deep kernel issue I would be in the same boat.

Now I am swapping the qca driver for the ath9k and it is working.  It does
not have the performance and I have a lot of enhancements to add, but OLSR
works just fine, so I have to go with it.

Thanks for advice and concern.  It is appreciated.


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:19 PM, Henning Rogge <(spam-protected)> wrote:

> Hi,
> maybe you could describe what is happening when you connect Olsrd to
> the qca wireless interface?
> Do you see the UDP socket for the interface? Do you see OLSR packets
> (UDP port 698)?
> Henning Rogge
> On Mon, May 1, 2017 at 11:54 PM, Lonnie Nunweiler
> <(spam-protected)> wrote:
> > Hi,
> >
> > Im am charged with adding OLSRto an existing firmware based on the
> Qualcom
> > qca driver, which has been working for many years.
> >
> > When OLSR runs it knows as much about the wireless as it does about the
> > Ethernet.  All ioctl calls have been checked and not a single error.The
> > does not use NL80211 but from my research that is optional anyway.
> >
> > To check for a stupid move on my part I changed to ath9k.  Same hardware,
> > same OS, just different driver.  It works perfectly.
> >
> > Does anyone have an idea of what the issue could be and where I should
> begin
> > to look?  I've spent a week tracking and adding "OLSR_PRINTF(1," to see
> the
> > contents of the structures, but to me they all look OK, but it refuses to
> > announce any info for the wireless ports.
> >
> > Thanks in advance.
> > Lonnie
> >
> >
> > --
> > 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/c0943c94/attachment-0001.html>

More information about the Olsr-users mailing list