outgoing interface field
For our particular implementation of AP mode with hostapd in Linux, we are using radiotap-injection interfaces to send management frames.
Now, 802.11w (encrypted management frames) requires that those frames are encrypted, due to key management issues we need to do that in the kernel. This means we can no longer simply inject the frames, we need to know, in the kernel, which interface to search for the key, since multiple virtual AP interfaces/BSSes may be configured on a single PHY.
This requires that we have a radiotap field indicating the outgoing interface to use for such key lookups. Further uses would be to use, for data frames, the fragmentation/RTS threshold from the given interface.
I don't, off-hand, see any other OS requiring this, so I'm shopping around asking vendors if I can have part of their vendor OUI namespace (one of the sub-namespaces) for Linux, but if anybody sees value in such a field for other OSes we can also add it to the standard.
Thoughts?
johannes
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 11 lines · Johannes Berg
For our particular implementation of AP mode with hostapd in Linux, we are using radiotap-injection interfaces to send management frames.
Now, 802.11w (encrypted management frames) requires that those frames are encrypted, due to key management issues we need to do that in the kernel. This means we can no longer simply inject the frames, we need to know, in the kernel, which interface to search for the key, since multiple virtual AP interfaces/BSSes may be configured on a single PHY.
This requires that we have a radiotap field indicating the outgoing interface to use for such key lookups.
Are you injecting by sending data to a socket? I think the sockets are bound to VAPs, not to PHYs since VAPs are seen as network devices.
Besides, are you going to serve more than one VAP with one socket? I would not do it without a good reason. I think ioctl on the socket would be an easier solution, as it needs to be done once per VAP, not once per packet.
Quoted 7 lines
Further uses would be to use, for
data frames, the fragmentation/RTS threshold from the given interface.I don't, off-hand, see any other OS requiring this, so I'm shopping around asking vendors if I can have part of their vendor OUI namespace (one of the sub-namespaces) for Linux, but if anybody sees value in such a field for other OSes we can also add it to the standard.
We could probably register an official Linux OUI for that if the code is intended for Linux.
Signature · 2 lines
Regards, Pavel Roskin
Quoted 3 lines
Are you injecting by sending data to a socket? I think the sockets are bound to VAPs, not to PHYs since VAPs are seen as network devices.
Yes. The socket is bound to a _cooked monitor_ interface.
Quoted 4 lines
Besides, are you going to serve more than one VAP with one socket? I would not do it without a good reason. I think ioctl on the socket would be an easier solution, as it needs to be done once per VAP, not once per packet.
Well, yes, of course we're going to serve multiple BSSes with one socket if they're all associated to one physical interface. Why not? It makes the code much cleaner and nicer. Why do you think I need a good reason to do this? I think you need a good reason _not to_ and this isn't a good reason. Besides, ioctls suck.
Quoted 10 lines
Quoted 7 lines
Further uses would be to use, for
data frames, the fragmentation/RTS threshold from the given interface.I don't, off-hand, see any other OS requiring this, so I'm shopping around asking vendors if I can have part of their vendor OUI namespace (one of the sub-namespaces) for Linux, but if anybody sees value in such a field for other OSes we can also add it to the standard.
We could probably register an official Linux OUI for that if the code is intended for Linux.
Who'd pay for it, and why bother to pollute the OUI namespace with something we're not using elsewhere?
johannes
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 4 lines · Johannes Berg
Quoted 2 lines
Are you injecting by sending data to a socket? I think the sockets are bound to VAPs, not to PHYs since VAPs are seen as network devices.
Yes. The socket is bound to a
_cookedmonitor_interface.
Oh well, I should have guessed that. Maybe we could introduce ioctl to put socket into "wireless injection mode", in which it would accept 802.11 packets with radiotap headers regardless of the interface mode. Then the sockets could be bound to the VAPs.
Quoted 7 lines
Quoted 4 lines
Besides, are you going to serve more than one VAP with one socket? I would not do it without a good reason. I think ioctl on the socket would be an easier solution, as it needs to be done once per VAP, not once per packet.
Well, yes, of course we're going to serve multiple BSSes with one socket if they're all associated to one physical interface. Why not?
It's a cleaner approach to respect the virtual interface abstraction existing in the kernel rather than ignore it. The kernel presents separate network interfaces to the userspace.
Quoted 4 lines
It makes
the code much cleaner and nicer. Why do you think I need a good reason to do this? I think you need a good reason_notto_and this isn't a good reason. Besides, ioctls suck.
ioctls suck for global configuration. They are adequate for configuring particular sockets or file descriptors.
Besides, radiotap headers are designed to be transferable between systems. It should be possible to send frames with radiotap headers from another system, possibly with a different endianness and different wireless hardware. Encoding local data (VAP number) makes radiotap headers system-specific.
Quoted 6 lines
Quoted 1 line
We could probably register an official Linux OUI for that if the
code is
Quoted 1 line
intended for Linux.
Who'd pay for it, and why bother to pollute the OUI namespace with something we're not using elsewhere?
It's funny, we are creating the rules that exclude us, and then we are shopping around for sponsors. We need exceptions for experimental use.
Signature · 2 lines
Regards, Pavel Roskin
Quoted 10 lines · Pavel Roskin
Quoted 4 lines · Johannes Berg
Quoted 2 lines
Are you injecting by sending data to a socket? I think the sockets are bound to VAPs, not to PHYs since VAPs are seen as network devices.
Yes. The socket is bound to a
_cookedmonitor_interface.Oh well, I should have guessed that. Maybe we could introduce ioctl to put socket into "wireless injection mode", in which it would accept 802.11 packets with radiotap headers regardless of the interface mode. Then the sockets could be bound to the VAPs.
I don't want to see the kernel code for that.
Quoted 11 lines
Quoted 7 lines
Quoted 4 lines
Besides, are you going to serve more than one VAP with one socket? I would not do it without a good reason. I think ioctl on the socket would be an easier solution, as it needs to be done once per VAP, not once per packet.
Well, yes, of course we're going to serve multiple BSSes with one socket if they're all associated to one physical interface. Why not?
It's a cleaner approach to respect the virtual interface abstraction existing in the kernel rather than ignore it. The kernel presents separate network interfaces to the userspace.
Well yeah, but what point is there in having many sockets? Anyway, Jouni and I have pretty much decided on this, and you don't really get a say unless you provide clean, working code :)
Quoted 6 lines
Besides, radiotap headers are designed to be transferable between systems. It should be possible to send frames with radiotap headers from another system, possibly with a different endianness and different
wireless hardware. Encoding local data (VAP number) makes radiotap headers system-specific.
This isn't designed to be ever saved to disk, it's for communication between userspace and the kernel when running an AP. We just happen to use radiotap for that to save inventing yet another interface.
Quoted 2 lines
It's funny, we are creating the rules that exclude us, and then we are shopping around for sponsors. We need exceptions for experimental use.
Actually, I just figured out that the OUIs have a 'locally assigned' bit like MAC addresses (well I guess MAC addresses inherit it from OUIs), so we can use that and assign "experimental" OUIs to ourselves as long as they don't clash within radiotap.
johannes
A message that is not in the archive (sent off-list or not yet received): 1213906462.8967.110.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org
Quoted 10 lines · Johannes Berg
Quoted 6 lines
Besides, radiotap headers are designed to be transferable between systems. It should be possible to send frames with radiotap headers from another system, possibly with a different endianness and different
wireless hardware. Encoding local data (VAP number) makes radiotap headers system-specific.This isn't designed to be ever saved to disk, it's for communication between userspace and the kernel when running an AP. We just happen to use radiotap for that to save inventing yet another interface.
Then there is very little point in discussing it. I thought you were going to suggest some elegant addition to the standard. Piggybacking the frames with some OS and system specific data is not.
Quoted 7 lines
Quoted 2 lines
It's funny, we are creating the rules that exclude us, and then we are shopping around for sponsors. We need exceptions for experimental use.
Actually, I just figured out that the OUIs have a 'locally assigned' bit like MAC addresses (well I guess MAC addresses inherit it from OUIs), so we can use that and assign "experimental" OUIs to ourselves as long as they don't clash within radiotap.
OK, fine.
Signature · 2 lines
Regards, Pavel Roskin