public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: Rob Cowart <rob.cowart@xecoenergy.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: batadv gw_mode client 0?
Date: Tue, 28 Jul 2020 07:06:06 +0200	[thread overview]
Message-ID: <1997151.jcLF785M7x@sven-edge> (raw)
In-Reply-To: <1C0C87FF-C97B-4118-BCC6-DF1163BAB05F@xecoenergy.com>

[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]

On Tuesday, 28 July 2020 01:07:09 CEST Rob Cowart wrote:
> So we have a new problem.  In BATMAN 2018 logging worked, but on BATMAN 2019 it doesn't - should I update to 2020?

What does this have to do with gw_mode client 0? At least you posted in the 
thread [0] with the subject "batadv gw_mode client 0". And you mail also has
the subject "batadv gw_mode client 0"

And please stop posting HTML messages [1]

> pi@raspberrypi:~ $ sudo batctl -v
> batctl 2019.4-1-g6046cf9 [batman-adv: 2019.4-9-g890c6748-dirty]
[...]
> pi@raspberrypi:~ $ sudo batctl log
> Error - no valid command or debug table specified: log

The log command was removed from batctl on purpose [2]. Please either get the 
data via trace-cmd [3] or build your batman-adv with DEBUGFS support and 
manually fetch the data from the deprecated log file
/sys/kernel/debug/batman_adv/log (tail -f, cat, ...).

Kind regards,
	Sven

[0] https://lists.open-mesh.org/mailman3/hyperkitty/list/b.a.t.m.a.n@lists.open-mesh.org/thread/FG4ZGHSHFHISJUKZ4XQH56ACBV4ASSSZ/
[1] https://www.open-mesh.org/projects/open-mesh/wiki/MailingList
[2] https://www.open-mesh.org/news/90
[3] https://www.open-mesh.org/projects/batman-adv/wiki/Understand-your-batman-adv-network#Logging

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2020-07-28  5:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 20:45 batadv gw_mode client 0? Rob Cowart
2020-06-16  7:01 ` Sven Eckelmann
     [not found]   ` <3DDDEFCA-57DC-43E1-8534-F816F872CD2B@xecoenergy.com>
2020-06-24 19:36     ` Sven Eckelmann
     [not found]       ` <9543BE37-DB78-4DC6-A674-F6460D5665BF@xecoenergy.com>
2020-06-24 19:54         ` Sven Eckelmann
     [not found]           ` <E3FD8A72-966A-4CBB-A036-8C0A4152983D@xecoenergy.com>
2020-06-24 20:13             ` Sven Eckelmann
2020-06-24 20:37               ` Rob Cowart
2020-06-24 21:01                 ` Mark Birss
2020-06-24 21:07                   ` Sven Eckelmann
2020-06-24 21:12                 ` Sven Eckelmann
     [not found]                   ` <1C0C87FF-C97B-4118-BCC6-DF1163BAB05F@xecoenergy.com>
2020-07-28  5:06                     ` Sven Eckelmann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1997151.jcLF785M7x@sven-edge \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=rob.cowart@xecoenergy.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox