Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 23 Oct 2002 15:35:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 23 Oct 2002 15:35:33 -0400 Received: from ithilien.qualcomm.com ([129.46.51.59]:46830 "EHLO ithilien.qualcomm.com") by vger.kernel.org with ESMTP id ; Wed, 23 Oct 2002 15:35:33 -0400 Message-Id: <5.1.0.14.2.20021023123707.09b5b168@mail1.qualcomm.com> X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 23 Oct 2002 12:41:15 -0700 To: jamal , David Woodhouse From: "Maksim (Max) Krasnyanskiy" Subject: Re: rtnetlink interface state monitoring problems. Cc: , In-Reply-To: References: <24818.1035226670@passion.cambridge.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1059 Lines: 28 Hi Jamal, >> But Bluetooth devices are not network devices, it seems. There exists no >> current mechanism for notifying anyone of state changes. Should we invent a >> new method of notification using netlink, or should Bluetooth interfaces in >> fact be normal network devices just like IrDA devices are? >> > >I think the only time you should go netdev is when it makes sense to run IP. Totally agree. >Is there IP over bluttooth? Yep. It's called BNEP (Bluetooth Network Encapsulation Protocol) which is bascially an Ethernet emulation. That thing is the netdev of course. >Then you could take advantage of all the nice features provided by netdevices (other >than being IP devices;->). >If not, it probably time for someone to write a generic notification >scheme via netlink. Might be interesting. Max - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/