RE: Emergency: Problems on NetworkManager 0.7.0. (Errors occured in Activation Stage 3 about DHClien
- From: Dan Williams <dcbw redhat com>
- To: Jue Yang <shuangfeiyu hotmail com>
- Cc: "networkmanager-list gnome org" <networkmanager-list gnome org>
- Subject: RE: Emergency: Problems on NetworkManager 0.7.0. (Errors occured in Activation Stage 3 about DHClien
- Date: Fri, 04 Apr 2008 15:19:10 -0400
On Wed, 2008-04-02 at 07:27 +0000, Jue Yang wrote:
> Hi,
>
> Sorry, I made a mistake. I used the word 'priority' as 'property'. :$
Ah, no problem :)
>
>
>
>
>
> ______________________________________________________________
> From: shuangfeiyu hotmail com
> To: dcbw redhat com; networkmanager-list gnome org
> Subject: RE: Emergency: Problems on NetworkManager 0.7.0.
> (Errors occured in Activation Stage 3 about DHClien
> Date: Wed, 2 Apr 2008 03:57:50 +0000
>
> Hi,
>
> I still have some questions about NMAccessPoint object.
>
> (1) NMclien and NMManager are share and operating the same
> NMAccessPoint object for a special AP?
> But manager different private structures?
So NM exports a D-Bus API, which is just Inter-Process Communications
kind of like DCOM, CORBA, etc. It exports "objects" that provide
"interfaces". The objects that NM exports are things like Devices,
AccessPoints, and Connections.
libnm-glib (and thus NMClient) are mainly a convenience wrapper over the
D-Bus interface to make it easier for programs that are based on glib to
work with NetworkManager. You could also skip libnm-glib and just talk
directly to D-Bus, but I believe that libnm-glib does save you a lot of
time if you are using glib to write your application.
As a consumer of the NetworkManager APIs, you only really care about the
D-Bus interface that NM exports, and also the API of libnm-glib.
> (2) When NMManager changes priorities of NMAccessPoint object,
> 'g_object_notity' will update the paramspec for the object.
> So when NMClient call function 'nm_object_get_byte_property',
> it can get correct value of the priority. Thus far I can
> understand.
> How can NMClient get correct 'strength' value from its
> private while not calling 'nm_object_get_byte_property'?
Mostly correct... The AP object that NetworkManager exports over D-Bus
has a number of properties, one of which is "strength". There are _two_
ways for libnm-glib's NMAccessPoint class to get the strength of the
object it wraps: calling the GetProperty() method of the AP object, or
listening for signals that NM emits when that property changes.
libnm-glib will generally call GetProperty() the first time the property
is requested by the caller. After that, it will only listen for signals
from NetworkManager. This reduces latency, since the value is cached
locally in libnm-glib (and thus libnm-glib doesn't have to ask NM for it
every time), and reduces the changes for the caller (your program) to
block on the D-Bus call.
Dan
>
>
> ______________________________________________________________
>
> > Subject: Re: FW: Emergency: Problems on NetworkManager
> 0.7.0. (Errors occured in Activation Stage 3 about DHClien
> > From: dcbw redhat com
> > To: shuangfeiyu hotmail com
> > CC: networkmanager-list gnome org
> > Date: Tue, 1 Apr 2008 17:21:32 -0400
> >
> > On Tue, 2008-04-01 at 04:11 +0000, Jue Yang wrote:
> > > Hi,
> > >
> > > I tried wpa_supplicant-0.5.7-21.fc8 and creating an
> network is
> > > OK now. Thanks a lot!
> > >
> > > During my development I need to add a priority to access
> > > point. I have followed the way of priority 'strength', but
> > > below error occurs.
> >
> > NM implements access point priority by a "last connected"
> metric, by
> > default trying the access point you last successfully
> connected to.
> > There is intentionally no "priority" field and users should
> not need to
> > manually re-order their connections.
> >
> > > Where can I check "org.freedesktop.DBus.Properties"?
> >
> > It's a standard D-Bus interface that all the NetworkManager
> objects
> > implement. It just allows the caller to grab properties off
> the object
> > using a defined mechanism.
> >
> > > What do those numbers with red color mean?
> > >
> > >
> > > ** (nm-applet:14225): WARNING **: nm_object_get_property:
> > > Error getting 'Ssid' for /: Method "Get" with signature
> "ss"
> > > on interface "org.freedesktop.DBus.Properties" doesn't
> exist
> >
> > This one is a bug, an object path of "/" should mean NULL.
> I'll fix
> > this, an object path of "/" should _never_ leak out of
> libnm-glib.
> >
> > > **: nm_object_get_property: Error getting 'Mesh'
> > > for /org/freedesktop/NetworkManager/AccessPoint/4: Method
> > > "Get" with signature "ss" on interface
> > > "org.freedesktop.DBus.Properties" doesn't exist
> >
> > This means that libnm-glib hasn't disposed of an access
> point that NM no
> > longer knows about. I think what's happening here is that
> reference
> > counting in the calling program isn't quite correct, and the
> caller is
> > using the AP after it's supposed to be gone.
> >
> > What sorts of things are you attempting to do here? I assume
> you're
> > reading the properties off the AP, are you doing this when
> the AP
> > appears, in response to a signal from the libnm-glib
> > NMDevice80211Wireless object, or some other way? Is your
> program
> > holding on to the AP after the signal saying the AP has
> disappeared
> > comes to your program?
> >
> > Dan
> >
> >
> > > > Subject: RE: Emergency: Problems on NetworkManager
> 0.7.0.
> > > (Errors occured in Activation Stage 3 about DHClien
> > > > From: dcbw redhat com
> > > > To: shuangfeiyu hotmail com
> > > > Date: Mon, 31 Mar 2008 14:22:28 -0400
> > > >
> > > > On Sun, 2008-03-30 at 08:39 +0000, Jue Yang wrote:
> > > > >
> > > > > Hi,
> > > > > The situation now confused me. The logs for creating a
> new
> > > network are
> > > > > below:
> > > >
> > > > You may have the wrong version of wpa_supplicant
> installed,
> > > you need a
> > > > fairly recent one that supports the 'frequency' option.
> What
> > > version of
> > > > wpa_supplicant do you currently have installed?
> > > >
> > > > Dan
> > > >
> > > > > Mar 31 16:22:02 localhost NetworkManager: <info>
> > > Activating device
> > > > > wlan0
> > > > > Mar 31 16:22:02 localhost NetworkManager: <info>
> > > Activation (wlan0)
> > > > > Stage 1 of 5 (Device Prepare) scheduled...
> > > > > Mar 31 16:22:02 localhost NetworkManager: <info>
> > > Activation (wlan0)
> > > > > Stage 1 of 5 (Device Prepare) started...
> > > > > Mar 31 16:22:02 localhost NetworkManager: <info>
> > > Activation (wlan0)
> > > > > Stage 2 of 5 (Device Configure) scheduled...
> > > > > Mar 31 16:22:02 localhost NetworkManager: <info>
> > > Activation (wlan0)
> > > > > Stage 1 of 5 (Device Prepare) complete.
> > > > > Mar 31 16:22:02 localhost NetworkManager: <info>
> > > Activation (wlan0)
> > > > > Stage 2 of 5 (Device Configure) starting...
> > > > > Mar 31 16:22:02 localhost NetworkManager: <info>
> > > Activation
> > > > > (wlan0/wireless): connection 'Auto yangjue_3' requires
> no
> > > security.
> > > > > No secrets needed.
> > > > > Mar 31 16:22:02 localhost NetworkManager: <info>
> Config:
> > > added 'ssid'
> > > > > value 'yangjue_3'
> > > > > Mar 31 16:22:02 localhost NetworkManager: <info>
> Config:
> > > added 'mode'
> > > > > value '1'
> > > > > Mar 31 16:22:02 localhost NetworkManager: <info>
> Config:
> > > added
> > > > > 'frequency' value '2462'
> > > > > Mar 31 16:22:02 localhost NetworkManager: <info>
> Config:
> > > added
> > > > > 'key_mgmt' value 'NONE'
> > > > > Mar 31 16:22:02 localhost NetworkManager: <info>
> > > Activation (wlan0)
> > > > > Stage 2 of 5 (Device Configure) complete.
> > > > > Mar 31 16:22:02 localhost NetworkManager: <info>
> Config:
> > > set
> > > > > interface ap_scan to 2
> > > > > Mar 31 16:22:02 localhost NetworkManager: <WARN>
> > > set_network_cb():
> > > > > Couldn't set network config: Did not receive correct
> > > message
> > > > > arguments..
> > > > > Mar 31 16:22:02 localhost NetworkManager: <info>
> > > Activation
> > > > > (wlan0/wireless): association request to the
> supplicant
> > > failed:
> > > > > fi.epitest.hostap.WPASupplicant.InvalidOptions - Did
> not
> > > receive
> > > > > correct message arguments.
> > > > > Mar 31 16:22:02 localhost NetworkManager: <info>
> > > Activation (wlan0)
> > > > > failed for access point (yangjue_3)
> > > > > Mar 31 16:22:02 localhost NetworkManager: <info>
> Marking
> > > connection
> > > > > 'Auto yangjue_3' invalid.
> > > > > Mar 31 16:22:02 localhost NetworkManager: <info>
> > > Activation (wlan0)
> > > > > failed.
> > > > > Mar 31 16:22:02 localhost NetworkManager: <info>
> > > Deactivating device
> > > > > wlan0.
> > > > > Mar 31 16:22:02 localhost kernel: rtl8187: Setting SW
> wep
> > > key
> > > > > Mar 31 16:27:32 localhost kernel: usb 3-2: new full
> speed
> > > USB device
> > > > > using uhci_hcd and address 2
> > > > > Mar 31 16:27:32 localhost kernel: usb 3-2:
> configuration
> > > #1 chosen
> > > > > from 1 choice
> > > > > Mar 31 16:27:32 localhost kernel: Initializing USB
> Mass
> > > Storage
> > > > > driver...
> > > > >
> > > > > What's the red line stands for? And how can I solve
> it?
> > > > >
> > > > >
> > > > >
> > > > >
> > >
> ______________________________________________________________________
> > > > >
> > > > > > Subject: Re: Emergency: Problems on NetworkManager
> > > 0.7.0. (Errors
> > > > > occured in Activation Stage 3 about DHClient.)
> > > > > > From: dcbw redhat com
> > > > > > To: shuangfeiyu hotmail com
> > > > > > CC: networkmanager-list gnome org
> > > > > > Date: Fri, 28 Mar 2008 09:50:12 -0400
> > > > > >
> > > > > > On Fri, 2008-03-28 at 07:41 +0000, Jue Yang wrote:
> > > > > > > hi,
> > > > > > >
> > > > > > > I am now in trouble. Could anybody can tell me
> what
> > > causes the
> > > > > error
> > > > > > > as follows.
> > > > > >
> > > > > > So you appear to be running with SELinux in
> enforcing
> > > mode. That
> > > > > should
> > > > > > normally work on Fedora 8 and Fedora 9 at least,
> with
> > > the latest
> > > > > > 'selinux-policy-targeted' package. Otherwise, you
> may
> > > need to
> > > > > relabel
> > > > > > your drive, sometimes that gets screwed up. You have
> two
> > > ways of
> > > > > > relabeling:
> > > > > >
> > > > > > 1) add 'autorelabel' to the kernel command line in
> GRUB
> > > > > >
> > > > > > 2) as root, 'touch /.autorelabel'
> > > > > >
> > > > > > Let me know if that helps. What version of
> > > selinux-policy-targeted
> > > > > do
> > > > > > you have installed, and whats the output of
> 'getenforce'
> > > when run as
> > > > > > root?
> > > > > >
> > > > > > Dan
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > >
> ______________________________________________________________________
> > > > > In a rush? Get real-time answers with Windows Live
> > > Messenger.
> > > >
> > >
> > >
> > >
> > >
> ______________________________________________________________
> > > Windows Live Hotmail is giving away Zunes. Enter for your
> > > chance to win.
> > >
> > >
> > >
> ______________________________________________________________________
> > > Windows Live Hotmail is giving away Zunes. Enter for your
> chance to
> > > win.
> > > _______________________________________________
> > > NetworkManager-list mailing list
> > > NetworkManager-list gnome org
> > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> >
>
>
>
> ______________________________________________________________
> Get in touch in an instant. Get Windows Live Messenger now.
>
>
> ______________________________________________________________________
> Going green? See the top 12 foods to eat organic.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
