Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 159723 - acess point can't be found with rt2500(script problem)
Summary: acess point can't be found with rt2500(script problem)
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] baselayout (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-02 08:17 UTC by GNUtoo
Modified: 2007-01-10 12:31 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description GNUtoo 2007-01-02 08:17:23 UTC
with the net.lo script i can't find my acess point despite of having the corect configuration in /etc/conf.d/net

but wifi-radar and RaConfig2500 can find it...

why?

simply because wifi-radar does multiple scan and net.lo only scan once(checked with rt2x00 with debuging indo in dmesg...by the way i use rt2500 not rt2x00)
Comment 1 Roy Marples (RETIRED) gentoo-dev 2007-01-03 03:33:10 UTC
At most I can make this a configuration variable

scans_ra0="5" # Do 5 scans

And it will default to 1. Would this be acceptable?
Note, this is still not a guarantee of the AP being found.
Comment 2 GNUtoo 2007-01-03 05:10:08 UTC
that is great
another option would be to scan until it find the acess point
Comment 3 GNUtoo 2007-01-03 05:18:36 UTC
(In reply to comment #2)
> that is great
> another option would be to scan until it find the acess point
> 

mabe it could also be both:
a number of max try wile it will stop when it has find the acess point
with 0=infinite
Comment 4 Roy Marples (RETIRED) gentoo-dev 2007-01-04 03:50:50 UTC
(In reply to comment #2)
> that is great
> another option would be to scan until it find the acess point

No, that is unacceptable - we must timeout.
However, the scanning operating takes a while (varies from hw to hw, but is normally 1-2 seconds at least) and there's nothing to stop you from doing

scans_eth0="999999"

which is kinda like infinite :)
Comment 5 GNUtoo 2007-01-04 12:03:53 UTC
(In reply to comment #4)
> (In reply to comment #2)
> > that is great
> > another option would be to scan until it find the acess point
> 
> No, that is unacceptable - we must timeout.
> However, the scanning operating takes a while (varies from hw to hw, but is
> normally 1-2 seconds at least) and there's nothing to stop you from doing
> 
> scans_eth0="999999"
> 
> which is kinda like infinite :)
> 
ok
Comment 6 Roy Marples (RETIRED) gentoo-dev 2007-01-10 12:31:08 UTC
This should be fixed in baselayout-1.13.0_alpha11. Re-open if you disagree.

We always do 2 scans by default, so you may not need to use any extra config options.