Re: dbus sleep/wake problem

[Michael Biebl]

Jürg Billeter wrote:
> On Mit, 2007-05-02 at 19:55 +0200, Michael Biebl wrote:
>> Dawid Wróbel wrote:
>>> Hi,
>>> It seems that nm 0.6.5 has a problem with waking up from sleep
>>> mode. What I did was:
>>>
>> I can confirm that. network-mnanager-(applet) does not autoconnect after
>> suspend/resume.
> 
> We've also had problems with reconnecting to wireless networks after
> resuming from suspend. Waiting five seconds with the real wakeup seems
> to fix it; we haven't investigated the real cause of the problem yet.
> The attached patch may help.
> 

Hi Jürg,

thanks for the patch. Unfortunately it doesn't really solve the problem
for me. It indeed defers the wakeup/network activation but the first
connection attempt after resume always fails, and I'm prompted again to
enter the key for my WPA secured network.
If I click cancel, and select my wireless network from the dropdown list
again, nm makes a new connection attempt and on the second  try it works
most of the time.


Cheers,
Michael

P.S.: Sometimes I wished, I could tell nm-applet, that my wireless key
is correct and instead of prompting me for entering a new WPA key after
a failed connection attempt it would simply try a new reconnect.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: dbus sleep/wake problem

[Jürg Billeter]

On Mit, 2007-05-02 at 19:55 +0200, Michael Biebl wrote:
> Dawid Wróbel wrote:
> > Hi,
> > It seems that nm 0.6.5 has a problem with waking up from sleep
> > mode. What I did was:
> > 
> 
> I can confirm that. network-mnanager-(applet) does not autoconnect after
> suspend/resume.

We've also had problems with reconnecting to wireless networks after
resuming from suspend. Waiting five seconds with the real wakeup seems
to fix it; we haven't investigated the real cause of the problem yet.
The attached patch may help.

Regards,

Jürg
-- 
Jürg Billeter <[EMAIL PROTECTED]>
diff -puNr NetworkManager-0.6.5.orig/src/nm-dbus-nm.c NetworkManager-0.6.5/src/nm-dbus-nm.c
--- NetworkManager-0.6.5.orig/src/nm-dbus-nm.c	2007-04-18 20:13:06.0 +0200
+++ NetworkManager-0.6.5/src/nm-dbus-nm.c	2007-04-29 10:12:55.0 +0200
@@ -593,10 +593,33 @@ static DBusMessage *nm_dbus_nm_sleep (DB
 	return NULL;
 }
 
+static gboolean nm_dbus_nm_wake_now (NMData *app_data) {
+	g_return_val_if_fail (app_data, FALSE);
+
+	if (!app_data->asleep)
+		return FALSE;
+
+	app_data->asleep = app_data->disconnected = FALSE;
+
+	/* Remove all devices from the device list */
+	nm_lock_mutex (app_data->dev_list_mutex, __FUNCTION__);
+	while (g_slist_length (app_data->dev_list))
+		nm_remove_device (app_data, (NMDevice *)(app_data->dev_list->data));
+	nm_unlock_mutex (app_data->dev_list_mutex, __FUNCTION__);
+
+	nm_add_initial_devices (app_data);
+
+	nm_schedule_state_change_signal_broadcast (app_data);
+	nm_policy_schedule_device_change_check (app_data);
+
+	return FALSE;
+}
+
 static DBusMessage *nm_dbus_nm_wake (DBusConnection *connection, DBusMessage *message, NMDbusCBData *data)
 {
 	NMData	*app_data;
 	DBusMessageIter iter;
+	GSource *source;
 	gboolean enable_networking = FALSE;
 
 	g_return_val_if_fail (data && data->data && connection && message, NULL);
@@ -621,23 +644,18 @@ static DBusMessage *nm_dbus_nm_wake (DBu
 	/* Restore networking only if we're not disconnected or
 	   enable_networking argument is passed. */
 	if (app_data->asleep && (!app_data->disconnected || enable_networking)) {
-		if (enable_networking)
+		if (enable_networking) {
 			nm_info ("Enabling networking.");
-		else
+			nm_dbus_nm_wake_now (app_data);
+		} else {
 			nm_info ("Waking up from sleep.");
 
-		app_data->asleep = app_data->disconnected = FALSE;
-
-		/* Remove all devices from the device list */
-		nm_lock_mutex (app_data->dev_list_mutex, __FUNCTION__);
-		while (g_slist_length (app_data->dev_list))
-			nm_remove_device (app_data, (NMDevice *)(app_data->dev_list->data));
-		nm_unlock_mutex (app_data->dev_list_mutex, __FUNCTION__);
-
-		nm_add_initial_devices (app_data);
-
-		nm_schedule_state_change_signal_broadcast (app_data);
-		nm_policy_schedule_device_change_check (data->data);
+			/* Delay wakeup a bit to make sure devices are ready. */
+			source = g_timeout_source_new (5000);
+			g_source_set_callback (source, nm_dbus_nm_wake_now, app_data, NULL);
+			g_source_attach (source, app_data->main_context);
+			g_source_unref (source);
+		}
 	}
 
 	return NULL;
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Request for ergonomy feature

[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.

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

Re: Request for ergonomy feature

[Michael Trunner]

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.

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
> 
-- 
Wenn das eigene Wohlbefinden von der vereinigten Dummheit fast aller
Anderer geprägt ist, lebt man meistens in einer Demokratie.

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

Possible to set passhrase in gconf

[Grant Williamson]

Hi,

I am looking at ways to pre-configure via a panel on initial login 
Wireless. For testing is it still possible to add the 
password/passphrase in wireless gconf file. If so what is the corect 
option I should use.

Also is there also any documentation anywhere for the options available?


i.e. Using gconftool-2 I have created the following network file ...

gconftool-2 -t string --set 
/system/networking/wireless/networks/ATMEL/essid "ATMEL"
gconftool-2 -t int --set 
/system/networking/wireless/networks/ATMEL/timestamp 1178104046
gconftool-2 -t bool --set 
/system/networking/wireless/networks/ATMEL/fallback 0
gconftool-2 -t list --list-type string --set 
/system/networking/wireless/networks/ATMEL/bssids ["00:00:00:00:00:00"]
gconftool-2 -t int --set 
/system/networking/wireless/networks/ATMEL/we_cipher 0
gconftool-2 -t int --set 
/system/networking/wireless/networks/ATMEL/wpa_psk_wpa_version 2
gconftool-2 -t int --set 
/system/networking/wireless/networks/ATMEL/wpa_psk_key_mgt 2
gconftool-2 -t string --set 
/system/networking/wireless/networks/ATMEL/wpa_psk_key 
"96038d57c5e67f2baaadbcc8e1a3d7c5976ace82b92bd6f5fe851ca8226ebd3d"

Looks like this ..
cat %gconf.xml




96038d57c5e67f2baaadbcc8e1a3d7c5976ace82b92bd6f5fe851ca8226ebd3d









00:00:00:00:00:00







ATMEL



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

Re: dbus sleep/wake problem

[Michael Biebl]

Dawid Wróbel wrote:
> Hi,
>   It seems that nm 0.6.5 has a problem with waking up from sleep
> mode. What I did was:
> 

I can confirm that. network-mnanager-(applet) does not autoconnect after
suspend/resume.

Cheers,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

dbus sleep/wake problem

[Dawid Wróbel]

Hi,
It seems that nm 0.6.5 has a problem with waking up from sleep
mode. What I did was:

dbus-send --system
--dest=org.freedesktop.NetworkManager  /org/freedesktop/NetworkManager
org.freedesktop.NetworkManager.sleep

and then:
dbus-send --system
--dest=org.freedesktop.NetworkManager  /org/freedesktop/NetworkManager
org.freedesktop.NetworkManager.wake 

I can see in the syslog that it does wake up but doesn't connect again
to eth0, as it was connected before suspending. Nothing more
happens after the last line of this log excerpt:

May  2 18:38:15 kromka NetworkManager:   Going to sleep.
May  2 18:38:15 kromka dhclient: There is already a pid file 
/var/run/dhclient-eth0.pid with pid 19337
May  2 18:38:15 kromka dhclient: killed old client process, removed PID file
May  2 18:38:15 kromka bridge-eth0: disabling the bridge
May  2 18:38:15 kromka bridge-eth0: down
May  2 18:38:15 kromka sudo: root : TTY=unknown ; PWD=/ ; USER=cromo ; 
COMMAND=/usr/bin/claws-mail --offline
May  2 18:38:15 kromka dhclient: wifi0: unknown hardware address type 801
May  2 18:38:15 kromka dhclient: can't create 
/var/lib/dhclient/dhclient-eth0.leases: No such file or directory
May  2 18:38:15 kromka dhclient: wifi0: unknown hardware address type 801
May  2 18:38:20 kromka NetworkManager:   Waking up from sleep.
May  2 18:38:20 kromka NetworkManager:   Deactivating device ath0.
May  2 18:38:20 kromka NetworkManager:   Deactivating device eth0.
May  2 18:38:20 kromka NetworkManager:   ath0: Device is fully-supported 
using driver 'ath_pci'.
May  2 18:38:20 kromka NetworkManager:   nm_device_init(): waiting for 
device's worker thread to start
May  2 18:38:20 kromka NetworkManager:   nm_device_init(): device's 
worker thread started, continuing.
May  2 18:38:20 kromka NetworkManager:   Now managing wireless (802.11) 
device 'ath0'.
May  2 18:38:20 kromka NetworkManager:   Deactivating device ath0.
May  2 18:38:20 kromka bridge-eth0: enabling the bridge
May  2 18:38:20 kromka bridge-eth0: up
May  2 18:38:20 kromka NetworkManager:   eth0: Device is fully-supported 
using driver 'tg3'.
May  2 18:38:20 kromka NetworkManager:   nm_device_init(): waiting for 
device's worker thread to start
May  2 18:38:20 kromka NetworkManager:   nm_device_init(): device's 
worker thread started, continuing.
May  2 18:38:20 kromka NetworkManager:   Now managing wired Ethernet 
(802.3) device 'eth0'.
May  2 18:38:20 kromka NetworkManager:   Deactivating device eth0.
May  2 18:38:22 kromka tg3: eth0: Link is up at 100 Mbps, full duplex.
May  2 18:38:22 kromka tg3: eth0: Flow control is on for TX and on for RX.
May  2 18:38:22 kromka NetworkManager:   Will activate wired connection 
'eth0' because it now has a link.

After removing the cable and plugging again:
May  2 18:44:12 kromka tg3: eth0: Link is down.
May  2 18:44:17 kromka tg3: eth0: Link is up at 100 Mbps, full duplex.
May  2 18:44:17 kromka tg3: eth0: Flow control is on for TX and on for RX.
May  2 18:44:17 kromka NetworkManager:   Will activate wired connection 
'eth0' because it now has a link.

And nothing more. I have to manually click on the eth0 interface name
from the list (in knetworkmanager) to force it to query dhcp server
and connect. 
It simply seems that autoconnecting after sleep/wake is broken.

-- 
Best regards
  Dawid Wróbel  
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Request for ergonomy feature

[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

Re: Request for ergonomy feature

[Christopher Aillon]

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

Re: Request for ergonomy feature

[Christopher Aillon]

Joan B. Moreau wrote:
> Hi all,
> 
> I like the applet but here my request in terms of ergonomy:
> 
> Would it be possible to stop triggering a scan when clicking on the
> applet (which people do quite frequently to see the available networks)

How do we know what the available networks are if we don't perform 
automatic scans?
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: intel pro wireless 3945ABG + Feisty Ubuntu

[Nicolas Will]

On Wed, 2007-05-02 at 10:32 -0400, Dan Williams wrote:
> On Tue, 2007-05-01 at 07:44 -0500, Nicolas Will wrote:
> > I. wrote:
> > > Hello friends,
> > > i've just installed on my laptop Ubuntu Feisty (last version):
> > > i have a intel pro wireless 3945ABG, which ubuntu seems to
> > > detect and activate. Infact, on the Network Manager, i can
> > > see the list of wireless networks in my neighborhood. But
> > > when i try to connect, it asks for WEP key and when i type
> > > it ... it doesnt connect. Also when i try to connect to a free
> > > network (there is one here), it does not go on.
> > > So the problem is that my box notices networks, but can't
> > > connect them
> > >
> > > Seems like it does not give me an ip address.
> > >
> > > What should i do, in your opinion?
> > > Someone has this configuration  (feisty+intel pro wireless 3945abg) ?
> > >  
> > > THANKS for your help guys... :-) 
> > 
> > 
> > I am afraid that I have to "me too" this one.
> > 
> > Same setup (Feisty and intel 3945), and same results on some WEP networks.
> > 
> > WPA and WPA2 work without any issue.
> > 
> > But WEP et acting weird. My brief look at logs may point towards
> > authentication and association, but failures at the DHCP stage.
> > 
> > Going manual using the Gnome settings helps.
> > 
> > Now, I hope that this is not due to the Debian/Ubuntu tweaks to NM...
> 
> Is this with iwlwifi or the older 3945 ieee80211-based drivers?

Older.

Nico

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

program FAQ

[Chandan Apsangi]

hi i am presently working on a client-server application in linux which uses
udp as underlying protocol, and on the server side i have used the
recv_from() function which is not receiving the messages delivered to it.
and on the client side the sendto() function is getting executed. Any
suggestions??
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: intel pro wireless 3945ABG + Feisty Ubuntu

[Nicolas Will]

I. wrote:
> Hello friends,
> i've just installed on my laptop Ubuntu Feisty (last version):
> i have a intel pro wireless 3945ABG, which ubuntu seems to
> detect and activate. Infact, on the Network Manager, i can
> see the list of wireless networks in my neighborhood. But
> when i try to connect, it asks for WEP key and when i type
> it ... it doesnt connect. Also when i try to connect to a free
> network (there is one here), it does not go on.
> So the problem is that my box notices networks, but can't
> connect them
>
> Seems like it does not give me an ip address.
>
> What should i do, in your opinion?
> Someone has this configuration  (feisty+intel pro wireless 3945abg) ?
>  
> THANKS for your help guys... :-) 


I am afraid that I have to "me too" this one.

Same setup (Feisty and intel 3945), and same results on some WEP networks.

WPA and WPA2 work without any issue.

But WEP et acting weird. My brief look at logs may point towards 
authentication and association, but failures at the DHCP stage.

Going manual using the Gnome settings helps.

Now, I hope that this is not due to the Debian/Ubuntu tweaks to NM...

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

Re: Future plans?

[Andrea Dell'Amico]

On Thu, 2007-04-26 at 18:26 -0400, Sam Varshavchik wrote:

> My only other pet peeve with a NetworkManager-based setup is having to enter 
> another password after logging in, to unlock the keyring. It's completely 
> pointless, and unneeded. A passphrase-protected keyring gives no value added 
> whatsoever, that you cannot already have with a non-world readable 
> passphrase file in your own account.
> 
> Someone once suggested pam_keyring.  I gave it a try.  I installed it. There 
> was very little documentation in it to tell me how to set up the PAM config 
> files for it.  What was there, was outdated, and was no longer applicable to 
> the modern PAM.  Typical.  Tried to improvise the PAM configuration, basing 
> it on other PAM service configurations, made no difference.  Still get 
> prompted for the password, absolutely nothing in any log file I could find 
> which would tell me why pam_keyring fails or does not work.  After futzing 
> around with it for an hour or so, completely clueless, I give up.

Hmm.. The configuration phase wasn't so difficult for me, but maybe I'm
fighting with pam for too long.

What follows is my /etc/pam.d/system-auth (from a FC5, I'm using it in
my FC6 laptop without modifications). Remove the 'pam_encfs' and
'pam_ssh' entries if you don't need them.

NB: your keyring password and your login password must be the same (and
encfs and ssh-agent too, if you use them)

authrequired  pam_env.so
authoptional  pam_encfs.so
authoptional  pam_ssh.so try_first_pass
authoptional  pam_keyring.so try_first_pass
authsufficientpam_unix.so nullok try_first_pass
authrequisite pam_succeed_if.so uid >= 500 quiet
authrequired  pam_deny.so

account required  pam_unix.so
account sufficientpam_succeed_if.so uid < 500 quiet
account required  pam_permit.so

passwordrequisite pam_cracklib.so try_first_pass retry=3
passwordsufficientpam_unix.so md5 shadow nullok try_first_pass
use_authtok
passwordrequired  pam_deny.so

session required  pam_limits.so
session required  pam_unix.so
session required  pam_encfs.so
session optional  pam_ssh.so
session optional  pam_keyring.so

-- 
Andrea Dell'Amico - 


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

Re: intel pro wireless 3945ABG + Feisty Ubuntu

[Dan Williams]

On Tue, 2007-05-01 at 07:44 -0500, Nicolas Will wrote:
> I. wrote:
> > Hello friends,
> > i've just installed on my laptop Ubuntu Feisty (last version):
> > i have a intel pro wireless 3945ABG, which ubuntu seems to
> > detect and activate. Infact, on the Network Manager, i can
> > see the list of wireless networks in my neighborhood. But
> > when i try to connect, it asks for WEP key and when i type
> > it ... it doesnt connect. Also when i try to connect to a free
> > network (there is one here), it does not go on.
> > So the problem is that my box notices networks, but can't
> > connect them
> >
> > Seems like it does not give me an ip address.
> >
> > What should i do, in your opinion?
> > Someone has this configuration  (feisty+intel pro wireless 3945abg) ?
> >  
> > THANKS for your help guys... :-) 
> 
> 
> I am afraid that I have to "me too" this one.
> 
> Same setup (Feisty and intel 3945), and same results on some WEP networks.
> 
> WPA and WPA2 work without any issue.
> 
> But WEP et acting weird. My brief look at logs may point towards
> authentication and association, but failures at the DHCP stage.
> 
> Going manual using the Gnome settings helps.
> 
> Now, I hope that this is not due to the Debian/Ubuntu tweaks to NM...

Is this with iwlwifi or the older 3945 ieee80211-based drivers?

Dan


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

Re: networkmanager fails to associate (ipw3945)

[dragoran]

no it does not work with ipw3945 1.2.1
it only worked once and now it fails to connect
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: networkmanager fails to associate (ipw3945)

[dragoran]

I tested with ipw3945 1.2.1 and it works too, so it seems that this was 
a driver bug
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

networkmanager and mac80211

[dragoran]

Hello,
while testing iwlwifi I found two bugs in nm:
1) when using a mac80211 driver like iwlwifi it shows
speed : unknown for the wireless connection
2) it always reports 100% for signal strength
see http://marc.info/?l=linux-wireless&m=117809490027074&w=2
else it works fine:
detected my wpa enabled ap, asked for the password and connected.
(I was using nm 0.6.4 on FC6 x86_64)
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: networkmanager fails to associate (ipw3945)

[dragoran]

Dan Williams wrote:
>
> Can you connect to that AP with plain wpa_supplicant and the 'wext'
> driver?
>
>   
using iwlwifi 0.0.16 it works also with networkmanager now :)
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Somes questions...

[Stéphane Bauland]

Hi peoples!

I'm an enlightenment contributor, and i hope to provide a sublib for nm. 
Someone from the project already start it some times ago.

This sublib is based on your cvs trunk to be uptodate for new appening 
changes.. It's written that we need to wait the "NetworkManagerInfo 
interface to be reworked...".

I would know if this interface has been reworked or if it still in 
developpemnent courrently ?

Thanks for your futurs answers.
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Request for ergonomy feature

[Greg Oliver]

On Wed, 2007-05-02 at 09:08 +0200, Soren Hansen wrote:
> On Wed, May 02, 2007 at 02:02:12AM -0500, Greg Oliver wrote:
> > > I like the applet but here my request in terms of ergonomy:
> > > 
> > > Would it be possible to stop triggering a scan when clicking on the
> > > applet (which people do quite frequently to see the available networks)
> > > but rather put a menu item "scan for available networks" that we can
> > > click when one decide so  ?
> > I second this!  I also see that it is a very fast moving piece of
> > software, so I expect it will be there one day and can wait.  I am
> > usually wired for the speed, but would be nice on occasion when I must
> > go wireless.
> 
> 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 - 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.

-Greg

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

Re: Request for ergonomy feature

[Soren Hansen]

On Wed, May 02, 2007 at 02:02:12AM -0500, Greg Oliver wrote:
> > I like the applet but here my request in terms of ergonomy:
> > 
> > Would it be possible to stop triggering a scan when clicking on the
> > applet (which people do quite frequently to see the available networks)
> > but rather put a menu item "scan for available networks" that we can
> > click when one decide so  ?
> I second this!  I also see that it is a very fast moving piece of
> software, so I expect it will be there one day and can wait.  I am
> usually wired for the speed, but would be nice on occasion when I must
> go wireless.

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.

-- 
Mange hilsner, Søren Hansen.


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

Re: Request for ergonomy feature

[Greg Oliver]

On Wed, 2007-05-02 at 08:58 +0300, Joan B. Moreau wrote:
> Hi all,
> 
> I like the applet but here my request in terms of ergonomy:
> 
> Would it be possible to stop triggering a scan when clicking on the
> applet (which people do quite frequently to see the available networks)
> but rather put a menu item "scan for available networks" that we can
> click when one decide so  ?
> 
> Thanks
> 
> Joan

I second this!  I also see that it is a very fast moving piece of
software, so I expect it will be there one day and can wait.  I am
usually wired for the speed, but would be nice on occasion when I must
go wireless.

-Greg

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