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: Mon, 12 Apr 2021 13:20:30 +0000 [thread overview]
Message-ID: <SN6PR01MB3648B9E70DF2898FD3BC83F587709@SN6PR01MB3648.prod.exchangelabs.com> (raw)
In-Reply-To: <CAB_54W4P4Y8q-A4x9H+zA7bf8KR=Qb7CFoxn24JuasiGSnHzTQ@mail.gmail.com>
Hello,
> -----Original Message-----
> From: Alexander Aring <alex.aring@gmail.com>
> Sent: Monday, April 12, 2021 8:29 AM
> I tried to reproduce it, I don't see any mistake and it does not work for me as
> well. However I am not an expert in af802154 socket (I never touched it so
> far) it's a very historical growing thing. Maybe Stefan can help here.
> However, I tested an IPv6 ping on my side and it worked. Just do ping6
> "fe80....%lowpan0", whereas the address is lowpan1 of course. May I have at
> the weekend time to look at it and maybe we can finally start some next
> generation socket interface or better make this one less complicated/fixing
> bugs (also some netns awareness seems to be missing, as I figured out?).
>
> I also was looking at wireshark, it was showing some data arriving.
I will try the IPv6 ping as well.
Any assistance is greatly appreciated. This is a proof of concept exercise at this point with no hard deadline.
Mark
next prev parent reply other threads:[~2021-04-12 13:20 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
2021-04-09 16:59 ` Mark Butsch
2021-04-12 12:28 ` Alexander Aring
2021-04-12 13:20 ` Mark Butsch [this message]
-- 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=SN6PR01MB3648B9E70DF2898FD3BC83F587709@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).