<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.linux.network.zigbee.devel">
    <title>gmane.linux.network.zigbee.devel</title>
    <link>http://blog.gmane.org/gmane.linux.network.zigbee.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1099"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1091"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1090"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1089"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1087"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1082"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1076"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1072"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1070"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1058"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1056"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1055"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1051"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1046"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1044"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1042"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1039"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1038"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1035"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1032"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1099">
    <title>Results of a small experiment: improve serialdriver latency by increasing the baud rate (with econotags)</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1099</link>
    <description>&lt;pre&gt;Good afternoon,

By default, the Econotag and izattach (part of the linux-zigbee 
userspace tools) expects the communications to run at 115200 bps. I 
wanted to know of it was affecting the performances, so I tried 
different values (by recompiling the firmware and the tools 
accordingly). I was mainly interested in reducing latency, this is why I 
exclusively used ping6 for my tests, but I guess the throughput should 
improve as well.

Here is the average round-trip time reported by ping6 between two 
nodes:
- at 115200 bps: ~ 400ms
- at 921600 bps: ~ 20ms (yes , 20 times faster)
- at 1843200 bps (maximum baudrate supported by the econotag): ~ 20 ms 
(same number as above)

As a side note, 1843200 bps is not a "standard" baud rate supported by 
the Linux kernel, which make it more complex to set on the software 
side. Given that there is not performance gain compared to 921600 bps, 
there seem to be no benefit in using this baud rate (but I might be 
wrong).

I do not believe my changes should make it to th&lt;/pre&gt;</description>
    <dc:creator>Tony Cheneau</dc:creator>
    <dc:date>2012-05-25T18:13:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1091">
    <title>Using a device driver for Linux-Zigbee</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1091</link>
    <description>&lt;pre&gt;Hi all,

I'm an early tester of linux-zigbee implementation. I was, until now, playing with "Serial" driver and having quite success to use it.

Is there any tutorial in the way that a driver like CC2420 or RF231 would be used on the user side.

I mean once the modules are loaded, what should be the next action from user side to really create, test, use the corresponding interface ... ? As with serial we could use izattach , iz, ip ... to manage the wpanx interface.

For now I've compiled the modules I could "modprobe" them, but except seeing them correctly with "lsmod", I do not see any new wpan-phy interface or other ? Event more after adding some debug "printk" I saw that the "probe" function was never called after registering ?

In advance thanks for your tips

-----------------------------------------------------------------------------------------
Pierre-emmanuel

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will co&lt;/pre&gt;</description>
    <dc:creator>Pierre-Emmanuel Goudet</dc:creator>
    <dc:date>2012-05-23T14:05:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1090">
    <title>Is 6lowpan fragmentation working?</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1090</link>
    <description>&lt;pre&gt;Hello,

I'm currently playing with the 6lowpan code and was wondering if the 
fragmentation support is supposed to be operational. The reason I ask is 
because when my packets grow too big (when fragmentation should kick 
in), my communications stop working.
I sniffed the traffic with Wireshark, and found out the first fragment 
(FRAG1) is always 25 bytes long and does not contain any payload. A 
quick look at the code seems to confirm that the first fragment carries 
no payload (see lowpan_skb_fragmentation()). I fail to see where RFC 
4944 indicates that the first fragment should be empty (and I fail to 
see what would be the benefit of this behavior anyway). So, is that the 
intended behavior? Did I miss something?

Either way, I'll look more into it, maybe this is only specific to my 
system (I ported the serial driver and applied some patches to it, so 
the packets might be mangled somewhere else).

Thank you in advance.

Regards,
Tony


------------------------------------------------------------------&lt;/pre&gt;</description>
    <dc:creator>Tony Cheneau</dc:creator>
    <dc:date>2012-05-22T21:42:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1089">
    <title>Bug in 6lowpan when uncompressing UDP datagram</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1089</link>
    <description>&lt;pre&gt;Hello again,

When running some connectivity tests, I discovered that UDP 
communication would not work between my nodes. Looking at the various 
printk() in the kernel, I found out that the IPv6 next header field is 
not set (set to 0) upon decompression and thus prevented correct 
processing of the decompressed packet at the upper layer (IPv6 layer).
When the next header is UDP, IPHC next header compression applies (as 
defined in Section 4.1 of RFC6282). The compression code in 6lowpan.c 
seems to behave correctly. However, upon decompression code (in 
lowpan_process_data()) fails to properly restore/set the next header 
field.

I attached a (very small) patch for this issue to this mail. It works 
in my configuration and enables the two nodes to communicate. I do not 
believe it will introduce any side-effects.

Regards,
Tony------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
thr&lt;/pre&gt;</description>
    <dc:creator>Tony Cheneau</dc:creator>
    <dc:date>2012-05-21T18:50:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1087">
    <title>Bug in 6lowpan 16-bit short address detectioncode</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1087</link>
    <description>&lt;pre&gt;Hello,

Last week, I was analyzing some 6lowpan packet with Wireshark and got 
notified by the tool that the checksum (TCP, UDP or ICMPv6) was wrong. 
Some investigations showed me that this issue has been discussed and 
solved in Contiki, as pointed out in the following thread:
http://comments.gmane.org/gmane.os.contiki.devel/7053

In my case, the issue was triggered by the format of the address I 
assigned to my nodes. They were assigned with addresses fe80::1 and 
fe80::2 and the 6lowpan code wrongly interpreted them as being 16-bit 
short address mapped an EUI-64 address (although the ff:fe part was 
missing).

It turns out that the lowpan_is_iid_16_bit_compressable macro in 
net/ieee802154/6lowpan.h is not correct and does not behave according to 
RFC6282. I attached a patch that intend to correct this behavior.

Regards,
Tony
From 84a884346b175d2c2890249d122e2f34735d433a Mon Sep 17 00:00:00 2001
From: Tony Cheneau &amp;lt;tony.cheneau&amp;lt; at &amp;gt;amnesiak.org&amp;gt;
Date: Thu, 17 May 2012 17:13:06 -0400
Subject: [PATCH 1/1] lo&lt;/pre&gt;</description>
    <dc:creator>Tony Cheneau</dc:creator>
    <dc:date>2012-05-21T15:27:30</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1082">
    <title>6lowpan Contiki fixes</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1082</link>
    <description>&lt;pre&gt;Hi Jon,

I want to sync Linux 6lowpan implementation with Contiki one, so how
can I derive latest 6lowpan fixes?
Do you have any tracking system or may be just a list with bugs were fixed?

Or 'git log' must be my favorite tool? :-)

Thanks,
Alex

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Alexander Smirnov</dc:creator>
    <dc:date>2012-05-14T12:21:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1076">
    <title>Bug when setting the hop limit in 6lowpan.c</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1076</link>
    <description>&lt;pre&gt;Hello,

I'm reading the 6lowpan.c file and I find the following code very odd. 
I believe a bug lies in it. I cannot test at the moment because the 
serial driver I plan on using does not work with the 6lowpan stack.

In lowpan_header_create(), there is the following switch (around line 
495):

I believe the code in the default block should be:

Can you confirm this is indeed a bug?

Regards,
Tony


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Tony Cheneau</dc:creator>
    <dc:date>2012-04-26T21:46:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1072">
    <title>[PATCH net-next 0/2][6lowpan] codeimprovements and refactorings</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1072</link>
    <description>&lt;pre&gt;The following patches contains 6lowpan code improvements.

With best regards,
Alex

8&amp;lt;--

The following changes since commit b89f01c8dab2b2d07729e1e6525272568bca54e0:

  6lowpan: add missing spin_lock_init() (2012-04-26 11:35:28 +0400)

are available in the git repository at:
  6lowpan_dev ..BRANCH.NOT.VERIFIED..

Alexander Smirnov (2):
      6lowpan: move frame allocation code to a separate function
      6lowpan: duplicate definition of IEEE802154_ALEN

 net/ieee802154/6lowpan.c |   85 +++++++++++++++++++++++++++-------------------
 net/ieee802154/6lowpan.h |    3 --
 2 files changed, 50 insertions(+), 38 deletions(-)

From: Alexander Smirnov &amp;lt;alex.bluesman.smirnov-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
Subject: [PATCH net-next 0/2][6lowpan] code improvements and refactorings
In-Reply-To: 


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how &lt;/pre&gt;</description>
    <dc:creator>Alexander Smirnov</dc:creator>
    <dc:date>2012-04-26T09:35:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1070">
    <title>[PATCH net 0/3][6lowpan] fixes for 6lowpan</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1070</link>
    <description>&lt;pre&gt;The following patch set contains several fixes for the 6lowpan holes which lead
to unpredictable module state.

With best regards,
Alex

8&amp;lt;--

The following changes since commit 872f24dbc604ef585ea7eec73020dcdfaffd1956:

  tipc: remove inline instances from C source files. (2012-04-24 00:41:03 -0400)

are available in the git repository at:
  6lowpan_dev ..BRANCH.NOT.VERIFIED..

Alexander Smirnov (3):
      6lowpan: fix segmentation fault caused by mlme request
      6lowpan: clean up fragments list if module unloaded
      6lowpan: add missing spin_lock_init()

 net/ieee802154/6lowpan.c |   40 ++++++++++++++++++++++++++++++++++++++--
 1 files changed, 38 insertions(+), 2 deletions(-)

From: Alexander Smirnov &amp;lt;alex.bluesman.smirnov-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
Subject: [PATCH net 0/3][6lowpan] fixes for 6lowpan
In-Reply-To: 


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's securit&lt;/pre&gt;</description>
    <dc:creator>Alexander Smirnov</dc:creator>
    <dc:date>2012-04-26T09:24:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1058">
    <title>iz list command not working correctly when alowpan0 interface exists</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1058</link>
    <description>&lt;pre&gt;Hello,

I noted that iz list never returns the proper result (or any result) 
when 6lowpan is loaded and a lowpan0 interface exists. This is true for 
the Linus' git tree (at least in 
rev:0034102808e0dbbf3a2394b82b1bb40b5778de9e, but I haven't seen any 
changes in the more recent revisions).

Here are the steps to reproduce the "bug":

I hooked a debugger to the kernel. The problem lies in the 
ieee802154_dump_iface() function, at the line 262:

Here, function ieee802154_mlme_ops(dev) always returns NULL, because 
the 6lowpan module does not register dev-&amp;gt;ml_priv (and set 
ARPHRD_IEEE802154 as dev-&amp;gt;type value).

Maybe this is not the proper list to report the bug (given that the 
6lowpan code is now part of the mainstream kernel). In that case, please 
redirect me to the proper mailing list.

Please let me know if you need more details.

Regards,
Tony


------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know..&lt;/pre&gt;</description>
    <dc:creator>Tony Cheneau</dc:creator>
    <dc:date>2012-04-23T19:51:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1056">
    <title>[PATCH v1] ieee802154: MRF24J40 driver</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1056</link>
    <description>&lt;pre&gt;Driver for the Microchip MRF24J40 802.15.4 WPAN module.

---

This is a first pass. All the places marked TODO contain things which I
think need to be fixed before merge. Some of these contain questions for
the Linux-Zigbee team. All comments appreciated.

I still plan change the structure of the SPI read functions to return an
error code.
---
 drivers/ieee802154/Kconfig    |    1 +
 drivers/ieee802154/mrf24j40.c |  747 +++++++++++++++++++++++++++++++++++++++++
 2 files changed, 748 insertions(+), 0 deletions(-)
 create mode 100644 drivers/ieee802154/mrf24j40.c

diff --git a/drivers/ieee802154/Kconfig b/drivers/ieee802154/Kconfig
index a9a6145..5703e7a 100644
--- a/drivers/ieee802154/Kconfig
+++ b/drivers/ieee802154/Kconfig
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -20,6 +20,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; config IEEE802154_FAKEHARD
           This driver can also be built as a module. To do so say M here.
   The module will be called 'fakehard'.
 
+&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt; HEAD
 config IEEE802154_FAKELB
 depends on IEEE802154_DRIVERS &amp;amp;&amp;amp; MAC802154
 tristate "Fake LR-WPAN driver with sev&lt;/pre&gt;</description>
    <dc:creator>Alan Ott</dc:creator>
    <dc:date>2012-04-23T04:34:33</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1055">
    <title>Unreachable code in serial.c (bug?)</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1055</link>
    <description>&lt;pre&gt;Hello,

I was reading the drivers/ieee802154/serial.c file (in the devel 
branch) and found the following code to be unreachable in function 
ieee802154_tty_open(), near line 889:

I believe the call to ieee802154_unregister_device() should be placed 
after the out_free label (or else, it is never reached). Can you 
confirm?

Regards,
Tony


------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
&lt;/pre&gt;</description>
    <dc:creator>Tony Cheneau</dc:creator>
    <dc:date>2012-04-20T21:10:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1051">
    <title>Kernel freezes during transmitting via 6lowpan</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1051</link>
    <description>&lt;pre&gt;I'm trying to use 6lowpan between two avr32 boards. On each board there 
are two at86rf231 sharing one IRQ.
I have patched at86rf230 and mac802154 into the mainline kernel 3.3.1.
The board setup code is the following:

static struct at86rf230_platform_data at86rf230_info_a =
     {
         .rstn         = -1,
         .slp_tr       = GPIO_PIN_PB(10),
         .dig2         = -1,
         .reset       = NULL,
         .reset_data    = NULL,
     };

static struct at86rf230_platform_data at86rf230_info_b =
     {
         .rstn         = -1,
         .slp_tr     = GPIO_PIN_PB(11),
         .dig2         = -1,
         .reset        = NULL,
         .reset_data    = NULL,
     };



static struct spi_board_info spi0_board_info[] __initdata = {

     {
         .modalias       = "at86rf230",
         .max_speed_hz   = 1000000,
         .irq        = AT32_EXTINT(1),
         .chip_select       = 2,
         .mode             = SPI_MODE_0,
         .platform_data  = &amp;amp;at86rf230_info_a,

     },

     {
         .m&lt;/pre&gt;</description>
    <dc:creator>Thomas Fechner</dc:creator>
    <dc:date>2012-04-11T13:49:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1046">
    <title>6lowpan in Ethernet packets</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1046</link>
    <description>&lt;pre&gt;Is there some simple way to hook the 6lowpan code up to the Ethernet
interface (private Ethertype maybe)? That would make an easy way to
test things on multiple machines (or VMs) without needing 802.15.4
radios.

&lt;/pre&gt;</description>
    <dc:creator>jonsmirl-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2012-04-09T19:28:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1044">
    <title>[SPAM] Status of the 6LoWPAN module in thezigbee-linux kernel tree (devel branch)</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1044</link>
    <description>&lt;pre&gt;Good afternoon,

I'm still trying to figure out if I have the latest version of the 
6LowPAN module. I'm currently using the devel branch of the Linux Zigbee 
kernel (rev: 9155ba3a1c13ba, slightly patched the autofs4 files so that 
it compiles) and I did not managed to get the 6LoWPAN part working 
(izchat works great).

It is crashing any of the two testbed computers each time I try to set 
up a 6LoWPAN network (the crash message on the console seems to be 
changing all the time and does not point toward any error in the 802154 
or 6LoWPAN subsystem, but I'll investigate it further if needed). I've 
been using the serial driver (with an econotag) and the fakehard driver, 
both yield the same outcome: the system hangs.

Here is how I reproduce the crash:

At this point (ifconfig lowpan0 up), the system stops functioning and 
the SSH access is frozen. Perhaps there is a step that I'm missing, I do 
not know. But I start wondering if I am the only one experiencing this 
issue.

Please let me know if you need m&lt;/pre&gt;</description>
    <dc:creator>Tony Cheneau</dc:creator>
    <dc:date>2012-04-09T19:05:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1042">
    <title>[PATCH] izoordinator: Fixes to error handling</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1042</link>
    <description>&lt;pre&gt;Some of the error handling was checking for != 0 on functions which returned
positive values on success.

Someone should have a look at the last one. I'm not sure what it was
supposed to do, since it failed every single time.

Signed-off-by: Alan Ott &amp;lt;alan-yzvJWuRpmD1zbRFIqnYvSA&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
---
 src/coordinator.c |    8 +++++---
 1 files changed, 5 insertions(+), 3 deletions(-)

diff --git a/src/coordinator.c b/src/coordinator.c
index a09633a..fe7d092 100644
--- a/src/coordinator.c
+++ b/src/coordinator.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -94,7 +94,8 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; static int mlme_start(uint16_t short_addr, uint16_t pan, uint8_t channel, uint8_
 nla_put_u8(msg, IEEE802154_ATTR_COORD_REALIGN, 0);
 #endif
 int err = nl_send_auto_complete(nl, msg);
-log_msg_nl_perror("nl_send_auto_complete", err);
+if (err &amp;lt; 0)
+log_msg_nl_perror("nl_send_auto_complete", err);
 return 0;
 }
 
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -129,7 +130,8 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; static int coordinator_associate(struct genlmsghdr *ghdr, struct nlattr **attrs)
 
 int err = nl_send_auto_complete(nl, msg);
 
-log_msg_nl_perro&lt;/pre&gt;</description>
    <dc:creator>Alan Ott</dc:creator>
    <dc:date>2012-04-05T04:28:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1039">
    <title>Unable to compile latest git revision of thelowpan-tools</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1039</link>
    <description>&lt;pre&gt;Good afternoon folks,

I tried compiling the lowpan-tools on Fedora 15 and CentOS 6.2 systems
but I
could not pass the "./configure" step (called by autogen.sh) and I
would be
grateful if anyone could help me figure out why. I cloned the git repo
and am
using the latest version available at the time I write these lines
(revision
6d4636d57f87a14).

Here is the last lines of the output of the ./configure:

I attached the corresponding (gzip'd) config.log to this mail if it can 
help.

The libnl3, as well as the corresponding development files, are
installed on my system as shown below (output of the Fedora 15):

Note that I cannot remove libnl (version 1) because it is a dependency
for a lot of packages, but I do not believe it should cause any trouble
(as I do not have the *-devel).

I tried to modify the configure.ac file in order to remove this test. I
believe this test has very small influence on the build (presence of
the
"-lm" flag), but I'm far from being an autotool guru, so I'm not
certain. Basically,&lt;/pre&gt;</description>
    <dc:creator>Tony Cheneau</dc:creator>
    <dc:date>2012-04-04T20:53:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1038">
    <title>Linux.com Article</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1038</link>
    <description>&lt;pre&gt;FYI:

https://www.linux.com/learn/tutorials/560384-how-linux-talks-to-the-internet-of-things-a-look-at-ieee-802154

Kind regards,

&lt;/pre&gt;</description>
    <dc:creator>Christophe Aeschlimann</dc:creator>
    <dc:date>2012-04-03T15:08:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1035">
    <title>interest in "Linux wireless networking"mini-summit in Barcelona?</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1035</link>
    <description>&lt;pre&gt;Greetings,

We are planning a wireless mini-summit event in coordination with the
LinuxCon Europe 2012 in Barcelona this November.  We plan to include
Linux developers working on Bluetooth, NFC, and 802.11 networking.
I posted about it on the linux-wireless and linux-bluetooth lists
last week:

http://marc.info/?l=linux-wireless&amp;amp;m=133244480823096&amp;amp;w=2

Do you think that there would be any interest in participation from
the 802.15.4 crowd?  Would anyone like to give a talk/presentation?
Or to introduce a topic for overall discussion?

Let me know! :-)

John
&lt;/pre&gt;</description>
    <dc:creator>John W. Linville</dc:creator>
    <dc:date>2012-03-28T13:49:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1032">
    <title>Econotag Setup</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1032</link>
    <description>&lt;pre&gt;Hello,

I got an Econotag and I'm trying to get it working. The larger goal is
to get my driver for the MRF24J40 working. Starting with a supported
device it seems makes sense.

Since I don't have any kind of 802.15.4 analyzer, I'm somewhat in the
dark, and the more information I can get about the status of the network
the better. On the Econotag (and I did order it with
Linux-802.15.4-serial firmware, and it came in a bag that said "Linux"),
the website says I'm supposed to see an LED for send and receive. Is
this still true with the current firmware? If so, then I'm doing
something wrong because I don't see any indicators ever.

I do the following (using the latest linux-zigbee tools from git):
    izattach /dev/ttyUSB1   [1]
    iz listphy
    iz add wpan-phy12
    ip link set wpan0 address ca:fe:ca:fe:ca:fe:ca:fe   [2]
    ifconfig wpan0 up  [3]
    iz assoc wpan0 777 1 11 short

Doing this I'd expect at least one packet to go out, and I'd expect to
see an LED flash on the Econotag, but I don't.

I also &lt;/pre&gt;</description>
    <dc:creator>Alan Ott</dc:creator>
    <dc:date>2012-03-28T05:05:03</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.network.zigbee.devel/1030">
    <title>6lowpan code and Contiki source</title>
    <link>http://comments.gmane.org/gmane.linux.network.zigbee.devel/1030</link>
    <description>&lt;pre&gt;Is anyone watching the Contiki 6lowpan source for bug patches to the
6lowpan code?  Problems found and patched there are likely in the
linux-zigbee code too since it is derived from Contiki. Contiki has
definitely fixed multiple problems in their code.

&lt;/pre&gt;</description>
    <dc:creator>jonsmirl-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2012-03-23T13:30:28</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.linux.network.zigbee.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.linux.network.zigbee.devel</link>
  </textinput>
</rdf:RDF>

