From owner-freebsd-net@FreeBSD.ORG Fri Mar 23 09:11:09 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A80AE106566B; Fri, 23 Mar 2012 09:11:09 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id CEB458FC14; Fri, 23 Mar 2012 09:11:08 +0000 (UTC) Received: by wern13 with SMTP id n13so3316063wer.13 for ; Fri, 23 Mar 2012 02:11:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9zhuI5P0wRBsh1g9bpAWfQvjrYcCse5PjCfTynTxgS8=; b=UgdMLVbYcTNG3lAo2DnRzQOWXZy20eUo3BZA2cZ5pNI1vNo7yOf071htfG3sUFlsey V3MYly+yORcR41UO6ZwvddMs26DkLE4Qrunn23pLGgfLwEXyDKMC/LGOB3joJvhF3y7x SC8b9J4pl6g+O2isS3Z8tWRq23MuRXkCLOj7Zk4EQKvnm1wGz0YavSjMJzkghofq1CpD d9oOy0A+j754sUu8Ld9NLjxq/lOACT5MlRJknOgy9Fz5vKQHSPw5e4GiwahJ9HkV5TFu UhjzyK6pb64h3Cn1lkzZKlYvjykS5DdH0IqQQJY2XUzwvAph3+/rEHlIRfcCF0XOms1y rUUw== MIME-Version: 1.0 Received: by 10.180.85.70 with SMTP id f6mr4766134wiz.5.1332493867449; Fri, 23 Mar 2012 02:11:07 -0700 (PDT) Received: by 10.223.110.138 with HTTP; Fri, 23 Mar 2012 02:11:07 -0700 (PDT) In-Reply-To: References: <201203222032.20699.bschmidt@freebsd.org> Date: Fri, 23 Mar 2012 10:11:07 +0100 Message-ID: From: Monthadar Al Jaberi To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org, Bernhard Schmidt Subject: Re: ifconfig meshforward command bug X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2012 09:11:09 -0000 On Thu, Mar 22, 2012 at 10:23 PM, Adrian Chadd wrote: > I've fixed the one that Monthadar has submitted. > > Monthadar, would you mind reviewing the rest of the mesh commands and > see which others need fixing? from what I can see the bug is for flags that we can either turn on or off. Another one I found, static DECL_CMD_FUNC(set80211meshpeering, val, d) { - set80211(s, IEEE80211_IOC_MESH_AP, atoi(val), 0, NULL); + set80211(s, IEEE80211_IOC_MESH_AP, d, 0, NULL); I took a quick look and think this is last one > > > Adrian thnx -- Monthadar Al Jaberi