All of
 help / color / mirror / Atom feed
From: Adika Bintang Sulaeman <>
To: Stefan Schmidt <>
Cc: Alexander Aring <>,,
Subject: Re: No device found for binding socket ieee802.15.4
Date: Mon, 4 Apr 2016 00:09:22 +0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> 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.

Hi Stefan,

I'm sorry if my question would be too stupid or shallow, I just want
to make sure because I'm really new to this.

I have run an example from [1] on client-server model using UDP and
IPv6. To run this example, on the client side I run the command:

"listener <IPv6 of another machine for lowpan interface>%lowpan0

According to [2], <IPv6 address>%<interface's name> notation means the
machine will try to communicate  to <IPv6 address> machine through the
<interface's name> interface. Hence, I basically have run
client/server program with Linux IPv6 over the lowpan0 interface.
Alexander Aring gave me a good presentation slide [3] and on page 12
it is clearly written that Linux still uses AF_INET6 for 6LoWPAN.

I just want to make sure whether my approach on making client-server
model over 6LoWPAN is right. I am not sure because I don't know
whether the IPv6 header is compressed using 6LoWPAN adaptation layer.


Best regards

  reply	other threads:[~2016-04-03 17:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-28 15:46 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
2016-04-03 17:09               ` Adika Bintang Sulaeman [this message]
  -- 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \
    --subject='Re: No device found for binding socket ieee802.15.4' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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.