From: Stefan Schmidt <stefan@osg.samsung.com>
To: Adika Bintang Sulaeman <adikabintang78@gmail.com>
Cc: Alexander Aring <alex.aring@gmail.com>,
linux-wpan@vger.kernel.org, jukka.rissanen@linux.intel.com
Subject: Re: No device found for binding socket ieee802.15.4
Date: Wed, 30 Mar 2016 22:42:32 +0200 [thread overview]
Message-ID: <56FC3A38.7030305@osg.samsung.com> (raw)
In-Reply-To: <CALqexQWw4QuPWxTDe8SdHxeOptq6TCf-O4Mq_UL-pDxqUz=h1A@mail.gmail.com>
Hello.
On 30/03/16 21:21, Adika Bintang Sulaeman wrote:
>> On 3/30/16, Stefan Schmidt <stefan@osg.samsung.com> wrote:
>> Are you actually sure you have the socket code for ieee802154 enabled in
>> your kernel build?
>> CONFIG_IEEE802154_SOCKET
>>
>> If it is not build into the kernel, are you sure the module is loaded?
>>
>> regards
>> Stefan Schmidt
>>
> Hi Stefan,
>
> Fortunately I got 802.15.4 socket work by modifying wpan-ping code.
I still don't see why you would need to do this. What did you change?
> By
> the way, does the function generate_packet(unsigned char *buf, struct
> config *conf, unsigned int seq_num) try to generate a packet which is
> not 6LoWPAN? The code set 0x00 for the dispatch header.
Yes, it is a 802.15.4 ping utility not using 6lowpan at all. Thus the
dispatch header is set to not a 6lowpan frame to avoid problems.
> Now I need an
> example of using 6LoWPAN socket API instead of creating packet
> manually. Would anyone mind sharing the code if you have implement it?
Its the normal IPv6 socket API of linux.
regards
Stefan Schmidt
next prev parent reply other threads:[~2016-03-30 20:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 15:46 No device found for binding socket ieee802.15.4 Adika Bintang Sulaeman
2016-03-29 8:37 ` Alexander Aring
2016-03-30 1:43 ` Adika Bintang Sulaeman
2016-03-30 8:29 ` Stefan Schmidt
2016-03-30 19:21 ` Adika Bintang Sulaeman
2016-03-30 20:42 ` Stefan Schmidt [this message]
2016-03-30 20:49 ` Adika Bintang Sulaeman
2016-03-30 20:58 ` Stefan Schmidt
2016-04-03 17:09 ` Adika Bintang Sulaeman
-- strict thread matches above, loose matches on Subject: below --
2016-03-28 15:21 Adika Bintang Sulaeman
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=56FC3A38.7030305@osg.samsung.com \
--to=stefan@osg.samsung.com \
--cc=adikabintang78@gmail.com \
--cc=alex.aring@gmail.com \
--cc=jukka.rissanen@linux.intel.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