linux-wpan.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Butsch <Mark.Butsch@myfuelmaster.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: "linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>
Subject: RE: things not working - newbie questions
Date: Fri, 9 Apr 2021 13:29:15 +0000	[thread overview]
Message-ID: <SN6PR01MB3648AD0120B58D72E5B0C00F87739@SN6PR01MB3648.prod.exchangelabs.com> (raw)
In-Reply-To: <CAB_54W7K7ir+CLxMkXGMYbxuvDEEJD5vNW2arbLLiaSKrGtbLg@mail.gmail.com>

Hello,

I ran the bash script you referenced, but was unsure of how to test.

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.

Thanks,
Mark

> -----Original Message-----
> From: Alexander Aring <alex.aring@gmail.com>
> Sent: Thursday, April 8, 2021 12:47 PM
> To: Mark Butsch <Mark.Butsch@myfuelmaster.com>
> Cc: linux-wpan@vger.kernel.org
> Subject: Re: things not working - newbie questions
> 
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
> 
> 
> Hi,
> 
> On Thu, 8 Apr 2021 at 09:59, Mark Butsch
> <Mark.Butsch@myfuelmaster.com> wrote:
> ...
> >
> > Understood. Probably best to focus on resolving the wpan level first
> >
> 
> You can try to use some virtual hardware driver to check if there are no
> setting failures whatever you are doing.
> 
> Load mac802154_hwsim. _Maybe_ it's required to move it into another
> namespace (for ip sometimes yes).
> It will register two phys (by default) who should be able to receive to each
> other, see [0] for an example.
> 
> - Alex
> 
> [0]
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith
> ub.com%2Flinux-
> wpan%2Frpld%2Fblob%2Fnonstoring_mode%2Ftest%2Fns_setup_simple&a
> mp;data=04%7C01%7CMark.Butsch%40myfuelmaster.com%7C855fe6084169
> 4ab3ebcf08d8faadf3f9%7Cdd4cdb5b3a504947bce6dd41ce3544d6%7C1%7C0
> %7C637534972318591913%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjA
> wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;s
> data=5MCmuyVwxZn7lC019oJ3689u6%2BzKt4Lods%2BEa9q3BAQ%3D&amp;r
> eserved=0

  reply	other threads:[~2021-04-09 13:29 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 [this message]
2021-04-09 14:27     ` Alexander Aring
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=SN6PR01MB3648AD0120B58D72E5B0C00F87739@SN6PR01MB3648.prod.exchangelabs.com \
    --to=mark.butsch@myfuelmaster.com \
    --cc=alex.aring@gmail.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).