[Commotion-dev] Ad-hoc problems in BB: authenticated but not authorized

[Ben West]

Ah, then I guess it's helpful I remember now that a pair of UBNT
Nanostation M5's I tested would not authorize w/ each other on their adhoc
VIF, when one node ran AA and the other node ran recent revision of BB,
isn't it?  Both nodes running BB were able to authorize.

So, that point to a backward incompatibility introduced into the
wireless-testing library at some point between AA and BB.

On Wed, Apr 1, 2015 at 2:18 PM, Dan Staples <
danstaples at opentechinstitute.org> wrote:

> The encryption parameter is psk2.
>
> On 04/01/2015 03:00 PM, Ben West wrote:
> > If this is on the adhoc VIF, what is specified for the encryption
> parameter for that VIF in /etc/config/wireless?  I've found that
> encryption=psk2 works fine, but something like encryption=psk2+aes doesn't
> jive with IBSS-RSN (even tho it works fine for VIFs set to ap or sta mode.
> >
> > On Wed, Apr 1, 2015 at 1:35 PM, Dan Staples <
> danstaples at opentechinstitute.org <mailto:danstaples at opentechinstitute.org>>
> wrote:
> >
> >     I'm testing out our 1.2rc1 builds which use OpenWRT Barrier Breaker,
> and I'm running into a problem I haven't seen in a while. A TP-Link WDR4300
> I'm using is trying to connect to an existing mesh of Picostations on a
> 2.4GHz channel. It fails to join the ad-hoc network, and when I run "iw dev
> wlan0 station dump", it indicates that for every nearby peer in the network
> that is has successfully authenticated but has *failed* to authorize. For
> example:
> >
> >     Station dc:9f:db:98:72:cf (on wlan0)
> >             inactive time:  9950 ms
> >             rx bytes:       11903
> >             rx packets:     166
> >             tx bytes:       0
> >             tx packets:     0
> >             tx retries:     0
> >             tx failed:      0
> >             signal:         -49 [-58, -49] dBm
> >             signal avg:     -48 [-57, -49] dBm
> >             tx bitrate:     1.0 MBit/s
> >             rx bitrate:     1.0 MBit/s
> >             authorized:     no
> >             authenticated:  yes
> >             preamble:       long
> >             WMM/WME:        yes
> >             MFP:            no
> >             TDLS peer:      no
> >
> >     We've run into this problem before on Attitude Adjustment, but I
> remember the fixes being ath9k driver patches. Reboots fail to make a
> difference. Interestingly, this same device has been working just fine on
> the same network until recently, when I changed the channel.
> >
> >     Has anyone seen this on BB and/or have any ideas how to fix it?
> >
> >     thanks,
> >     Dan
> >
> >     --
> >     Dan Staples
> >
> >     Open Technology Institute
> >     https://commotionwireless.net
> >     OpenPGP key: http://disman.tl/pgp.asc
> >     Fingerprint: 2480 095D 4B16 436F 35AB 7305 F670 74ED BD86 43A9
> >     _______________________________________________
> >     Commotion-dev mailing list
> >     Commotion-dev at lists.chambana.net <mailto:
> Commotion-dev at lists.chambana.net>
> >     https://lists.chambana.net/mailman/listinfo/commotion-dev
> >
> >
> >
> >
> > --
> > Ben West
> > http://gowasabi.net
> > ben at gowasabi.net <mailto:ben at gowasabi.net>
> > 314-246-9434
>
> --
> Dan Staples
>
> Open Technology Institute
> https://commotionwireless.net
> OpenPGP key: http://disman.tl/pgp.asc
> Fingerprint: 2480 095D 4B16 436F 35AB 7305 F670 74ED BD86 43A9
> _______________________________________________
> Commotion-dev mailing list
> Commotion-dev at lists.chambana.net
> https://lists.chambana.net/mailman/listinfo/commotion-dev
>



-- 
Ben West
http://gowasabi.net
ben at gowasabi.net
314-246-9434
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-dev/attachments/20150401/c0648cd0/attachment-0001.html>