[Guessnet-devel] Priority of profiles

[Leon Bogaert]

Hi Massimiliano,

I tried to reproduce the behavior. But I couldn't manage to come up with the results you experienced. Whenever there are two networks in range that match one of the rules, guessnet always picks one. But based on alphabetical order of the essid?

For example. I have two networks in range: hotspot && Tim_Online. The two rules:

iface wlan0-02_tim inet dhcp
  test wireless essid Tim_online closed
iface wlan0-03_open inet dhcp
  test wireless open

I renamed the second rule to wlan0-03_open so Tim_online should be picket first. But when I run guessnet I get this output:
  guessnet: Removing candidate wlan0-01_home
  guessnet: Removing candidate wlan0-02_tim
  guessnet: Keeping candidate wlan0-03_open

It picks the 03_ over 02_
So then I swapped the 02 & 03_

I ran the scan again:

guessnet: Removing candidate wlan0-01_home
guessnet: Keeping candidate wlan0-02_open
guessnet: Removing candidate wlan0-03_tim

And now it picks 02_ over 03_???

If the ordering is based on essid, that would not be very useful. Because (most of the times) you can't adjust the name of the essid. But you can adjust the name of your rules.

Leon

________________________________________
From: Massimiliano Masserelli [negro at interim.it]
Sent: 26 May 2008 12:52
To: guessnet-devel at lists.alioth.debian.org
Cc: Leon Bogaert
Subject: Re: [Guessnet-devel] Priority of profiles

On Tue, May 06, 2008 at 10:33:31PM +0200, Leon Bogaert wrote:

> I'm using the guessnet_0.48-1_amd64.deb package of debian. It's
> working very well, except that if there are two networks in range that
> match one of the criteria, it picks the wrong one.  On what criteria
> prioritizes the list?

Profiles list is prioritized in alphabetical order. I know it' not the
best method but hey, it's a method! :)

Problem is: in testing with your setup, I discovered a nasty bug in scan
results processing, which was causing the scan to report no success if
two or more profiles were to match. So having two networks in range
should cause guessnet to report "none" and eventually not configure the
interface. Can you confirm this behaviour?

Regards.
--
Massimiliano Masserelli
-------------------------------------------------------------------------------
Amo gli animali: hanno un buon sapore.
        -- Frank D. Fellenz (fdfellenz at ccgate.dp.beckman.com)