[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK-6q+h7497czku9rf9E4E=up5k5gm_NT0agPU2bUZr4ADKioQ@mail.gmail.com>
Date: Thu, 16 Jun 2022 09:00:08 -0400
From: Alexander Aring <aahringo@...hat.com>
To: Stefan Schmidt <stefan@...enfreihafen.org>
Cc: linux-wpan - ML <linux-wpan@...r.kernel.org>,
linux-bluetooth@...r.kernel.org,
Network Development <netdev@...r.kernel.org>
Subject: Re: 6lowpan netlink
Hi,
On Thu, Jun 16, 2022 at 3:57 AM Stefan Schmidt
<stefan@...enfreihafen.org> wrote:
>
> Hello Alex.
>
> On 13.06.22 05:44, Alexander Aring wrote:
> > Hi all,
> >
> > I want to spread around that I started to work on some overdue
> > implementation, a netlink 6lowpan configuration interface, because
> > rtnetlink is not enough... it's for configuring very specific 6lowpan
> > device settings.
>
> Great, looking forward to it!
I would like to trigger a discussion about rtnetlink or generic. I can
put a nested rtnetlink for some device specific settings but then the
whole iproute2 (as it's currently is) would maintain a specific
6lowpan setting which maybe the user never wants...
I think we should follow this way when there is a strict ipv6 device
specific setting e.g. l2 neighbor information in ipv6 ndisc.
- Alex
Powered by blists - more mailing lists