On Thu, Mar 7, 2019 at 11:11 PM Jaap Keuter wrote:
>
> Hi Richard,
>
> It’s not ideal, but not unheard of, so I don’t see why it can’t be done here.
>
> Thanks,
> Jaap
>
> > On 8 Mar 2019, at 04:32, Richard Sharpe wrote:
> >
> > Hi folks,
> >
> > One of the other specs, IEEE1905 refers to the rea
There is no a packet-ieee80211.h ? for extern ?
On Fri, Mar 8, 2019 at 8:11 AM Jaap Keuter wrote:
> Hi Richard,
>
> It’s not ideal, but not unheard of, so I don’t see why it can’t be done
> here.
>
> Thanks,
> Jaap
>
> > On 8 Mar 2019, at 04:32, Richard Sharpe
> wrote:
> >
> > Hi folks,
> >
> >
Hi Richard,
It’s not ideal, but not unheard of, so I don’t see why it can’t be done here.
Thanks,
Jaap
> On 8 Mar 2019, at 04:32, Richard Sharpe wrote:
>
> Hi folks,
>
> One of the other specs, IEEE1905 refers to the reason codes defined in
> table 9-45 of IEEE802.11.
>
> The easiest way to
Hi folks,
One of the other specs, IEEE1905 refers to the reason codes defined in
table 9-45 of IEEE802.11.
The easiest way to deal with that is to make it non-static in
packet-ieee80211.c.
Does anyone know of a better way? I need to refer to it in a header field array.
--
Regards,
Richard Shar
