Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <1d51db1a-746c-db67-99ec-cfe5c5a43616@desertmonitor.com>
Date:   Thu, 11 Aug 2022 01:04:49 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.11.0
Subject: Re: 6LoWPAN (IPv6 over BLE) neighbor discovery
Content-Language: en-US
To:     Alexander Aring <aahringo@redhat.com>
Cc:     linux-wpan - ML <linux-wpan@vger.kernel.org>,
        linux-bluetooth@vger.kernel.org
References: <3a3904c4-1bf9-ef1b-3d03-b5c3e1e2f8c5@desertmonitor.com>
 <CAK-6q+gBUHaR5njKHJJnONW41duVafMA-6R8jKMtN=7M1mg6rA@mail.gmail.com>
 <f1dcf16f-938c-0768-4c88-754a0ea7c2d0@desertmonitor.com>
 <CAK-6q+hfJ=oUHx0t7ueaNxg8NVsQZ2oJZ9wzj1PoP1fhHwpMrg@mail.gmail.com>
From:   Philipp Blum <philipp-blum@desertmonitor.com>
In-Reply-To: <CAK-6q+hfJ=oUHx0t7ueaNxg8NVsQZ2oJZ9wzj1PoP1fhHwpMrg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi,

sorry, just realized I used the info@ email ^^

 > What kind of workarounds? I am curious...

The radvd workaround to distribute a PD.
Ideally I would like it to be as plug & and play as possible.
Connecting the sensors to my router and passing down the PD 
automatically. At the end of the day, not everyone is a dev.

 > Okay, if you like you could also try [0] on bluetooth networks... I
 > never did it on bluetooth. Although I think it does not make any sense
 > because it makes only sense on a mesh network and so far I understand
 > this is the difference between bluetooth 4.x vs 5.x/upwards and
 > currently there is no mesh bluetooth 6lowpan support here (but mesh
 > bluetooth on link-layer is there). It's a star topology. I guess what
 > you could try out is ndisc-proxy setup which is mostly the same but no
 > routing involved and they share the same prefix.

Btw, I am on Bluetooth 4.2. I had a hard time to even find non audio 
only Bluetooth 5.x USB sticks. Yes, it's only star topology so far. Even 
though, from my understanding, you could theoretically run a RPL network 
behind it.
There are more powerful MCUs that would be able to act as a RPL root.
Even though it probably would be better to use the linux border router 
as root. Puts less pressure on the sensor nodes.
I am not familiar with ndisc-proxy. If you could point me to some 
resources, that would be very helpful. Going to take a look into it.
Sharing the same prefix would be fine for now, since I only run it in a 
star topology anyway.
RPL should be, from my understanding, also work on BLE. RIOT allows 
three concurrent connections for BLE, as I remember.

I don't really understand why rpld only works in a mesh network.
When it runs on 6LoWPAN, it should also run on BLE, or am I missing 
something?

best regards
Philipp