On Mon, Jan 30, 2012 at 21:35, David Goodenough <david.goodenough@xxxxxxxxxxxxx> wrote: > On Monday 30 Jan 2012, Goldenshtein, Victor wrote: >> On Thu, Jan 26, 2012 at 9:27 PM, David Goodenough >> >> <david.goodenough@xxxxxxxxxxxxx> wrote: >> > As I understand it hostapd is not involved in mesh (802.11s) networks, >> > so how does this integrate there? As I understand it 802.11s is entirely >> > done in the kernel. >> >> At this point we don't have any plans to extend DFS support to mesh >> networks. > That is fine, and obviously your choice. My point is simply that provision > so that someone else can add it would be sensible, and in particular to > assume that anything that could have mesh support would have a userland > component kind of locks it out as I understand 802.11s support at the > moment. I understand that using *secure* mesh requires a userspace component: http://o11s.org/trac/wiki/HOWTO Arguably there's no reason why a separate userspace component couldn't handle DFS for mesh interfaces. A project for the future could be to split it out of hostapd so it can be re-used for interfaces that aren't managed by hostapd. Thanks, -- Julian Calaby Email: julian.calaby@xxxxxxxxx Profile: http://www.google.com/profiles/julian.calaby/ .Plan: http://sites.google.com/site/juliancalaby/ -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
