Date: Fri, 23 Mar 2012 19:13:46 +0100 From: Bernhard Schmidt <bschmidt@freebsd.org> To: Monthadar Al Jaberi <monthadar@gmail.com> Cc: freebsd-net@freebsd.org, Adrian Chadd <adrian@freebsd.org> Subject: Re: ifconfig meshforward command bug Message-ID: <201203231913.46980.bschmidt@freebsd.org> In-Reply-To: <CA%2BsBSoJaMOH9sk9Q3XatqkaZ8rukAGmZ9ycadgaYu%2BfwMFhjsQ@mail.gmail.com> References: <CA%2BsBSoJaxxRRsUqmpN6k8q6M_SZ_605ip6auN44k5BQ7a_XOtQ@mail.gmail.com> <CAJ-VmomvyQO0TTT1F5LbVbQX7nfo-X6NCCfJ75ZPrxhunHWfDQ@mail.gmail.com> <CA%2BsBSoJaMOH9sk9Q3XatqkaZ8rukAGmZ9ycadgaYu%2BfwMFhjsQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 23 March 2012 10:11:07 Monthadar Al Jaberi wrote:
> On Thu, Mar 22, 2012 at 10:23 PM, Adrian Chadd <adrian@freebsd.org> 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
Correct, and committed, thanks!
--
Bernhard
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201203231913.46980.bschmidt>