netdev
[Top] [All Lists]

Re: rtnetlink interface state monitoring problems.

To: jamal <hadi@xxxxxxxxxx>, David Woodhouse <dwmw2@xxxxxxxxxxxxx>
Subject: Re: rtnetlink interface state monitoring problems.
From: "Maksim (Max) Krasnyanskiy" <maxk@xxxxxxxxxxxx>
Date: Wed, 23 Oct 2002 12:41:15 -0700
Cc: <linux-kernel@xxxxxxxxxxxxxxx>, <netdev@xxxxxxxxxxx>
In-reply-to: <Pine.GSO.4.30.0210222055170.24323-100000@xxxxxxxxxxxxxxxx>
References: <24818.1035226670@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
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


<Prev in Thread] Current Thread [Next in Thread>