[Olsr-users] ignore whether interface is wireless
Tue May 16 08:22:20 CEST 2017
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.
On Thu, May 4, 2017 at 6:08 PM, Lonnie Nunweiler
> 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.
> 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 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
>> 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
>> output indicates a problem or not.
> Olsr-users mailing list
More information about the Olsr-users