All of lore.kernel.org
 help / color / mirror / Atom feed
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:58:53 +0200	[thread overview]
Message-ID: <56FC3E0D.7060604@osg.samsung.com> (raw)
In-Reply-To: <CALqexQV2z5wR3y8pUtWeF0eENyo3v6pdak6sm09g7LcPuQ+4cA@mail.gmail.com>

Hello.

On 30/03/16 22:49, Adika Bintang Sulaeman wrote:
>> I still don't see why you would need to do this. What did you change?
> Sorry, I think I didn't explain clearly. I forgot to set pan_id and
> short address. Now the wpan-ping works fine. I tried to create a
> server program which is based on 802.15.4 and 6LoWPAN, and I imitate
> the code from wpan-ping. I didn't mean that I literally changed the
> wpan-ping.

OK, that makes more sense now. Without the address being setup this 
would fail.

>> Its the normal IPv6 socket API of linux.
> Thank you for your explanation, Stefan Schmidt.

If you have no specific requirements for the 6LoWPAN part normal 
client/server code written for the Linux IPv6 socket API should work 
over the lowpan0 interface.

regards
Stefan Schmidt

  reply	other threads:[~2016-03-30 20:58 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
2016-03-30 20:49           ` Adika Bintang Sulaeman
2016-03-30 20:58             ` Stefan Schmidt [this message]
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=56FC3E0D.7060604@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.