Re: Rescanning Network

[Matthew Tippett <tippettm gmail com>]

Looking deeper at the logs, I notice

Feb 15 19:39:00 localhost NetworkManager: <WARNING>^I  (): 
nm_device_wireless_process_scan_results(ath0): process_scan_results() 
returned an error.
Feb 15 19:39:00 localhost NetworkManager: process_scan_results: 
assertion `res_buf_len > 0' failed

What would cause these issues?

Regards,

Matthew

Dan Williams wrote:
> On Mon, 2006-02-13 at 21:52 -0500, Matthew Tippett wrote:
>   
> > Hi.
> >
> > I am trying to work out how to force a rescan of available networks with 
> > NetworkManager.
> >
> > NetworkManager scans and locates access points quite happily, but if I 
> > change locations without a restart, I can't seem to force a rescan to 
> > locate the new network.
> >
> > Is there any user accessable way to force a rescan?  'iwlist scan' 
> > reports the networks correctly.
> >
> > I am using NetworkManager 0.5.1 on Ubuntu Dapper.
> >     
>
> Hmm... NM uses a composite scan algorithm, which aggregates the results
> of the past 3 or so scans.  These scans could be anywhere from 20s to 2
> minutes apart.  When an access point hasn't been in one of the scans for
> about 5 mintues, its purged from the list.
>
> So, if the following is the case, then there's a bug:  if you put the
> laptop in a car, drive somewhere, take it out, and it still lists the
> same networks more than 5 minutes later.
>
> However, as noted above, it does take some time for APs to time out.
> How long are you waiting?
>
> Dan
>
>
>
>