hello,
If we have to go into the console to delete some configuration file, the
whole point of the applet is over (confort for the users, otherwise,
iwconfig works always ;-)
What is the decision about the menu item to scan for new networks
rather than triggering the scan when the user click on the applet ?
THanks
Joan
Michael Trunner wrote:
Am Mittwoch, den 02.05.2007, 17:39 -0400 schrieb Dan Williams:
On Wed, 2007-05-02 at 23:00 +0200, Michael Trunner wrote:
Hi,
I had a very similar idea. If I have choose a network it shouldn't
switch to another when the my goes off. Because everyday when my own
network is to faraway nm switch to the network of my neighbour. In this
case nm shouldn't search for other networks. I think a checkbox search
for networks would be nice.
If you don't want to associate with your neighbors network, remove it
from GConf. You connected to it once upon a time, which is why NM is
trying now. Granted, there should be a nice way to remove cached
networks, but having a checkbox for scanning is not the solution.
Hmm okay, but I have a similar problem on my University. There is one
for the complete campus (VPN) and one for special buildings with eap
which I prefer. But sometimes it switch like at home. Deleting the gconf
entry is okay for the problem with my neighbours. But not for my problem
one the university, because when I leave the building (so there is no
eap conncetion) then I'm using the campus WLAN and the gconf entry is
back.
Maybe some one have a good idea for this problem.
Michael
Dan
Bye
Michael
Am Mittwoch, den 02.05.2007, 19:12 +0300 schrieb Joan Moreau:
The point is not to do it by oneself or by the pc, but one may click
several time on the icon to see the status of the discovery which
trigger a new search and that does not end , while having to click once
on a button let people be able to see the current list of network
without risking to trigger a new search.
Christopher Aillon wrote:
Greg Oliver wrote:
On Wed, 2007-05-02 at 09:08 +0200, Soren Hansen wrote:
Could one of you perhaps explain to me why you want to do something
manually that network-manager does for you automatically? I don't quite
get it.
Honestly, so my LED does not blink repeatedly
You'll have others blinking anyway. Hard disk, etc.
- as well as go back to a
previous request to have wired/wireless active simultaneously (I know
thats coming). In that situation, that would be most pleasant. My
radio would not be scanning constantly when I do not need it and I could
scan when I want them both on.
And if your wired ever dies out? Or if you need to move for some reason
and need to unplug? Do you want NetworkManager to just sit there for
you to realize what happened, then click the applet, then click perform
scan, wait for a few seconds, figure out which Network, and then connect
you to wireless?
Personally, I'd rather my music stream keep on playing. The whole point
of NetworkManager is to do the work for you. People that don't want it
to do the work still have iwconfig/iwlist.
___
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
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
