Messages in this thread | | | Date | Wed, 23 Oct 2002 12:41:15 -0700 | From | "Maksim (Max) Krasnyanskiy" <> | Subject | Re: rtnetlink interface state monitoring problems. |
| |
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/
| |