gmane.linux.network.networkmanager.devel

Re: Little white window SECRET

Brian Morrison — 2012-05-23T11:31:21

On Wed, 23 May 2012 13:02:03 +0200
Timothy Murphy <gayleard< at >eircom.net> wrote:


Ah, I didn't realise that you couldn't, I thought you were saying that
the window was very small and didn't allow you to see what was entered.


I am not currently using NM but back in the dim and distant past I used
it for WiFi on my laptop, I did occasionally get a similar window, I
think it was used by the GNOME key storage program rather than directly
by NM. 


See above.


I'd guess that this could be a problem in your wireless driver rather
than directly in NM itself, but I'm not the best person to ask about it.

Perhaps someone else could comment if you add in a bit more information
about which hardware you have and which driver versions you're using. I
think it's known that some wireless drivers are less solid than others,
but it's probably also AP dependent too. WiFi standards are, well, not
actually standards at all, the WiFi Alliance testing is more like a set
of interoperability tests with 'gold' APs and hence it's p

Re: Little white window SECRET

Timothy Murphy — 2012-05-23T11:02:03


As I said, it does not allow any input into the window,
even if I click "show password",
which is in fact the only thing I can do in the window.

Do you see this "Secret" window?
If so, does it accept input?

Who provides this window, incidentally?
Is it NM?

I'm afraid this incident highlighted for me
how bad NM is when it doesn't work.
(I emphasize that this is only 5% or less of the time.
95% of the time it works fine.)
But when it is not working, I get out my Android phone
(Samsung Galaxy S2) and see if that has a network connection,
so I'll know if the fault actually lies with my WiFi router,
or with dhcpd on my server.
(These are rarely the case.)

The point is, I've never known my Android to have any problems
with WiFi, anywhere.
It lists the access points it sees (as does NM),
and if I click on one it asks me for the password
if that is required, and that is it.
I can go from one location to another,
and it seems to have no problem,
while NM appears to find a change of location very challenging.

Re: Little white window SECRET

Brian Morrison — 2012-05-23T09:12:43

On Wed, 23 May 2012 11:02 +0200
Timothy Murphy <gayleard< at >eircom.net> wrote:


It wants the password, or phrase, for your wireless connection whether
it is Wi-Fi or some other flavour.

You should be able to type in the field, it may not show the whole
string entered, but it should be there. Cut and paste would probably
help if you have your password/phrase/key somewhere accessible.

Little white window SECRET

Timothy Murphy — 2012-05-23T09:02:00

Every now and again NM stops working,
and a little window appears in the middle of the screen
(in fact in the middle of all virtual desktops
on my Fedora-16/KDE laptop).
The window is entitled Secret,
and it has a space to enter a password.
But in fact it is impossible to write in the space provided,
even if one clicks "Show password".

I don't know what password is wanted, even if I could enter one.

I find the only thing to do when this happens is to reboot the laptop.
NM usually works OK after the reboot.

Best way to keep alive mobile connection + openvpn?

PongráczI — 2012-05-23T07:16:02

Dear Guys,

We try to make a system, based on debian testing with MM 0.5.2, which is able to provide the following:

 
it connect automatically to the mobile broadband network using ZTE or Huawei usb modems,
 
it reconnects in any case, when the modem or the provider drops the connection,
 
it builds up the openvpn channel via the mobile broadband when ppp0 interface is available and working well
 
it can make it without any user interaction
 
note: there is gnome, but lightdm, fluxbox, policykit, network-manager, modem-manager, nm-applet, nmcli. Minimal system.


As I can see at this moment, we have to write our own control script, which controls at this moment only the 2G/3G connection:

 
checks gsm device is ready/available
 
checks the wwan is on or turn it on
 
nm-applet setup contains auto-connect for the connection


As in the last few days I found some strange issues with the stability of the mobile connection, I wonder how others solve this kind of problem?

Do you have any solution, recommendatio

Re: [PATCH v2] Re: Change the state of iface from disconnected toconnected using nmcli

Jirka Klimes — 2012-05-22T16:46:49

Commited:
e0329b4 libnm-glib: add 'autoconnect' property for devices
d1cbeeb core: authenticate Set() D-Bus call for NMDevice "Autoconnect" 
property
6d9338f core: add "Autoconnect" property to NMDevice

Jirka

[PATCH 4/4] Add switches to the Applet menu

Niv Sardi — 2012-05-21T23:03:48

this is actually quite a bigger change, we factorize a bit of code adding the menu to the function (though it's not strictly necesary), we give a callback to toggle the device state,
note that the callback is unimplemented for bt and wired.

Signed-off-by: Niv Sardi <xaiki< at >debian.org>
---
 src/applet-device-bt.c    |   12 +++--
 src/applet-device-cdma.c  |   15 ++++--
 src/applet-device-gsm.c   |   15 ++++--
 src/applet-device-wifi.c  |   16 ++++--
 src/applet-device-wimax.c |   15 ++++--
 src/applet-device-wired.c |   12 +++--
 src/applet.c              |  119 +++++++++++++++++++++++++++++++++++++++++++--
 src/applet.h              |   10 ++--
 8 files changed, 178 insertions(+), 36 deletions(-)

diff --git a/src/applet-device-bt.c b/src/applet-device-bt.c
index 4f1cac2..cbba5b9 100644
--- a/src/applet-device-bt.c
+++ b/src/applet-device-bt.c
< at >< at > -129,6 +129,12 < at >< at > add_connection_items (NMDevice *device,
 }
 }
 
+static gboolean
+bt_toggle (GtkWidget *sw, gpointer user_data)
+{
+g_log (G_LOG_DOMAIN, G_LOG_LEV

[PATCH 3/4] move creation ofapplet_menu_item_create_device_item_helper to it's own helper

Niv Sardi — 2012-05-21T23:03:47

this is going to be used to be able to make a more complex widget there, you should have guessed by the name it's going to be a switch

Signed-off-by: Niv Sardi <xaiki< at >debian.org>
---
 src/applet.c |   28 ++++++++++++++++++++++++++--
 1 file changed, 26 insertions(+), 2 deletions(-)

diff --git a/src/applet.c b/src/applet.c
index 6081a71..7b3a97b 100644
--- a/src/applet.c
+++ b/src/applet.c
< at >< at > -613,6 +613,30 < at >< at > applet_menu_item_activate_helper (NMDevice *device,
 }
 }
 
+GtkWidget *
+applet_menu_create_switch_item_helper (NMApplet  *applet,
+   GtkWidget *label,
+   GtkWidget *swbox)
+{
+GtkWidget *menu_item = gtk_image_menu_item_new ();
+#if GTK_CHECK_VERSION(3,1,6)
+GtkWidget *box = gtk_box_new (GTK_ORIENTATION_HORIZONTAL, 0);
+#else
+GtkWidget *box = gtk_hbox_new (FALSE, 0);
+#endif
+
+gtk_box_pack_start (GTK_BOX (box), label, TRUE, TRUE, 0);
+if (swbox)
+gtk_box_pack_start (GTK_BOX (box), swbox, FALSE, FALSE, 0);
+
+g_object_set (G_OBJECT (menu_item),
+              "child", b

[PATCH 2/4] whitespace fixup

Niv Sardi — 2012-05-21T23:03:46

Signed-off-by: Niv Sardi <xaiki< at >debian.org>
---
 src/applet.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/applet.c b/src/applet.c
index ccbbfbe..6081a71 100644
--- a/src/applet.c
+++ b/src/applet.c
< at >< at > -621,7 +621,7 < at >< at > applet_menu_item_add_complex_separator_helper (GtkWidget *menu,
 {
 GtkWidget *menu_item = gtk_image_menu_item_new ();
 #if GTK_CHECK_VERSION(3,1,6)
-        GtkWidget *box = gtk_box_new (GTK_ORIENTATION_HORIZONTAL, 0);
+GtkWidget *box = gtk_box_new (GTK_ORIENTATION_HORIZONTAL, 0);
 #else
 GtkWidget *box = gtk_hbox_new (FALSE, 0);
 #endif

[PATCH 1/4] reorder a bit the 'draw' signal hack

Niv Sardi — 2012-05-21T23:03:45

we draw the label in the box 'draw' signal, but we return FALSE, so that if there are other elements in the box they do get drawn too.
we also actually pass the label to the callback instead of looking for it.
this allows us to put a widget a little more complex in the same spot.

Signed-off-by: Niv Sardi <xaiki< at >debian.org>
---
 src/applet.c |   30 ++++++++++++++++++++++--------
 1 file changed, 22 insertions(+), 8 deletions(-)

diff --git a/src/applet.c b/src/applet.c
index be4e516..ccbbfbe 100644
--- a/src/applet.c
+++ b/src/applet.c
< at >< at > -689,7 +689,6 < at >< at > applet_new_menu_item_helper (NMConnection *connection,
 static void
 menu_item_draw_generic (GtkWidget *widget, cairo_t *cr)
 {
-GtkWidget *label;
 PangoFontDescription *desc;
 PangoLayout *layout;
 int width = 0, height = 0, owidth, oheight;
< at >< at > -699,8 +698,7 < at >< at > menu_item_draw_generic (GtkWidget *widget, cairo_t *cr)
 gdouble ypadding = 5.0;
 gdouble postpadding = 0.0;
 
-label = gtk_bin_get_child (GTK_BIN (widget));
-text = gtk_label_get_text (GTK_

[RFC] [PATCH 0/4] Make the C network-manager-gnome applet as sexy asthe gnome-shell one

Niv Sardi — 2012-05-21T23:03:44

Hello, this is an intent to get the C GNOME applet to look nice:
i.e. have switches for each device.  the patch is incomplete, but is
more a proof of concept than anything else.

you can see the result here:
http://core.evilgiggle.com/~xaiki/hacks/network-manager/new-nm-applet-sc.png
with a Dark GTK theme on the main screen, and the NO-theme theme in
the Xephyr.

in a nutshell:
+ Toggle button for each NMDevice (tested that it works for wireless
  only)
+ a spinner when the device state is not stable (connecting,
  disconnecting, searching,…)

[PATCH 1/4] reorder a bit the 'draw' signal hack

instead of drawing the label only, we draw in the menuitem cr, and
return FALSE to get the other widgets to draw, then we hookup 'draw'
on the label to inibit drawing there.

[PATCH 2/4] whitespace fixup

it was getting in my eyes all the time.

[PATCH 3/4] move creation of applet_menu_item_create_device_item_helper to it's own helper

this makes room for more complex widgets,
at this stage everything looks the same.

Re: ifcfg-rh and wpa_supplicant

Oncaphillis — 2012-05-22T05:21:53

Don't know how to figure out the 40MHz issue.

(A) Here comes the dmesg part around ath9k initialization in
     Fedora12/Linux 3.2.13

<snip>
ath9k 0000:04:00.0: PCI INT A -> Link[LN3A] -> GSI 18 (level, low) -> IRQ 18
ath9k 0000:04:00.0: setting latency timer to 64
...
...
ath: EEPROM regdomain: 0x60
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: 00
ath: Regpair used: 0x60
...
...
ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
Registered led device: ath9k-phy0
ieee80211 phy0: Atheros AR9280 Rev:2 mem=0xff560000, irq=18
</snip>

and the iwconfig stuff:

<snip>
wlan0     IEEE 802.11bgn  ESSID:"oncaphillis"
           Mode:Managed  Frequency:2.442 GHz  Access Point: 
00:25:9C:D0:04:FB
           Bit Rate=54 Mb/s   Tx-Power=16 dBm
           Retry  long limit:7   RTS thr:off   Fragment thr:off
           Encryption key:off
           Power Management:on
           Link Quality=45/70  Signal level=-65 dBm
           Rx invalid nwid:0  Rx invali

Re: [PATCH v2] Re: Change the state of iface from disconnected toconnected using nmcli

Dan Williams — 2012-05-21T21:52:33

One last thing with the permissions code; if we can't find the device
when we're about to call g_object_set(), we should return
NM_MANAGER_ERROR_UNKNOWN_DEVICE.  Other than that they both look good.

THanks!
Dan

Re: ifcfg-rh and wpa_supplicant

Dan Williams — 2012-05-21T17:02:57

Right, so we need to figure out why wifi isn't working on F16.  It
should work, and it should work well with nl80211.  WEXT is deprecated
and will be removed from upstream kernels in the future.  ath9k is
actively developed upstream and any issues are usually fixed pretty
quickly.

Are there any interesting messages in 'dmesg' output for your wifi card?
Is your access point 802.11n-enabled?  Is it using 40MHz wide channels?

Dan

Re: ifcfg-rh and wpa_supplicant

Oncaphillis — 2012-05-21T16:31:11

  Right now I've switched back to a fedora 13 with a self compiled
kernel 3.2.13. The wpa_supplicant gets started by /etc/init.d/wpa_supplicant
abd definitely uses the -Dwext option.

  The target I'm aiming for is Fedora16 with kernel 3.3.5-2 but I 
currently can't use it
since wifi does not work

Thanks

O.

Re: ifcfg-rh and wpa_supplicant

Dan Williams — 2012-05-21T15:42:36

That device is driven by the ath9k driver, which is one of the
better-supported mac80211 chipsets, so it should certainly work with
nl80211.  If it's not working, then we need to get some supplicant and
kernel debugging information to see what's wrong in the driver.  What
kernel version do you have?

Dan

Re: Not able to connect from CDMA2000 Modem from Network Managerconnection

ezee — 2012-05-20T19:36:18

I had attached it in previous thread...

ezee wrote:

Re: Not able to connect from CDMA2000 Modem from Network Managerconnection

Aleksander Morgado — 2012-05-20T17:55:13

http://live.gnome.org/NetworkManager/Debugging
  or
https://wiki.ubuntu.com/DebuggingModemmanager

Re: Not able to connect from CDMA2000 Modem from Network Managerconnection

ezee — 2012-05-20T13:47:57

Hi Aleksander,

Thanks for your reply :)

Yes, I am sure about connectivity. I can use it on my mate's Win OS.

Could you please refer me to any  guide to create ModemManager log?

--Eshant


Aleksander Morgado-5 wrote:

Re: Not able to connect from CDMA2000 Modem from Network Managerconnection

Aleksander Morgado — 2012-05-20T09:02:53

Hey,


Cannot see ModemManager debug logs; those would help. Anyway, there's a
warning saying:

<warn> CDMA connection failed: (32) No service

You sure you have connectivity in there?

Not able to connect from CDMA2000 Modem from Network Managerconnection

ezee — 2012-05-20T03:45:50

http://old.nabble.com/file/p33876035/kern.log kern.log  
http://old.nabble.com/file/p33876035/lshal.log lshal.log  
http://old.nabble.com/file/p33876035/m-tool.log m-tool.log  
http://old.nabble.com/file/p33876035/searchusb.log searchusb.log  
http://old.nabble.com/file/p33876035/syslog.log syslog.log  
http://old.nabble.com/file/p33876035/usb-info.txt usb-info.txt  
I have trouble connecting my modem through Network Manager. The modem is
given by Indian Government Telco. BSNL. I have attached logs as asked 
https://wiki.ubuntu.com/NetworkManager/Hardware/3G/Probing here . Please
help me to get this device supported. I use Ubuntu OS in my system and don't
want to migrate to Windows.


Reproduced issue on 12.04 also.


Thanks for your time and help...:)