linux-wpan.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Mark Butsch <Mark.Butsch@myfuelmaster.com>
Cc: "linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>
Subject: Re: things not working - newbie questions
Date: Fri, 9 Apr 2021 10:27:56 -0400	[thread overview]
Message-ID: <CAB_54W4j7G53YT8G32GdM4pNET8i0v9_zkNMe=0dwdfbHvEXFg@mail.gmail.com> (raw)
In-Reply-To: <SN6PR01MB3648AD0120B58D72E5B0C00F87739@SN6PR01MB3648.prod.exchangelabs.com>

Hi,

On Fri, 9 Apr 2021 at 09:29, Mark Butsch <Mark.Butsch@myfuelmaster.com> wrote:
>
> Hello,
>
> I ran the bash script you referenced, but was unsure of how to test.
>

okay, forget that bash script please.

> I also tried using the mac802154_hwsim driver without the separate namespaces.
>
> I took it as far as creating and bringing up the wpan's and they show up in ifconfig.
>
> Then I tried using wpan-ping, but got time outs like I was seeing with the real hardware.
>
> Ifconfig shows one phy with the TX packet count increasing and the other with the RX packet count increasing like I saw with the real hardware as well.
>

please tell us all the steps which you are doing with mac802154_hwsim,
the good part of that I can type it here as exactly what you do and
then I can tell you why it's not working.

- Alex

  reply	other threads:[~2021-04-09 14:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-08 13:59 things not working - newbie questions Mark Butsch
2021-04-08 16:46 ` Alexander Aring
2021-04-09 13:29   ` Mark Butsch
2021-04-09 14:27     ` Alexander Aring [this message]
2021-04-09 16:59       ` Mark Butsch
2021-04-12 12:28         ` Alexander Aring
2021-04-12 13:20           ` Mark Butsch
  -- strict thread matches above, loose matches on Subject: below --
2021-03-23 21:14 Mark Butsch
2021-03-30  7:30 ` Stefan Schmidt

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='CAB_54W4j7G53YT8G32GdM4pNET8i0v9_zkNMe=0dwdfbHvEXFg@mail.gmail.com' \
    --to=alex.aring@gmail.com \
    --cc=Mark.Butsch@myfuelmaster.com \
    --cc=linux-wpan@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).