On Wed, 2010-12-01 at 16:23 -0800, Javier Cardona wrote:
> +static int nl80211_join_mesh(struct sk_buff *skb, struct genl_info *info)
> +{
> + struct cfg80211_registered_device *rdev = info->user_ptr[0];
> + struct net_device *dev = info->user_ptr[1];
> + struct mesh_config cfg;
> + int err;
> +
> + /* start with default */
> + memcpy(&cfg, &default_mesh_config, sizeof(cfg));
> +
> + /* and parse other given info */
> + err = nl80211_parse_mesh_params(info, &cfg, NULL);
> + if (err)
> + return err;
>
> Only the mesh id should be mandatory for starting the mesh, and none
> of the other mesh parameters. Therefore I would change the above to:
>
> + if (info->attrs[NL80211_ATTR_MESH_PARAMS]) {
> + err = nl80211_parse_mesh_params(info, &cfg, NULL);
> + if (err)
> + return err;
> + }
Good point.
> + case NL80211_IFTYPE_MESH_POINT:
> + /* backward compat code ... */
> + if (wdev->ssid_len)
> + __cfg80211_join_mesh(rdev, dev, wdev->ssid,
> + wdev->ssid_len, NULL);
> +
>
> This doesn't quite work: when mesh interfaces are created with a mesh
> id you set wdev->ssid_len.
> Later, when the interface is brought up, the mesh won't start because
> of the last check below:
Oops, good catch.
> If you want to keep working on this we'll be happy to test it again,
> or if you want we can take it from here and finish this.
> Let me know.
I'll finish it, shouldn't be too much.
> > I just noticed that this will lose mesh parameters when you leave the
> > mesh, unlike previously where they would be kept.
>
> ...I don't think there's an issue. I'll ask around.
Ok, I'll leave it as is for now.
Regarding this I also noticed something else: there's a bug still in the
patch -- if you attempt to set mesh parameters on an interface that's
down it'll go through to mac80211, but then the parameters will just be
overwritten upon joining. Clearly, that's not desirable, but I'm not
sure whether we need the ability to update mesh parameters while the
interface isn't joined to a mesh?
johannes
--
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
