Re: Scannning
>> 1) why can't nm do the scan in the time between the user clicks and the menu >> is popped? > >Because scans take a non-trival amount of time on many cards. You >simply cannot block the menu being popped down for 3 or 5 seconds while >a scan is taking place. If you can't update the list while it is shown (as a gtk limitation) you can change the icon in a scaning one, so the user will understand why it waits for 5 seconds. (5 seconds? are you sure? I have ipw2200 and the scan through iwlist lasts in mess than half second) I really think that a user prefers to wait for some seconds and have a coherent list. What is the sense of an old list? Tell me what you think about it >> 2) so if I do "while echo 0; do iwlist eth1 scan; done" it is a dos, so nm >> should not interest on dos... > >Yes, but you have root and can shoot yourself in the foot with it. >People using NM don't necessarily have root. I don't need root to do iwlist eth1 scan >> 3) if you really want to consider dos, you can trigger a N-secons timeout >> after the first scan > >That's the plan. NM scans periodically, but when you drop the applet >down, NM will do a scan. If you click again, another scan will be >scheduled for 10 or 20 seconds from that point. ok it is good. ___ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Scannning
On Mon, 2007-03-19 at 15:58 +, yelo_3 wrote: > > There are essentially none, except that the 'iwlist scan' obviously > > starts a scan right away, and blocks waiting on the scan results, while > > NetworkManager schedules scans at various points in time because it's > > not a command-line tool that you explicitly invoke from a terminal. But > > the internal process is pretty much the same. > > > > Dan > > Ok so if there are no substantial differences: > 1) why can't nm do the scan in the time between the user clicks and the menu > is popped? Because scans take a non-trival amount of time on many cards. You simply cannot block the menu being popped down for 3 or 5 seconds while a scan is taking place. > 2) so if I do "while echo 0; do iwlist eth1 scan; done" it is a dos, so nm > should not interest on dos... Yes, but you have root and can shoot yourself in the foot with it. People using NM don't necessarily have root. > 3) if you really want to consider dos, you can trigger a N-secons timeout > after the first scan That's the plan. NM scans periodically, but when you drop the applet down, NM will do a scan. If you click again, another scan will be scheduled for 10 or 20 seconds from that point. Dan > 4) because the user will see results when he clicks on the applet, there is > no advantage at all >in doing scans when the applet is not used (and the user is already > connected), unless >you want to add a "new networks found" notify (but now there is no > such feature) > > > > > > > > > > > > ___ > L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: > http://it.docs.yahoo.com/nowyoucan.html > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Scannning
> There are essentially none, except that the 'iwlist scan' obviously > starts a scan right away, and blocks waiting on the scan results, while > NetworkManager schedules scans at various points in time because it's > not a command-line tool that you explicitly invoke from a terminal. But > the internal process is pretty much the same. > > Dan Ok so if there are no substantial differences: 1) why can't nm do the scan in the time between the user clicks and the menu is popped? 2) so if I do "while echo 0; do iwlist eth1 scan; done" it is a dos, so nm should not interest on dos... 3) if you really want to consider dos, you can trigger a N-secons timeout after the first scan 4) because the user will see results when he clicks on the applet, there is no advantage at all in doing scans when the applet is not used (and the user is already connected), unless you want to add a "new networks found" notify (but now there is no such feature) ___ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Scannning
On Mon, 2007-03-19 at 14:59 +, yelo_3 wrote: > > Right, that's a bug. The scan shouldn't get rescheduled a further 20 > > seconds every time the menu is dropped down, it should let the 20s > > timeout run down first. > > Dan > > In my case the scan is not done, even If I wait for the 20 seconds timeout. > > Can someone tell me the differences between how nm and iwlist scan for new > networks? There are essentially none, except that the 'iwlist scan' obviously starts a scan right away, and blocks waiting on the scan results, while NetworkManager schedules scans at various points in time because it's not a command-line tool that you explicitly invoke from a terminal. But the internal process is pretty much the same. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Scannning
> Right, that's a bug. The scan shouldn't get rescheduled a further 20 > seconds every time the menu is dropped down, it should let the 20s > timeout run down first. > Dan In my case the scan is not done, even If I wait for the 20 seconds timeout. Can someone tell me the differences between how nm and iwlist scan for new networks? ___ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Scannning
On Mon, 2007-03-19 at 10:27 -0400, Matthew Saltzman wrote: > On Mon, 19 Mar 2007, Tambet Ingo wrote: > > [...] > > There are multiple problems when trying to "fix" this behavior: > > > > * Scanning disables all other operations on card so network doesn't work at > > that time. That's the reason there is a timeout, that's the reason there > > can't be a "scan now" button (well, part of the reason anyway). We need to > > protect NM from malicious users who can write a shell script to make NM scan > > constantly (or if they're not smart enough, keep hitting that > > button/activating the menu manually). [1] > > [...] > > > > [1] I'm not sure how serious that is since any user can just deactivate all > > networking anyway. > > The idea of preventing a user from intentionally launching a DoS attack on > his own service seems strange to me. As you say, if a user wants to deny > himself a service, all he needs to do is turn it off. (If NM is intended > to manage networks on a truely multi-user system, that's different. But > that's not how I ever envisioned it. I don't use NM on my workstations > because they don't need the dynamic network management facility. I just > don't think of laptops as "real" multi-user systems.) > > Accidental self-DoS is a different issue. One thing that occurs to me is > simply not rescheduling the scan if the menu is opened within the > 20-second interval. Then a user can just reopen the menu every few > seconds and see if it's been updated. There's no way to really cancel a > scheduled scan, so what's wrong with just letting it go once scheduled? Right, that's a bug. The scan shouldn't get rescheduled a further 20 seconds every time the menu is dropped down, it should let the 20s timeout run down first. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Scannning
On Mon, 2007-03-19 at 14:48 +0200, Tambet Ingo wrote: > Here's how scanning is scheduled: > > When the nm-applet's devices menu is expanded, NetworkManager > schedules a scan to start in 20 seconds. If the menu is deactivated > and activated again within that 20 seconds, NM re-schedules the scan > after another 20 seconds. So if you keep clicking on applet with > intervals less than 20 seconds, the NM initiated scan never happens. > When the scan is actually initiated, it takes a bit time to get the > results back and it depends on wireless driver how fast/slow it is. If > the menu is still expanded, the scan results are not added to the > menu, you have to deactivate the menu and activate it again to see the > results (and a new scan is scheduled again). Right, there are bugs in the scan algorithm like this one that should get fixed, but before that we needed to determine exactly _how_ it should best get fixed, which I think we now know. We'd have problems if people wanted very short scan intervals while connected, which doesn't appear to be the case. For 0.6.x at least, I think we can get a good enough patch. Dan > There are multiple problems when trying to "fix" this behavior: > > * Scanning disables all other operations on card so network doesn't > work at that time. That's the reason there is a timeout, that's the > reason there can't be a "scan now" button (well, part of the reason > anyway). We need to protect NM from malicious users who can write a > shell script to make NM scan constantly (or if they're not smart > enough, keep hitting that button/activating the menu manually). [1] > > * The devices menu is a GtkMenu widget which means the changes made to > the menu (adding/removing menu items) while it's expanded doesn't > change it's appearance until it's shown next time. Another > difficulties are to keep the menu sorted correctly, replace the labels > of devices (there's a generic and specific variants, depending on the > number of same type devices). Nothing impossible, just requires a lot > of work and while the SVN trunk barely works at the moment, it's > doesn't make sense to work on that right now. > > [1] I'm not sure how serious that is since any user can just > deactivate all networking anyway. > > Tambet > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Scannning
On Mon, 2007-03-19 at 00:12 +, yelo_3 wrote: > It is simpler: Sorry I was not clear. I was not connected, and I was moving > around to search for the correct AP (there is only one for students) > > In this case and in the case that wireless was off, scanning is not fast > enough Ok, good. In this case, we can make NM scan more frequently quite easily, because you're not connected to anything. The problem with frequent scans is really only when you're connected. Sorry for all the misunderstanding :) We may still need to back that down somewhat, since active scanning does take battery power on a laptop, and not all drivers support passive scanning. So now that all this is sorted out, we can do a few things: 1) scan quickly after a GUI event like app menu dropdown, right now that doesn't happen quite as quickly as we'd all like 2) change the max scan timeout while disconnected to be somewhat lower Dan > - Messaggio originale - > Da: Dan Williams <[EMAIL PROTECTED]> > A: yelo_3 <[EMAIL PROTECTED]> > Cc: NetworkManager-List > Inviato: Lunedì 19 marzo 2007, 1:04:16 > Oggetto: Re: Scannning > > On Sun, 2007-03-18 at 23:45 +, yelo_3 wrote: > > The use case is when I move around, in my university! There are different > > access points in different places. > > Or simply when I decide to enable wireless and before it was disabled > > Do they have the same SSID? Doesn't NetworkManager disconnect you when > you move out of range of one SSID? When you're disconnected, NM should > scan more frequently. > > So is the case that you are _still_ in the coverage of SSID A, but you > have now moved into the area SSID B (A and B overlap), but you want to > switch off A move to B immediately when B is in range? > > Dan > > > - Messaggio originale - > > Da: Dan Williams <[EMAIL PROTECTED]> > > A: yelo_3 <[EMAIL PROTECTED]> > > Cc: NetworkManager-List > > Inviato: Lunedì 19 marzo 2007, 0:40:36 > > Oggetto: Re: Scannning > > > > On Sun, 2007-03-18 at 16:50 +, yelo_3 wrote: > > > > In my experience when I click the applet new networks begin showing up > > > > within 30 seconds. This is with an IPW2200 and IPW3945, my Atheros > > > > card sometimes takes longer. > > > > > > it is not always true, with my ipw2200 sometimes I have to wait around 2 > > > minutes > > > > What's the use-case here again? > > > > Are you suspending, going home, and waking the laptop up and the AP is > > not showing up in the menu? > > > > Or are you turning on an access point and expecting it to show up? > > > > Or are you walking from one access point coverage area to another? > > > > Or? > > > > Dan > > > > > > > > > > > > > > > > > > > > > > ___ > > L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: > > http://it.docs.yahoo.com/nowyoucan.html > > > > > > > > > > > ___ > L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: > http://it.docs.yahoo.com/nowyoucan.html > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Scannning
> Here's how scanning is scheduled: > When the nm-applet's devices menu is expanded, NetworkManager schedules a > scan to start in 20 seconds. If the menu is deactivated and activated again > within that 20 seconds, NM re-schedules the scan after another 20 seconds. I've tried to do so: boot with wireless off, login, wireless activation, click on the applet, 30 seconds of wait, another click on the applet. The result is empty, so there is a problem in this way... Anyway I didn't really understand why it is scheduled and why can't be done immediately > There are multiple problems when trying to "fix" this behavior: > * Scanning disables all other operations on card so network doesn't work at > that time. > We need to protect NM from malicious users who can write a shell script All right, I didn't know it I'm sure the user can do a script which does "iwlist eth1 scan", so this is not a nm problem oh, and if I do "iwlist eth1 scan" my network does not go down... So how is scan implemented in nm? > * The devices menu is a GtkMenu widget which means the changes made to the > menu (adding/removing menu items) while it's expanded doesn't change it's > appearance until it's shown next time. Isn't there a redraw function? I know that C APIs are very sad, but I hope there is one! ___ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Scannning
On Mon, 19 Mar 2007, Tambet Ingo wrote: > [...] > There are multiple problems when trying to "fix" this behavior: > > * Scanning disables all other operations on card so network doesn't work at > that time. That's the reason there is a timeout, that's the reason there > can't be a "scan now" button (well, part of the reason anyway). We need to > protect NM from malicious users who can write a shell script to make NM scan > constantly (or if they're not smart enough, keep hitting that > button/activating the menu manually). [1] > [...] > > [1] I'm not sure how serious that is since any user can just deactivate all > networking anyway. The idea of preventing a user from intentionally launching a DoS attack on his own service seems strange to me. As you say, if a user wants to deny himself a service, all he needs to do is turn it off. (If NM is intended to manage networks on a truely multi-user system, that's different. But that's not how I ever envisioned it. I don't use NM on my workstations because they don't need the dynamic network management facility. I just don't think of laptops as "real" multi-user systems.) Accidental self-DoS is a different issue. One thing that occurs to me is simply not rescheduling the scan if the menu is opened within the 20-second interval. Then a user can just reopen the menu every few seconds and see if it's been updated. There's no way to really cancel a scheduled scan, so what's wrong with just letting it go once scheduled? -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Scannning
Here's how scanning is scheduled: When the nm-applet's devices menu is expanded, NetworkManager schedules a scan to start in 20 seconds. If the menu is deactivated and activated again within that 20 seconds, NM re-schedules the scan after another 20 seconds. So if you keep clicking on applet with intervals less than 20 seconds, the NM initiated scan never happens. When the scan is actually initiated, it takes a bit time to get the results back and it depends on wireless driver how fast/slow it is. If the menu is still expanded, the scan results are not added to the menu, you have to deactivate the menu and activate it again to see the results (and a new scan is scheduled again). There are multiple problems when trying to "fix" this behavior: * Scanning disables all other operations on card so network doesn't work at that time. That's the reason there is a timeout, that's the reason there can't be a "scan now" button (well, part of the reason anyway). We need to protect NM from malicious users who can write a shell script to make NM scan constantly (or if they're not smart enough, keep hitting that button/activating the menu manually). [1] * The devices menu is a GtkMenu widget which means the changes made to the menu (adding/removing menu items) while it's expanded doesn't change it's appearance until it's shown next time. Another difficulties are to keep the menu sorted correctly, replace the labels of devices (there's a generic and specific variants, depending on the number of same type devices). Nothing impossible, just requires a lot of work and while the SVN trunk barely works at the moment, it's doesn't make sense to work on that right now. [1] I'm not sure how serious that is since any user can just deactivate all networking anyway. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Scannning
> Does it cost much just to set a menu (as in all Windows) that reset the > list of network available and launch a scan immediately ? The problem is different: Dan was saying that the scan is performed every time you click on the applet, although I don't really know if it is done! (at least in ubuntu feisty). Which distribution are you using? So the new button should not be needed. But I still don't understand why in our case the scan lasts in 2 minutes... What could cause this problem? ___ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Scannning
Dan, The use case, is, as many people with a laptop, to move from a location to another, and not willing to wait 2 minutes because the applet just does not scan fast enough the new networks available. Does it cost much just to set a menu (as in all Windows) that reset the list of network available and launch a scan immediately ? Thanks a lot, it would make life much easier for some of us, Joan Dan Williams wrote: > On Sun, 2007-03-18 at 16:50 +, yelo_3 wrote: > >>> In my experience when I click the applet new networks begin showing up >>> within 30 seconds. This is with an IPW2200 and IPW3945, my Atheros >>> card sometimes takes longer. >>> >> it is not always true, with my ipw2200 sometimes I have to wait around 2 >> minutes >> > > What's the use-case here again? > > Are you suspending, going home, and waking the laptop up and the AP is > not showing up in the menu? > > Or are you turning on an access point and expecting it to show up? > > Or are you walking from one access point coverage area to another? > > Or? > > Dan > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Scannning
It is simpler: Sorry I was not clear. I was not connected, and I was moving around to search for the correct AP (there is only one for students) In this case and in the case that wireless was off, scanning is not fast enough - Messaggio originale - Da: Dan Williams <[EMAIL PROTECTED]> A: yelo_3 <[EMAIL PROTECTED]> Cc: NetworkManager-List Inviato: Lunedì 19 marzo 2007, 1:04:16 Oggetto: Re: Scannning On Sun, 2007-03-18 at 23:45 +, yelo_3 wrote: > The use case is when I move around, in my university! There are different > access points in different places. > Or simply when I decide to enable wireless and before it was disabled Do they have the same SSID? Doesn't NetworkManager disconnect you when you move out of range of one SSID? When you're disconnected, NM should scan more frequently. So is the case that you are _still_ in the coverage of SSID A, but you have now moved into the area SSID B (A and B overlap), but you want to switch off A move to B immediately when B is in range? Dan > - Messaggio originale - > Da: Dan Williams <[EMAIL PROTECTED]> > A: yelo_3 <[EMAIL PROTECTED]> > Cc: NetworkManager-List > Inviato: Lunedì 19 marzo 2007, 0:40:36 > Oggetto: Re: Scannning > > On Sun, 2007-03-18 at 16:50 +, yelo_3 wrote: > > > In my experience when I click the applet new networks begin showing up > > > within 30 seconds. This is with an IPW2200 and IPW3945, my Atheros > > > card sometimes takes longer. > > > > it is not always true, with my ipw2200 sometimes I have to wait around 2 > > minutes > > What's the use-case here again? > > Are you suspending, going home, and waking the laptop up and the AP is > not showing up in the menu? > > Or are you turning on an access point and expecting it to show up? > > Or are you walking from one access point coverage area to another? > > Or? > > Dan > > > > > > > > > > > ___ > L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: > http://it.docs.yahoo.com/nowyoucan.html ___ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Scannning
On Sun, 2007-03-18 at 23:45 +, yelo_3 wrote: > The use case is when I move around, in my university! There are different > access points in different places. > Or simply when I decide to enable wireless and before it was disabled Do they have the same SSID? Doesn't NetworkManager disconnect you when you move out of range of one SSID? When you're disconnected, NM should scan more frequently. So is the case that you are _still_ in the coverage of SSID A, but you have now moved into the area SSID B (A and B overlap), but you want to switch off A move to B immediately when B is in range? Dan > - Messaggio originale - > Da: Dan Williams <[EMAIL PROTECTED]> > A: yelo_3 <[EMAIL PROTECTED]> > Cc: NetworkManager-List > Inviato: Lunedì 19 marzo 2007, 0:40:36 > Oggetto: Re: Scannning > > On Sun, 2007-03-18 at 16:50 +, yelo_3 wrote: > > > In my experience when I click the applet new networks begin showing up > > > within 30 seconds. This is with an IPW2200 and IPW3945, my Atheros > > > card sometimes takes longer. > > > > it is not always true, with my ipw2200 sometimes I have to wait around 2 > > minutes > > What's the use-case here again? > > Are you suspending, going home, and waking the laptop up and the AP is > not showing up in the menu? > > Or are you turning on an access point and expecting it to show up? > > Or are you walking from one access point coverage area to another? > > Or? > > Dan > > > > > > > > > > > ___ > L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: > http://it.docs.yahoo.com/nowyoucan.html ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Scannning
The use case is when I move around, in my university! There are different access points in different places. Or simply when I decide to enable wireless and before it was disabled - Messaggio originale - Da: Dan Williams <[EMAIL PROTECTED]> A: yelo_3 <[EMAIL PROTECTED]> Cc: NetworkManager-List Inviato: Lunedì 19 marzo 2007, 0:40:36 Oggetto: Re: Scannning On Sun, 2007-03-18 at 16:50 +, yelo_3 wrote: > > In my experience when I click the applet new networks begin showing up > > within 30 seconds. This is with an IPW2200 and IPW3945, my Atheros > > card sometimes takes longer. > > it is not always true, with my ipw2200 sometimes I have to wait around 2 > minutes What's the use-case here again? Are you suspending, going home, and waking the laptop up and the AP is not showing up in the menu? Or are you turning on an access point and expecting it to show up? Or are you walking from one access point coverage area to another? Or? Dan ___ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Scannning
On Sun, 2007-03-18 at 16:50 +, yelo_3 wrote: > > In my experience when I click the applet new networks begin showing up > > within 30 seconds. This is with an IPW2200 and IPW3945, my Atheros > > card sometimes takes longer. > > it is not always true, with my ipw2200 sometimes I have to wait around 2 > minutes What's the use-case here again? Are you suspending, going home, and waking the laptop up and the AP is not showing up in the menu? Or are you turning on an access point and expecting it to show up? Or are you walking from one access point coverage area to another? Or? Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Scannning
Exactly. Maybe a menu can just trigger "iwlist wlan0 scan" ? yelo_3 wrote: >> In my experience when I click the applet new networks begin showing up >> within 30 seconds. This is with an IPW2200 and IPW3945, my Atheros >> card sometimes takes longer. >> > > it is not always true, with my ipw2200 sometimes I have to wait around 2 > minutes > > > > > > > > > > ___ > L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: > http://it.docs.yahoo.com/nowyoucan.html > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Scannning
> In my experience when I click the applet new networks begin showing up > within 30 seconds. This is with an IPW2200 and IPW3945, my Atheros > card sometimes takes longer. it is not always true, with my ipw2200 sometimes I have to wait around 2 minutes ___ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Scannning
On 3/18/07, Joan Moreau <[EMAIL PROTECTED]> wrote: > > Would it be possible to add in the menu a simple action "scan new networks" > > It would really make life much easier... > > Thanks > > Joan > > When you click the menu it triggers a scan event, the scan is not instantaneous due to various driver issues but it should start populating local networks shortly after you click it. In my experience when I click the applet new networks begin showing up within 30 seconds. This is with an IPW2200 and IPW3945, my Atheros card sometimes takes longer. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
