Hi Marcel, On Wed, Apr 18, 2012 at 04:29:55PM +0200, Marcel Holtmann wrote: > > > > > > If we create virtual interface then netdev is allocated and we can handle > > > > > > it with common tools. > > > > > > > > > > what common tools do you wanna use here. We actually do not wanna have > > > > > them show up as netdev devices at all. AMP connections don't have IP > > > > > addresses or anything else for that matter. > > > > > > > > I might want to set up MAC address. Otherwise I might not need netdev. I > > > > feel that I need it for interface separation. > > > > > > what MAC address? And where do you get this MAC address from? AMP > > > controllers do not have MAC addresses. > > > > I assume I need some address to send/receive data over wireless. > > from a Bluetooth point, we do not have to deal with the MAC address. > When looking at the mac80211 part, I do not know. However even then, > that address should come from the driver and not from userspace. The MAC address coming from driver might be already used in default wireless interface. I am not very familiar with wireless devices, maybe they have pool of MAC addresses we might choose from ... My point here: we create virtual interface and separate it from other wireless interfaces => hence we do not need to worry (much) about concurrency between wireless interfaces. Those interfaces need to have separate MAC addresses assigned if I understand virtual interfaces concept right. Best regards Andrei Emeltchenko -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
