Alex, Just wanted to mention that I am building on ubuntu -linux. (End solution is to run the openthread nodes inside containers and establish communication via fakeLB) . Wondering if it is possible to connect the PHY devices and establish communication without RIOT? Or is RIOT required to establish communication between PHY devices ? -Sujay -----Original Message----- From: Sujay G Sent: Thursday, September 20, 2018 11:37 AM To: Alexander Aring <aring@xxxxxxxxxxxx>; Michael Richardson <mcr@xxxxxxxxxxxx> Cc: linux-wpan@xxxxxxxxxxxxxxx Subject: RE: about openthread and 6lowpan Alex, I was able to port your changes to latest open thread successfully. I followed the procedure in http://www.spinics.net/lists/linux-wpan/msg04167.html to bring up Open Thread nodes but the nodes were not able to communicate with each other. Can you provide some pointers on How to connect the PHY's ? I have looked at https://github.com/RIOT-OS/RIOT/pull/5582 but not clear on how to connect the PHY's using RIOT. Can you please share procedure to establish communication between PHY using RIOT? -Sujay -----Original Message----- From: mailto:linux-wpan-owner@xxxxxxxxxxxxxxx [mailto:linux-wpan-owner@xxxxxxxxxxxxxxx] On Behalf Of Alexander Aring Sent: Monday, September 10, 2018 8:37 PM To: Michael Richardson <mailto:mcr@xxxxxxxxxxxx> Cc: Sujay G <mailto:sujay.g@xxxxxxx>; mailto:linux-wpan@xxxxxxxxxxxxxxx Subject: Re: about openthread and 6lowpan Hi, On Sun, Sep 09, 2018 at 04:49:49PM -0400, Michael Richardson wrote: > > Sujay G <mailto:sujay.g@xxxxxxx> wrote: > > I have been testing openThread on Docker. I wanted to use 6Lowpan with > > openthread. I assumed openThread would interact with wpan interfaces > > and added wpan interfaces in container namespace but it did not work. > > > Then I came across change for 6Lowpan. Comparison yielded changes in 7 > > files vs the latest openThread repositiry > > > github.com/openthread/openthread/compare/master...linux-wpan:af802154 > > Why are you asking the linux-wpan ML about openthread patches? :-) > it's okay. > Alex did some patches to make openthread work better with the virtual > interfaces... it's up to the openthread people to adopt them or not. > What is does is to run openthread as somewhat "user space stack" with limited functionality on monitor interfaces. It's good for debugging. "limited functionality" is e.g. not ack handling, every frame get to userspace... it's a pain to run productive I think. I worried, here was somebody who said "it just works for him on node interfaces", but in this case the kernel run filtering... I am worried that people using it in this way and don't know what they do. > > I manually merged the files and am trying to resolve the errors. > > > Had few queries regarding the openThread and 6Lowpan > > > Why was the project (af802154) abandoned ? Was openThread working with > > the above 6Lowpan changes ? Does the current openThread stack support > > 6Lowpan ? any configuration needs to be enabled ? or is it the right > > way to port the af802154 to current implementation of openthread ? > > You could rebase it, and maybe you have more influence with the > openthread people than we do. agree. - Alex ::DISCLAIMER:: -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
