Skip to content

Weird APs have single integer Quality instead of x/100, which network.py barfs on #198

@darryllee

Description

@darryllee

So in the attached iwlist.out file, you'll see one of my neighbors APs (grr, crappy AT&T router) has a Quality of 40, instead of the expected 72/100 or 48/100.

Apparently network.py never expected such lame access points, but instead of just setting Quality to 12, it falls through, and it gets set to your default of '', which then breaks the sortNetworks function, which really wants to find a slash and do some division.

I wrote a workaround: #197

But I think it'd be better to figure out why it's not able to get the single integer Quality from these lame APs (I'm not seeing any other places where it's looking for a / or a 100), but maybe this will help somebody who's also running into this problem.

Also, I'm using a super-cheap Sabrent dongle, in case that matters. But the iwlist scan runs fine on it, so I think it's these weird APs that is throwing things off.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions