From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.s-osg.org ([54.187.51.154]:59240 "EHLO lists.s-osg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753391AbcC3IyW (ORCPT ); Wed, 30 Mar 2016 04:54:22 -0400 Subject: Re: 802.15.4G support? References: <20160228140659.GA17980@omega> <28981.1457015214@obiwan.sandelman.ca> <20160304083528.GA1525@omega> <24416.1457106776@obiwan.sandelman.ca> <20160304163749.GA21798@omega> <15462.1457122604@obiwan.sandelman.ca> <56E6D9F6.70308@osg.samsung.com> <25857.1457997112@obiwan.sandelman.ca> From: Stefan Schmidt Message-ID: <56FB943B.3030105@osg.samsung.com> Date: Wed, 30 Mar 2016 10:54:19 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-wpan-owner@vger.kernel.org List-ID: To: Remi Philippe , Michael Richardson Cc: Alexander Aring , linux-wpan@vger.kernel.org Hello. On 15/03/16 06:19, Remi Philippe wrote: > On Tue, Mar 15, 2016 at 3:11 AM, Michael Richardson wrote: >> Stefan Schmidt wrote: >> > 2) If the 802.15.4g node uses a SUN PHY with a 2047 byte MTU we can run into >> > trouble with normal nodes only able to handle 127. So far there is nothing >> > specified to handle this case. Michael is proposing to use 6lo ND for this >> > and record the MTU value for this neighbour in the l2 nd cache. Something >> > that would certainly work but would need specing and implementing. I see this >> > as a mid term goal we want to have. Anyone going to work on this? >> >> It's not even clear to me that ND can do this. >> I still propose that we want to have a space in the l2 or l3 ND cache for >> this info. It could well go in the L3 cache because it is really a statement >> about how the 6lowpan layer should fragment. >> >> > 3) Until 2) is done I would suggest we add a config option "802.15.4g with >> > SUN PHY" which will change the hardcoded MTU from 127 to 2047 and will thus >> > only work for a 15.g with SUN PHY only network. No interop as we have no way >> > of knowing. The option would be disabled by default and the help text needs >> > to mention the drawbacks. Once we have 2) in place we can remove this. >> >> Couldn't we use "ifconfig blah0 mtu 2047"? > Maybe we should do both, have a flag to specify the PHY type as the > PHY header is slightly different in15.4g MR-FSK to support for mode > switch, data whitening... it needs to support 2 octets header (page 52 > of the 802.15.4g-2012 spec) it can also lock the max MTU supported for > the media. And allow to change the MTU from command line. > Did you move on with this? If you ahve any patches let us know. We are happily going to review them. regards Stefan Schmidt