Re: NetworkManager-list Digest, Vol 49, Issue 2

[Dustin Howett]

Done so, networkmanager reconnected, and my hostname got reset to
localhost.localdomain.

On Fri, Oct 3, 2008 at 5:36 PM, Dan Williams <[EMAIL PROTECTED]> wrote:
> On Fri, 2008-10-03 at 17:24 -0400, Dustin Howett wrote:
>> On Fri, Oct 3, 2008 at 7:49 AM, Alexander Sack <[EMAIL PROTECTED]> wrote:
>> > On Thu, Oct 02, 2008 at 06:28:02PM -0400, Dustin Howett wrote:
>> >> On Thu, Oct 2, 2008 at 3:20 PM, Dan Williams <[EMAIL PROTECTED]> wrote:
>> >> >
>> >> > It's a matter of persistent storage... when you reboot you'd probably
>> >> > like to have the hostname come back as what you set it before, and that
>> >> > means you have to store the persistent hostname somewhere on the
>> >> > filesystem...
>> >> >
>> >>
>> >> This is completely true. I'd like to have my hostname remain what I
>> >> set it; unfortunately, no matter what I set MY hostname to, NM insists
>> >> on making me localhost.localdomain, no matter what.
>> >> What might be better is some way to change it from nm or the related
>> >> applet; without other system administration tools.
>> >
>> > The latest trunk builds shouldn't do that anymore. What build/package
>> > are you using?
>> >
>>
>> Latest trunk build straight from SVN as of not even 5 minutes ago,
>> unfortunately.
>
> Did you reboot or 'killall -TERM nm-system-settings'?  One of those two
> is necessary for the fix to take effect.
>
> Dan
>
>
>



-- 

- DH
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: NetworkManager-list Digest, Vol 49, Issue 2

[Dan Williams]

On Fri, 2008-10-03 at 17:24 -0400, Dustin Howett wrote:
> On Fri, Oct 3, 2008 at 7:49 AM, Alexander Sack <[EMAIL PROTECTED]> wrote:
> > On Thu, Oct 02, 2008 at 06:28:02PM -0400, Dustin Howett wrote:
> >> On Thu, Oct 2, 2008 at 3:20 PM, Dan Williams <[EMAIL PROTECTED]> wrote:
> >> >
> >> > It's a matter of persistent storage... when you reboot you'd probably
> >> > like to have the hostname come back as what you set it before, and that
> >> > means you have to store the persistent hostname somewhere on the
> >> > filesystem...
> >> >
> >>
> >> This is completely true. I'd like to have my hostname remain what I
> >> set it; unfortunately, no matter what I set MY hostname to, NM insists
> >> on making me localhost.localdomain, no matter what.
> >> What might be better is some way to change it from nm or the related
> >> applet; without other system administration tools.
> >
> > The latest trunk builds shouldn't do that anymore. What build/package
> > are you using?
> >
> 
> Latest trunk build straight from SVN as of not even 5 minutes ago,
> unfortunately.

Did you reboot or 'killall -TERM nm-system-settings'?  One of those two
is necessary for the fix to take effect.

Dan


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: NetworkManager-list Digest, Vol 49, Issue 2

[Dustin Howett]

On Fri, Oct 3, 2008 at 7:49 AM, Alexander Sack <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 02, 2008 at 06:28:02PM -0400, Dustin Howett wrote:
>> On Thu, Oct 2, 2008 at 3:20 PM, Dan Williams <[EMAIL PROTECTED]> wrote:
>> >
>> > It's a matter of persistent storage... when you reboot you'd probably
>> > like to have the hostname come back as what you set it before, and that
>> > means you have to store the persistent hostname somewhere on the
>> > filesystem...
>> >
>>
>> This is completely true. I'd like to have my hostname remain what I
>> set it; unfortunately, no matter what I set MY hostname to, NM insists
>> on making me localhost.localdomain, no matter what.
>> What might be better is some way to change it from nm or the related
>> applet; without other system administration tools.
>
> The latest trunk builds shouldn't do that anymore. What build/package
> are you using?
>

Latest trunk build straight from SVN as of not even 5 minutes ago,
unfortunately.
Thanks!
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: knetworkmanager stopped working

[Anton Moiseev]

>> > > Oct  2 18:39:41 benderamp-hp NetworkManager: 
>> > > wait_for_connection_expired(): Connection (2)
>> > > /org/freedesktop/NetworkManagerSettings/Connection/1 failed to
>> > > activate (timeout): (0) Connection was not provided by any settings
>> > > service
>> >
>> > Looks like a configuration mismatch between KNM and NM to me. You could
>> > try to recreate your connections.
>>
>> It means that something (knm probably) told NetworkManager to activate a
>> connection, but that thing (knm probably) didn't actually provide that
>> connection over D-Bus.
>
> Or NM rejected the connection because some setting's properties changed
> (e.g. NM property name != KNM property name) due to a NM or KNM update. That's
> what I observed in the majority of cases.
>
> Helmut
>

The thing is that I have completely removed all updated packages and reinstalled
NetworkManager and NetworkManager-kde from OpenSUSE installation DVD,
and those versions did work together after initial system setup.
I have also tried to remove all configuration settings of knetworkmanager
(~/.kde/share/apps/knetworkmanagerrc) from my home directory, so for me I
have rather closely reproduced the situation in which knetworkmanager did work
in the past, but now it does not. So I must have missed something here
- probably
this could be some DBUS update or config file which I have missed.

I will try to write to knetworkmanager mailing list provided above.




As temporary workaround I would ask another question - is it possible to run
gnome network manager (nm-applet) under kde4? if it is possible, then how.

When I start nm-applet from console, I receive the following error message:

** (nm-applet:8134): WARNING **: 
applet_dbus_manager_start_service(): Could not acquire the
NetworkManagerUserSettings service as it is already taken.  Return: 3


(nm-applet:8134): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed


I have wireless network, protected with password, which is stored in
gnome keyring,
if that makes sense.

Thank's to all for help
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Storing the WEP key outside user's keyring

[Dan Williams]

On Fri, 2008-10-03 at 15:40 -0500, Aaron Konstam wrote:
> On Fri, 2008-10-03 at 15:55 -0400, Dan Williams wrote:
> > On Fri, 2008-10-03 at 18:47 +0200, Marcin 'Qrczak' Kowalczyk wrote:
> > > 2008/10/3 Robert Piasek <[EMAIL PROTECTED]>:
> > > 
> > > > You can use keyfile plugin and define your system wide connection. That 
> > > > way
> > > > NM will activate during boot.
> > > 
> > > How do do that? Where is the documentation?
> > 
> > There is a system settings service that will use the configuration from
> > your /etc/network/interfaces file if it's configured correctly, and/or
> > you can use the keyfile plugin for persistent connection storage as
> > well.
> What constitutes "configured correctly"? Does Fedora have a ketfile
> plugin, and if so where do you get it and how is it used?

Yes, but it's not enabled by default until the plugin interaction issues
are sorted out soon.

Dan

> > 
> > I'd first try setting up /etc/network/interfaces in the normal Ubuntu
> > way and if that fails, then Alexander should fix it :P
> > 
> > Dan
> > 
> > 
> > ___
> > NetworkManager-list mailing list
> > NetworkManager-list@gnome.org
> > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> --
> ===
> I've been on this lonely road so long, Does anybody know where it goes,
> I remember last time the signs pointed home, A month ago. -- Carpenters,
> "Road Ode"
> ===
> Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED]
> 

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Storing the WEP key outside user's keyring

[Aaron Konstam]

On Fri, 2008-10-03 at 15:55 -0400, Dan Williams wrote:
> On Fri, 2008-10-03 at 18:47 +0200, Marcin 'Qrczak' Kowalczyk wrote:
> > 2008/10/3 Robert Piasek <[EMAIL PROTECTED]>:
> > 
> > > You can use keyfile plugin and define your system wide connection. That 
> > > way
> > > NM will activate during boot.
> > 
> > How do do that? Where is the documentation?
> 
> There is a system settings service that will use the configuration from
> your /etc/network/interfaces file if it's configured correctly, and/or
> you can use the keyfile plugin for persistent connection storage as
> well.
What constitutes "configured correctly"? Does Fedora have a ketfile
plugin, and if so where do you get it and how is it used?
> 
> I'd first try setting up /etc/network/interfaces in the normal Ubuntu
> way and if that fails, then Alexander should fix it :P
> 
> Dan
> 
> 
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
--
===
I've been on this lonely road so long, Does anybody know where it goes,
I remember last time the signs pointed home, A month ago. -- Carpenters,
"Road Ode"
===
Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED]

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Storing the WEP key outside user's keyring

[Marcin 'Qrczak' Kowalczyk]

2008/10/3 Dan Williams <[EMAIL PROTECTED]>:

> I'd first try setting up /etc/network/interfaces in the normal Ubuntu
> way and if that fails, then Alexander should fix it :P

I can't make it working: I entered data in System → Preferences →
Network, which indeed stored them in /etc/network/interfaces, but the
network is unreachable and nm does not list that connection. (And I
think this GUI is being deprecated, favoring nm.)

I will give up.

-- 
Marcin Kowalczyk
[EMAIL PROTECTED]
http://qrnik.knm.org.pl/~qrczak/
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: knetworkmanager stopped working

[Dan Williams]

On Fri, 2008-10-03 at 00:20 +0200, Helmut Schaa wrote:
> Am Donnerstag, 2. Oktober 2008 schrieb Dan Williams:
> > On Thu, 2008-10-02 at 17:07 +0200, Helmut Schaa wrote:
> > > Hi,
> > > 
> > > Am Donnerstag, 2. Oktober 2008 schrieb Anton Moiseev:
> > > > Oct  2 18:39:41 benderamp-hp NetworkManager: 
> > > > wait_for_connection_expired(): Connection (2)
> > > > /org/freedesktop/NetworkManagerSettings/Connection/1 failed to
> > > > activate (timeout): (0) Connection was not provided by any settings
> > > > service
> > > 
> > > Looks like a configuration mismatch between KNM and NM to me. You could
> > > try to recreate your connections.
> > 
> > It means that something (knm probably) told NetworkManager to activate a
> > connection, but that thing (knm probably) didn't actually provide that
> > connection over D-Bus.
> 
> Or NM rejected the connection because some setting's properties changed
> (e.g. NM property name != KNM property name) due to a NM or KNM update. That's
> what I observed in the majority of cases.

Ah, understood.  I don't think any of the settings have changed for more
than a month now...  vpn data/secrets split should have been the last
one.

Dan


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Which AP is chosen when several are found for the same SSID?

[Dan Williams]

On Fri, 2008-10-03 at 11:42 -0400, Jose Aliste wrote:
> Thanks for the info ... I just have one more question, see inline. 
> 
> On Thu, Oct 2, 2008 at 3:18 PM, Dan Williams <[EMAIL PROTECTED]> wrote:
> On Wed, 2008-10-01 at 19:14 -0400, Jose Aliste wrote:
> 
> > Hi all,
> >
> > I want to ask the question in the subject:
> > Which AP is chosen when several are found for the same SSID?
> > I ask this because I see three AP from mi wireless network
> at my
> > office. Two of them are "802.11G" AP are the other one is
> only
> > "802.11B" the signal for the slow one is better(it is
> nearer) and NM
> > always connects to it. However, I would like to NM to
> connect to one
> > of the others because even with less signal the connection
> is
> > better( 33mb/s against the 11mb/s of  a b connection!).
> 
> 
> At this moment, this is left up to the driver and the
> supplicant.  The
> supplicant will apparently choose the AP with the best signal
> strength
> (since the scan results for the same SSID are sorted by signal
> strength), but the driver can also choose to roam from AP to
> AP based on
> other criteria.
> 
>  
> 
> > So, how can I tell NM to use the AP I need ?
> 
> 
> You can try to set the BSSID in the connection editor to lock
> it onto
> one of the APs, but the driver has the discretion to ignore
> that and
> roam to an AP it thinks is better.  We don't yet have the
> facility to
> lock to 802.11g at _any_ level of the stack, not just
> NetworkManager.
> 
> I am using NM 0.6 in Hardy and If I do as you or aaron said(keeping in
> th bssid only the address of the ap I want), but it does not work. 
> However, If I go with manual config and I set the  AP by using the
> wireless-ap option in the /etc/network/interfaces  then everything
> works... Would I be more lucky in NM 0.7, I mean does NM 0.7 try to
> force the AP? Btw wpa_supplicant is used even if I am not using WPA? 

NM 0.6 doesn't have the capability to lock to a particular AP.  NM 0.7
has the capability, but is still subject to driver behavior.  Give NM
0.7 a shot and let us know if locking to your AP's BSSID works.

Dan

> Thanks
> 
> José
> 
>  
> 
> You could try setting the data rate, but that doesn't always
> do what you
> want since you can only set it to one value, and the card
> would be
> unable to rate-scale based on signal quality of the locked AP.
> 
> In short, can't really be done, but this is only partly NM's
> fault.
> There's a lot more work in the stack from drivers, to WEXT, to
> wpa_supplicant to make sure this works the way you want it.
> 
> Dan
> 
> 
> 
> 

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Problems with latest network manager

[Dan Williams]

On Fri, 2008-10-03 at 18:50 +0100, Tim Hawkins wrote:
> GSM modems now seem to be completely broken and no longer function. I am
> unable to make a connection 
> on a previously functioning system. 
> 
> Hardware: Acer Aspire One. 
> Modem: Huawei 169G ( very similar to 220 )
> Provider: Three UK, Orange UK 
> OS: Intrepid Alpha6, tracking changes in update manager. 
> Version effected: 0.7~~svn20080927t101113.0-ubuntu1
> 
> symptoms are:
> 
>   1) The GSM modem connection now prompts for a password, even though the
> password 
>   is provided in the configuration for the connection, the 
> password does
> not 
>   seem to do anything, if i enter a password, it is immediately
> rejected, too 
>   fast to have been used in a connection attempt. I have even 
> tried
> entering
>   network password, admin password, keyring password, all to no 
> avail. 

I may have just fixed that yesterday; if the PPP server didn't take the
password the first time and re-asked, then NM would re-ask since the
server apparently didn't like you.  NM will now try the password at
least one more time before actually asking you.

>   2) The password above is shown on the entry dialogue in clear, so now
> everybody on the 
>   train next to me can see my password as I type it. Should show
> shrouded and 
>   have a "show password" check box under it as per all other 
> dialogues. 

Yes, the dialog there needs some work to:

(a) prefill the existing password
(b) add a "Show Password" button
(c) show the user as well (though that can't be changed there, it should
be shown for informational purposes)

>   3) The connection type (GPRS, UMTS etc ) is not retained in the
> connection info screen, changing 
>   it and then reentering the editor shows it was not saved, the 
> default
> however 
>   is "UMTS", not "Any" which it should be. (side note, UMTS is 
> not a
> well understood term
>   outside of the US, cant we just use simple terms like 2G, 3G , 
> any).

Really?  I've _never_ heard anyone in the US say "UMTS", but I've heard
tons of people in Europe and elsewhere use it.  The US never actually
deployed UMTS alone, both T-Mobile and AT&T (and the regional GSM
providers) pretty much jumped directly to HSDPA/HSPA.  There are
certainly UMTS _phones_ running around, but all the providers use their
custom terminology for that.

> Setting 
>   this wrong seems to result in a "disconnect" message  
> immediately when
> dialling, and since you 
>   can no longer set it ... well . 

Those options don't actually do anything at this time since each piece
of hardware has different mechanisms for changing bands.  That and other
options in that dialog will be hidden before release.

>   4) Setting a connection to "system" is not saved, existing connections
> i had set to "system"
>   have mysteriously disappeared, i had a number of connections 
> setup for
> the multiple 
>   testing accounts I have on this machine, now they are no longer
> visible. How do I 
>   get to my "system" connection definitions now.? 

It's likely  that the plugins your distro has set up for system settings
aren't capable of saving (ifupdown, ifcfg-fedora, ifcfg-suse).  The only
one that can write out information is the keyfile plugin which isn't
enabled by default.

Before 0.7 is release, the system settings service will stack the
plugins and saving will work correctly when both a read-only and a
read-write plugin are in use.

>   5) The connection configuration  editor dialog will often (most of the
> time) under circumstances i cant yet pin down, not enable 
>   the OK button on the conf dialog, leaving only Cancel there. 
> This
> happens no matter 
>   what you change on the dialog. If its doing it for some reason, 
> then
> it should say that on the screen, something like "saving disabled
> because ." 

The OK button is only enabled when all the options in all the pages
validate.  Internally there is enough information to give the user
"hints" as to what might be wrong, but that's not hooked up at this
time.  It sucks, yes.  The idea solution is to use some visual hints
(highlight the tab and entry with red or something?) and have tooltips
for each entry showing how to enter the data.

> 6) The dropdown menu with the connections listed, shows a "disconect"
> entry under any 3g connection, which does nothing, you have to click on 
> the actual connection menu entry to disconnect it. 

That shouldn't be the case; it seems to work for me here with stock
upstream NM from latest SVN.  Can you grab some logs
from /var/log/daemon.log from NM around the time you're trying to
disconnect?

> 7) Not related to 3G, there does not seem to be any way to "disconnect"
> a wifi connection, other than to connect another one., can we have the 
> ability to disconne

Re: Storing the WEP key outside user's keyring

[Dan Williams]

On Fri, 2008-10-03 at 18:47 +0200, Marcin 'Qrczak' Kowalczyk wrote:
> 2008/10/3 Robert Piasek <[EMAIL PROTECTED]>:
> 
> > You can use keyfile plugin and define your system wide connection. That way
> > NM will activate during boot.
> 
> How do do that? Where is the documentation?

There is a system settings service that will use the configuration from
your /etc/network/interfaces file if it's configured correctly, and/or
you can use the keyfile plugin for persistent connection storage as
well.

I'd first try setting up /etc/network/interfaces in the normal Ubuntu
way and if that fails, then Alexander should fix it :P

Dan


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Problems with latest network manager

[Tim Hawkins]

After a lot of messing around i have finally managed to get it to dial.
I believe that network-manager is crashing and restarting shortly after
booting, but as i log in it is dialling using one of the GSM profiles
that i had set to system, that i can no longer see. But because the
modem is connected to the wrong network the dial does not succeed. This
may be resulting in the crash.

I can make it dial and connect by... 

1) Boot the machine with the modem connected, wait for the crash
reporter to report that the network manager has crashed... 

2) Remove and reinsert the modem, this seems to be important...

3) Open minicom and issue the AT+COPS=1,2,23420 command to the modem to
make it attach to the 3 network. 

4) Restart the machine (restarting network manager does not seem to
work)

5) network manager will now dial and connect to the network immediately
after login and wont crash. 

On Fri, 2008-10-03 at 18:50 +0100, Tim Hawkins wrote:
> GSM modems now seem to be completely broken and no longer function. I am
> unable to make a connection 
> on a previously functioning system. 
> 
> Hardware: Acer Aspire One. 
> Modem: Huawei 169G ( very similar to 220 )
> Provider: Three UK, Orange UK 
> OS: Intrepid Alpha6, tracking changes in update manager. 
> Version effected: 0.7~~svn20080927t101113.0-ubuntu1
> 
> symptoms are:
> 
>   1) The GSM modem connection now prompts for a password, even though the
> password 
>   is provided in the configuration for the connection, the 
> password does
> not 
>   seem to do anything, if i enter a password, it is immediately
> rejected, too 
>   fast to have been used in a connection attempt. I have even 
> tried
> entering
>   network password, admin password, keyring password, all to no 
> avail. 
> 
>   2) The password above is shown on the entry dialogue in clear, so now
> everybody on the 
>   train next to me can see my password as I type it. Should show
> shrouded and 
>   have a "show password" check box under it as per all other 
> dialogues. 
> 
>   3) The connection type (GPRS, UMTS etc ) is not retained in the
> connection info screen, changing 
>   it and then reentering the editor shows it was not saved, the 
> default
> however 
>   is "UMTS", not "Any" which it should be. (side note, UMTS is 
> not a
> well understood term
>   outside of the US, cant we just use simple terms like 2G, 3G , 
> any).
> Setting 
>   this wrong seems to result in a "disconnect" message  
> immediately when
> dialling, and since you 
>   can no longer set it ... well . 
> 
>   4) Setting a connection to "system" is not saved, existing connections
> i had set to "system"
>   have mysteriously disappeared, i had a number of connections 
> setup for
> the multiple 
>   testing accounts I have on this machine, now they are no longer
> visible. How do I 
>   get to my "system" connection definitions now.? 
> 
>   5) The connection configuration  editor dialog will often (most of the
> time) under circumstances i cant yet pin down, not enable 
>   the OK button on the conf dialog, leaving only Cancel there. 
> This
> happens no matter 
>   what you change on the dialog. If its doing it for some reason, 
> then
> it should say that on the screen, something like "saving disabled
> because ." 
> 
> 6) The dropdown menu with the connections listed, shows a "disconect"
> entry under any 3g connection, which does nothing, you have to click on 
> the actual connection menu entry to disconnect it. 
> 
> 7) Not related to 3G, there does not seem to be any way to "disconnect"
> a wifi connection, other than to connect another one., can we have the 
> ability to disconnect a wifi connection like we have with the gsm
> modems. 
> 
> 8) I know its against HID design guidelines, but can we have all the
> "action" buttons on the dialogue's moved to the top, network manager
> will be used a lot on net-books etc which have small screens (480->600
> pixels high), i quite often find i cant reach the buttons to action
> dialogs on my net-book ( note there is a trick you can use, turn on
> virtual desktops and arrange them in a 2x2 array) then drag your dialog
> until it is half way between the two, then you can use the up and down
> desktop move functions to reach the upper and lower halves of the
> dialog, but its a pain to have to do this all the time). 
> 
> 9) enhancement request... Most GSM modems have a network scanning mode
> on the huawei's  you open minicom on /dev/ttyUSB2 at 115200 baud, and
> issue. "AT+COPS=?", the modem will then rapid blink for a while and
> respond with a list of available networks, with network names and
> numbers. you can then issue AT+COPS=1,2,network_number to set the
> network. for example AT+COPS=1,2,23400 will select "3 UK". This is a
> life saver bec

Problems with latest network manager

[Tim Hawkins]

GSM modems now seem to be completely broken and no longer function. I am
unable to make a connection 
on a previously functioning system. 

Hardware: Acer Aspire One. 
Modem: Huawei 169G ( very similar to 220 )
Provider: Three UK, Orange UK 
OS: Intrepid Alpha6, tracking changes in update manager. 
Version effected: 0.7~~svn20080927t101113.0-ubuntu1

symptoms are:

1) The GSM modem connection now prompts for a password, even though the
password 
is provided in the configuration for the connection, the 
password does
not 
seem to do anything, if i enter a password, it is immediately
rejected, too 
fast to have been used in a connection attempt. I have even 
tried
entering
network password, admin password, keyring password, all to no 
avail. 

2) The password above is shown on the entry dialogue in clear, so now
everybody on the 
train next to me can see my password as I type it. Should show
shrouded and 
have a "show password" check box under it as per all other 
dialogues. 

3) The connection type (GPRS, UMTS etc ) is not retained in the
connection info screen, changing 
it and then reentering the editor shows it was not saved, the 
default
however 
is "UMTS", not "Any" which it should be. (side note, UMTS is 
not a
well understood term
outside of the US, cant we just use simple terms like 2G, 3G , 
any).
Setting 
this wrong seems to result in a "disconnect" message  
immediately when
dialling, and since you 
can no longer set it ... well . 

4) Setting a connection to "system" is not saved, existing connections
i had set to "system"
have mysteriously disappeared, i had a number of connections 
setup for
the multiple 
testing accounts I have on this machine, now they are no longer
visible. How do I 
get to my "system" connection definitions now.? 

5) The connection configuration  editor dialog will often (most of the
time) under circumstances i cant yet pin down, not enable 
the OK button on the conf dialog, leaving only Cancel there. 
This
happens no matter 
what you change on the dialog. If its doing it for some reason, 
then
it should say that on the screen, something like "saving disabled
because ." 

6) The dropdown menu with the connections listed, shows a "disconect"
entry under any 3g connection, which does nothing, you have to click on 
the actual connection menu entry to disconnect it. 

7) Not related to 3G, there does not seem to be any way to "disconnect"
a wifi connection, other than to connect another one., can we have the 
ability to disconnect a wifi connection like we have with the gsm
modems. 

8) I know its against HID design guidelines, but can we have all the
"action" buttons on the dialogue's moved to the top, network manager
will be used a lot on net-books etc which have small screens (480->600
pixels high), i quite often find i cant reach the buttons to action
dialogs on my net-book ( note there is a trick you can use, turn on
virtual desktops and arrange them in a 2x2 array) then drag your dialog
until it is half way between the two, then you can use the up and down
desktop move functions to reach the upper and lower halves of the
dialog, but its a pain to have to do this all the time). 

9) enhancement request... Most GSM modems have a network scanning mode
on the huawei's  you open minicom on /dev/ttyUSB2 at 115200 baud, and
issue. "AT+COPS=?", the modem will then rapid blink for a while and
respond with a list of available networks, with network names and
numbers. you can then issue AT+COPS=1,2,network_number to set the
network. for example AT+COPS=1,2,23400 will select "3 UK". This is a
life saver because the modems will often lock onto an alternative 
network that does not do 3G (blink blue), in the uk orange is the fall
back GPRS (blink green)
network for three's 3G network, once the modem gets locked onto that 
network its a bugger to get it off it as the signal strength is often
greater than the 3g one. Can we have a network browser, and the ability
to set the network for a connection?, i notice there is a network Field
in the config, but no indication as to what is supposed to be put there,
the full name , short name, network number ?... and no indication as to 
what it is supposed to do, does it force the modem to that network, or
abort the connection if the modem is not on that network, or is it just
for information?. 

As stated above, the 3g Modem side is now unusable, which is a shame as 
it was working very well only a few days ago.



___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Storing the WEP key outside user's keyring

[Marcin 'Qrczak' Kowalczyk]

2008/10/3 Robert Piasek <[EMAIL PROTECTED]>:

> You can use keyfile plugin and define your system wide connection. That way
> NM will activate during boot.

How do do that? Where is the documentation?

-- 
Marcin Kowalczyk
[EMAIL PROTECTED]
http://qrnik.knm.org.pl/~qrczak/
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Which AP is chosen when several are found for the same SSID?

[Jose Aliste]

Thanks for the info ... I just have one more question, see inline.

On Thu, Oct 2, 2008 at 3:18 PM, Dan Williams <[EMAIL PROTECTED]> wrote:

> On Wed, 2008-10-01 at 19:14 -0400, Jose Aliste wrote:
> > Hi all,
> >
> > I want to ask the question in the subject:
> > Which AP is chosen when several are found for the same SSID?
> > I ask this because I see three AP from mi wireless network at my
> > office. Two of them are "802.11G" AP are the other one is only
> > "802.11B" the signal for the slow one is better(it is nearer) and NM
> > always connects to it. However, I would like to NM to connect to one
> > of the others because even with less signal the connection is
> > better( 33mb/s against the 11mb/s of  a b connection!).
>
> At this moment, this is left up to the driver and the supplicant.  The
> supplicant will apparently choose the AP with the best signal strength
> (since the scan results for the same SSID are sorted by signal
> strength), but the driver can also choose to roam from AP to AP based on
> other criteria.
>
>

> > So, how can I tell NM to use the AP I need ?
>
> You can try to set the BSSID in the connection editor to lock it onto
> one of the APs, but the driver has the discretion to ignore that and
> roam to an AP it thinks is better.  We don't yet have the facility to
> lock to 802.11g at _any_ level of the stack, not just NetworkManager.
>

I am using NM 0.6 in Hardy and If I do as you or aaron said(keeping in th
bssid only the address of the ap I want), but it does not work.
However, If I go with manual config and I set the  AP by using the
wireless-ap option in the /etc/network/interfaces  then everything works...
Would I be more lucky in NM 0.7, I mean does NM 0.7 try to force the AP? Btw
wpa_supplicant is used even if I am not using WPA?

Thanks

José



> You could try setting the data rate, but that doesn't always do what you
> want since you can only set it to one value, and the card would be
> unable to rate-scale based on signal quality of the locked AP.
>
> In short, can't really be done, but this is only partly NM's fault.
> There's a lot more work in the stack from drivers, to WEXT, to
> wpa_supplicant to make sure this works the way you want it.
>

> Dan
>
>
>
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Storing the WEP key outside user's keyrin g

[Robert Piasek]

Marcin 'Qrczak' Kowalczyk wrote:
> Network-manager successfully connects to a wireless network, using the
> WEP key it stored in the Gnome keyring. Is it possible to enable that
> connection without an X session, without logging in, and in particular
> without unlocking the keyring? How to do that?
>
> This is network-manager 0.7~~svn20080928t225540+eni0-0ubuntu2~nm3~hardy1.
>
>   

You can use keyfile plugin and define your system wide connection. That way
NM will activate during boot.

Regards,
Rob

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: NetworkManager-list Digest, Vol 49, Issue 2

[Alexander Sack]

On Thu, Oct 02, 2008 at 06:28:02PM -0400, Dustin Howett wrote:
> On Thu, Oct 2, 2008 at 3:20 PM, Dan Williams <[EMAIL PROTECTED]> wrote:
> >
> > It's a matter of persistent storage... when you reboot you'd probably
> > like to have the hostname come back as what you set it before, and that
> > means you have to store the persistent hostname somewhere on the
> > filesystem...
> >
> 
> This is completely true. I'd like to have my hostname remain what I
> set it; unfortunately, no matter what I set MY hostname to, NM insists
> on making me localhost.localdomain, no matter what.
> What might be better is some way to change it from nm or the related
> applet; without other system administration tools.

The latest trunk builds shouldn't do that anymore. What build/package
are you using?

 - Alexander

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: knetworkmanager stopped working

[Helmut Schaa]

Am Donnerstag, 2. Oktober 2008 schrieb Dan Williams:
> On Thu, 2008-10-02 at 17:07 +0200, Helmut Schaa wrote:
> > Hi,
> > 
> > Am Donnerstag, 2. Oktober 2008 schrieb Anton Moiseev:
> > > Oct  2 18:39:41 benderamp-hp NetworkManager: 
> > > wait_for_connection_expired(): Connection (2)
> > > /org/freedesktop/NetworkManagerSettings/Connection/1 failed to
> > > activate (timeout): (0) Connection was not provided by any settings
> > > service
> > 
> > Looks like a configuration mismatch between KNM and NM to me. You could
> > try to recreate your connections.
> 
> It means that something (knm probably) told NetworkManager to activate a
> connection, but that thing (knm probably) didn't actually provide that
> connection over D-Bus.

Or NM rejected the connection because some setting's properties changed
(e.g. NM property name != KNM property name) due to a NM or KNM update. That's
what I observed in the majority of cases.

Helmut
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: NetworkManager-list Digest, Vol 49, Issue 2

[Howard Chu]

Dan Williams wrote:

On Wed, 2008-10-01 at 16:14 -0700, Howard Chu wrote:

Message: 5
Date: Wed, 1 Oct 2008 23:58:22 +0200
From: Alexander Sack<[EMAIL PROTECTED]>
Subject: [PATCH] hostname support for ifupdown plugin + allow
read-only   hostname system provider + move nm_inotify_helper to 
plugin
independent place (system-settings/src/)
To: networkmanager-list@gnome.org
Message-ID:<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"

Implement system hostname support for debian/ubuntu

Fix "only system-setting plugins with 
NM_SYSTEM_CONFIG_INTERFACE_CAP_MODIFY_HOSTNAME
are considered a valid hostname provider"

Make nm-inotify-helper from ifcfg-fedora plugin usable
for other plugins too

Is any of that really necessary? Any tool that rewrites /etc/hostname is also
going to already call sethostname(); shouldn't you only need to call
gethostname() to get NM in sync? Why go thru the hassle of opening and reading
a file and calling sethostname() to tell the kernel what it already knows?


It's a matter of persistent storage... when you reboot you'd probably
like to have the hostname come back as what you set it before, and that
means you have to store the persistent hostname somewhere on the
filesystem...


Right, and /etc/init.d takes care of reading it on boot, so NM doesn't need to 
worry about restoring the persisted state. Moreover, NM gets started too late 
in the boot process for it to be useful for this purpose.



But it's just good programming to ensure that when that file changes,
updates are recognized, because whatever wrote that file out doesn't
_have_ to call sethostname(2).


Yes, but it's whatever wrote that file's responsibility to worry about it. 
After all, not everyone out there will even be running NetworkManager in the 
first place. Any admin tool that mucks around here can't assume that some 
other process will cleanup after it. Any sysadmin using vi has to know what 
they're doing.

--
  -- Howard Chu
  CTO, Symas Corp.   http://www.symas.com
  Director, Highland Sun http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: wpa_supplicant cli works, but NM insists "wireless is disabled"

[Andrew]

>>this time.  It's a policy decision; I made the decision to keep things
>>simple and direct and interpret the user's intent as disabling wireless
>>when the rfkill switch is turned on.
>
>Dan,
>
>even if I were some sort of C and networking guru and veteran member of your 
>development team, still i would not seek to impose any modifications to your 
>code.  (And I am light years away from all the above)  (I say this in response 
>to your mentioning "upstream" -- a word i've not heard before but assume has 
>something to do with committing code changes for general use). Your generous 
>contribution of skill has made things easier for millions.
>
>However, could you please provide a quick hack to meet my rare need, to keep 
>my wifi class always enabled, regardless of what the BIOS is reporting?  It 
>would be confined to my system strictly.

I am not asking for a whole patch.  Only a more specific clue as to which 
variables are involved, and at which level would it be best to intervene by 
assigning a constant (I'm assuming something like assigning a constant "TRUE" 
to some boolean somewhere)

thanks again
andrew
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: knetworkmanager stopped working

[Dan Williams]

On Thu, 2008-10-02 at 17:07 +0200, Helmut Schaa wrote:
> Hi,
> 
> Am Donnerstag, 2. Oktober 2008 schrieb Anton Moiseev:
> > Oct  2 18:39:41 benderamp-hp NetworkManager: 
> > wait_for_connection_expired(): Connection (2)
> > /org/freedesktop/NetworkManagerSettings/Connection/1 failed to
> > activate (timeout): (0) Connection was not provided by any settings
> > service
> 
> Looks like a configuration mismatch between KNM and NM to me. You could
> try to recreate your connections.

It means that something (knm probably) told NetworkManager to activate a
connection, but that thing (knm probably) didn't actually provide that
connection over D-Bus.

Dan


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

[PATCH] Fix crash of nm-system-settings in add_default_dhcp_connection

[Alexander Sack]

Fix crash of nm-system-settings in add_default_dhcp_connection when 
wired 
  device gets removed. 
  
* system-settings/src/main.c: 
- (add_default_dhcp_connection,device_removed_cb): 
passing the "key" instead of the value as second 
argument 
to g_hash_table_remove calls helps. 


Here the crash:

...
#6  0x00407e35 in get_details_for_udi (app=0x1cca4d0,
udi=0x1cdb1d0 "p��\001", mac=0x7fff49875070)
at main.c:244
#7  0x004081bd in add_default_dhcp_connection
(user_data=0x1cda560) at main.c:351
#8  0x7fe93e86750b in g_timeout_dispatch (source=0x1cd6a00,
callback=0x3e71, user_data=0x6)
at /build/buildd/glib2.0-2.18.1/glib/gmain.c:3587
#9  0x7fe93e866d4b in IA__g_main_context_dispatch
(context=0x1cd4b50)
at /build/buildd/glib2.0-2.18.1/glib/gmain.c:2142
#10 0x7fe93e86a51d in g_main_context_iterate (context=0x1cd4b50,
block=1, dispatch=1, 
self=) at
/build/buildd/glib2.0-2.18.1/glib/gmain.c:2776
#11 0x7fe93e86aa4d in IA__g_main_loop_run (loop=0x1ccb460) at
/build/buildd/glib2.0-2.18.1/glib/gmain.c:2984
#12 0x00408ce6 in main (argc=1, argv=0x7fff49875438) at
main.c:663



 - Alexander

=== modified file 'ChangeLog'
--- ChangeLog	2008-10-02 17:11:42 +
+++ ChangeLog	2008-10-03 02:52:39 +
@@ -1,8 +1,18 @@
+2008-10-03  Alexander Sack  <[EMAIL PROTECTED]>
+
+	Fix crash of nm-system-settings in add_default_dhcp_connection when wired
+	device gets removed.
+
+	* system-settings/src/main.c:
+		- (add_default_dhcp_connection,device_removed_cb):
+			passing the "key" instead of the value as second argument
+			to g_hash_table_remove calls helps.
+
 2008-10-02  Dan Williams  <[EMAIL PROTECTED]>
 
 	* src/nm-gsm-device.c
 		- (enter_pin_done, enter_pin, check_pin_done, real_act_stage1_prepare):
 			pass the required GSM secret along via user_data rather than keeping
 			it around in the private data where it sometimes didn't get cleared
 		- (real_get_ppp_name): implement using the GSM username
 

=== modified file 'system-settings/src/main.c'
--- system-settings/src/main.c	2008-08-27 02:57:21 +
+++ system-settings/src/main.c	2008-10-03 02:52:39 +
@@ -377,17 +377,17 @@ add_default_dhcp_connection (gpointer us
 	g_byte_array_append (s_wired->mac_address, info->mac->data, ETH_ALEN);
 	nm_connection_add_setting (wrapped, NM_SETTING (s_wired));
 
 	nm_sysconfig_settings_add_connection (info->app->settings, info->connection);
 
 	return FALSE;
 
 ignore:
-	g_hash_table_remove (info->app->wired_devices, info);
+	g_hash_table_remove (info->app->wired_devices, info->udi);
 	return FALSE;
 }
 
 static void
 device_added_cb (DBusGProxy *proxy, const char *udi, NMDeviceType devtype, gpointer user_data)
 {
 	Application *app = (Application *) user_data;
 	WiredDeviceInfo *info;
@@ -408,17 +408,17 @@ device_removed_cb (DBusGProxy *proxy, co
 {
 	Application *app = (Application *) user_data;
 	WiredDeviceInfo *info;
 
 	info = g_hash_table_lookup (app->wired_devices, udi);
 	if (!info)
 		return;
 
-	g_hash_table_remove (app->wired_devices, info);
+	g_hash_table_remove (app->wired_devices, info->udi);
 }
 
 /**/
 
 static void
 dbus_cleanup (Application *app)
 {
 	if (app->g_connection) {

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: NetworkManager-list Digest, Vol 49, Issue 2

[Dustin Howett]

On Thu, Oct 2, 2008 at 3:20 PM, Dan Williams <[EMAIL PROTECTED]> wrote:
>
> It's a matter of persistent storage... when you reboot you'd probably
> like to have the hostname come back as what you set it before, and that
> means you have to store the persistent hostname somewhere on the
> filesystem...
>

This is completely true. I'd like to have my hostname remain what I
set it; unfortunately, no matter what I set MY hostname to, NM insists
on making me localhost.localdomain, no matter what.
What might be better is some way to change it from nm or the related
applet; without other system administration tools.
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

PPP Setting doesn't seem to stick

[Darren Albers]

When I modify the setting "Send PPP Echo Packets" of my CDMA
connection it doesn't seem to stick.   Is anyone seeing that setting
stick, I wonder if I am having a profile issue or if this is an actual
bug.

Thanks!
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Storing the WEP key outside user’s keyring

[Marcin 'Qrczak' Kowalczyk]

Network-manager successfully connects to a wireless network, using the
WEP key it stored in the Gnome keyring. Is it possible to enable that
connection without an X session, without logging in, and in particular
without unlocking the keyring? How to do that?

This is network-manager 0.7~~svn20080928t225540+eni0-0ubuntu2~nm3~hardy1.

-- 
Marcin Kowalczyk
[EMAIL PROTECTED]
http://qrnik.knm.org.pl/~qrczak/
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list