View previous topic :: View next topic |
Author |
Message |
sog Guru
Joined: 04 Apr 2004 Posts: 356
|
Posted: Tue Mar 07, 2006 6:06 pm Post subject: |
|
|
don't know the answer to all of that, but i do not have net.eth* in my default runlevel - NM takes care of that for me _________________ ------------------------------------------------
(blog) http://www.redmonk.com/sogrady/ |
|
Back to top |
|
|
bhogg Tux's lil' helper
Joined: 29 Jun 2003 Posts: 96
|
Posted: Sun Mar 12, 2006 6:24 pm Post subject: |
|
|
Hi,
I'm trying to install networkmanager 0.6.0 (or any other version) using the gentopia ebuilds. I had to add this package and all associated ebuilds to package.keywords (am I missing something or is this always needed for gentopia stuff?), but still received the following during the configure check:
Code: | checking for syslog.h... yes
checking for unistd.h... (cached) yes
checking for mode_t... yes
checking for pid_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking whether i686-pc-linux-gnu-gcc needs -traditional... no
checking for working memcmp... yes
checking for select... yes
checking for socket... yes
checking for uname... yes
checking for intltool >= 0.27.2... 0.34.1 found
checking for perl... /usr/bin/perl
checking for XML::Parser... ok
checking for iconv... /usr/bin/iconv
checking for msgfmt... /usr/bin/msgfmt
checking for msgmerge... /usr/bin/msgmerge
checking for xgettext... /usr/bin/xgettext
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for LC_MESSAGES... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for ngettext in libc... yes
checking for dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... /usr/bin/msgfmt
checking for dcgettext... yes
checking for gmsgfmt... /usr/bin/gmsgfmt
checking for xgettext... /usr/bin/xgettext
checking for catalogs to be installed... bg bs ca cs da de el en_CA es fi fr gu hr hu it ja ko lt nb ne nl pa pt_BR rw sk sq sr sr@Latn sv uk vi wa zh_CN zh_TW
checking for wireless-tools >= 28pre9... yes
checking for i686-pc-linux-gnu-pkg-config... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for DBUS... yes
Your dbus version is 0,60,0.
checking for GTHREAD... yes
checking for GLIB... yes
checking for GMODULE... yes
checking for HAL... yes
checking for GTK... yes
checking for GDK_PIXBUF... yes
checking for GLADE... yes
checking for GCONF... yes
checking for GNOME_KEYRING... yes
checking for NOTIFY... yes
checking for LIBNL... configure: error: Package requirements (libnl-1) were not met:
No package 'libnl-1' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables LIBNL_CFLAGS
and LIBNL_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
!!! Please attach the config.log to your bug report:
!!! /var/tmp/portage/networkmanager-0.6.0/work/NetworkManager-0.6.0/config.log
!!! ERROR: net-misc/networkmanager-0.6.0 failed.
!!! Function econf, Line 495, Exitcode 0
!!! econf failed
!!! If you need support, post the topmost build error, NOT this status message.
|
Any ideas?
Brian |
|
Back to top |
|
|
seiichiro0185 Tux's lil' helper
Joined: 18 Dec 2005 Posts: 115 Location: Berlin, Germany
|
Posted: Sun Mar 12, 2006 7:32 pm Post subject: |
|
|
a simple emerge dev-libs/libnl before merging NetworkManager solved that for me (after adding libnl to package.keywords)
seiichiro0185 _________________ Desktop: AMD Athlon64 4850e@2,9GHz| 2GB RAM | 500GB HDD
Laptop: Dell Vostro 1310: C2D 2.1GHz | 4GB RAM | 250GB HDD
Server: Via C7D 1,5GHz | 512MB RAM | 1TB HDD |
|
Back to top |
|
|
bhogg Tux's lil' helper
Joined: 29 Jun 2003 Posts: 96
|
Posted: Sun Mar 12, 2006 9:13 pm Post subject: |
|
|
Thanks for the quick reply... that nearly got it working. It emerged without incident, but when nm-applet is run as a user or as root:
Code: | nm-applet
** (nm-applet:7908): WARNING **: Icon nm-no-connection missing: Icon 'nm-no-connection' not present in theme
(nm-applet:7908): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:7908): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
|
followed by a bunch more g_object_unref errors, and finally a pop-up stating certain files could not be found. Looks like it's just the display icon that's missing?
Last edited by bhogg on Sun Mar 12, 2006 9:26 pm; edited 2 times in total |
|
Back to top |
|
|
sog Guru
Joined: 04 Apr 2004 Posts: 356
|
Posted: Sun Mar 12, 2006 9:20 pm Post subject: |
|
|
run this:
gtk-update-icon-cache -f /usr/share/icons/hicolor/ _________________ ------------------------------------------------
(blog) http://www.redmonk.com/sogrady/ |
|
Back to top |
|
|
bhogg Tux's lil' helper
Joined: 29 Jun 2003 Posts: 96
|
Posted: Sun Mar 12, 2006 9:34 pm Post subject: |
|
|
Getting closer...
I found that command just before you posted the reply After starting NetworkManager and running nm-applet, the icon is displayed and is providing a list of wirless APs. But similarily to other times I've tried to get NetworkManager working (ie. SuSE, FC4, etc) it will not actually connect to the AP when the WEP key is provided (after clicking on the desired AP in the list). I'm also getting these error messages in the terminal window:
Code: | # nm-applet
** Message: <information> You are now connected to the wired network.
libnotify-Message: Unable to get session bus: Unable to determine the address of the message bus
** (nm-applet:9107): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:9107): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:9107): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
libnotify-Message: Unable to get session bus: Unable to determine the address of the message bus
** (nm-applet:9107): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:9107): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (nm-applet:9107): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed |
Obviously this app isn't even v1 yet, but does seem to have a great interface if only I could get it to actually work. Previously on other distros I managed to get it connecting to the home network, but would not grab an IP from hotspots. |
|
Back to top |
|
|
bhogg Tux's lil' helper
Joined: 29 Jun 2003 Posts: 96
|
Posted: Sun Mar 19, 2006 10:53 pm Post subject: |
|
|
Anyone know what the above errors mean, and how they can be fixed?
NetworkManager will list the AP's no problem, but will not actually connect to them. |
|
Back to top |
|
|
icantux Tux's lil' helper
Joined: 25 Sep 2005 Posts: 122
|
Posted: Mon Mar 20, 2006 3:20 pm Post subject: |
|
|
Did you try version 0.6.1? Seems 0.6.1 came out only 10 days after 0.60 was released. |
|
Back to top |
|
|
thepi Guru
Joined: 06 Jan 2004 Posts: 352 Location: Tokyo, Japan
|
Posted: Mon Mar 27, 2006 11:47 am Post subject: |
|
|
bhogg: I guess your local or global dbus session isn't running.
Make sure that dbus is in the default (NOT boot) runlevel:
Code: |
rc-update add dbus default
/etc/init.d/dbus start
|
To automatically start a local dbus session, save the following script as /etc/X11/xinit/xinitrc.d/30-dbus:
Code: |
#!/bin/bash
# launches a session dbus instance
dbuslaunch="`which dbus-launch 2>/dev/null`"
if [ -n "$dbuslaunch" ] && [ -x "$dbuslaunch" ] && [ -z "$DBUS_SESSION_BUS_ADDRESS" ]; then
eval `$dbuslaunch --sh-syntax --exit-with-session`
fi
|
hth,
pi~ _________________ Violence is the last resort of the incompetent --Isaac Asimov
Gentoo on Acer TM800 | Help! | Vote! | Get FF! |
|
Back to top |
|
|
Hazzl n00b
Joined: 03 Dec 2003 Posts: 27 Location: Berlin, Germany
|
Posted: Mon Mar 27, 2006 2:54 pm Post subject: Problems with Netorkmanager |
|
|
Since this seems to be the official NetworkManager support thread I'll post here. Any input at all would be greatly appreaciated
I can't manage to get NetworkManager to associate with my network
Code: |
Mar 27 17:51:11 [NetworkManager] <information>_starting..._
Mar 27 17:51:11 [NetworkManager] <information>_ra0: Device is fully-supported using driver 'rt2500'._
Mar 27 17:51:11 [NetworkManager] <information>_nm_device_init(): waiting for device's worker thread to start_
Mar 27 17:51:11 [NetworkManager] <information>_nm_device_init(): device's worker thread started, continuing._
Mar 27 17:51:11 [NetworkManager] <information>_Now managing wireless (802.11) device 'ra0'._
Mar 27 17:51:11 [NetworkManager] <information>_Deactivating device ra0._
Mar 27 17:51:14 [kernel] eth0: link down
Mar 27 17:51:14 [NetworkManager] <information>_eth0: Device is fully-supported using driver '8139too'._
Mar 27 17:51:14 [NetworkManager] <information>_nm_device_init(): waiting for device's worker thread to start_
Mar 27 17:51:14 [NetworkManager] <information>_nm_device_init(): device's worker thread started, continuing._
Mar 27 17:51:14 [NetworkManager] <information>_Now managing wired Ethernet (802.3) device 'eth0'._
Mar 27 17:51:14 [NetworkManager] <information>_Deactivating device eth0._
Mar 27 17:51:34 [NetworkManager] <information>_Updating allowed wireless network lists._
Mar 27 17:51:34 [NetworkManager] <information>_SWITCH: no current connection, found better connection 'ra0'._
Mar 27 17:51:34 [NetworkManager] <information>_Activated the DHCP daemon /sbin/dhcdbd with PID 5628._
Mar 27 17:51:35 [dhcdbd] Started up.
Mar 27 17:51:35 [dhcdbd] message_handler: message handler not found under /com/redhat/dhcp/ra0 for sub-path ra0.dbus.get.reason
Mar 27 17:51:35 [NetworkManager] <information>_Will activate connection 'ra0/TaipeiHOSTEL'._
Mar 27 17:51:35 [NetworkManager] <information>_Device ra0 activation scheduled..._
Mar 27 17:51:35 [NetworkManager] <information>_Activation (ra0) started..._
Mar 27 17:51:35 [NetworkManager] <information>_Activation (ra0) Stage 1 of 5 (Device Prepare) scheduled..._
Mar 27 17:51:35 [NetworkManager] <information>_Activation (ra0) Stage 1 of 5 (Device Prepare) started..._
Mar 27 17:51:35 [NetworkManager] <information>_Activation (ra0) Stage 2 of 5 (Device Configure) scheduled..._
<information>_Activation (ra0) Stage 2 of 5 (Device Configure) starting..._
Mar 27 17:51:35 [NetworkManager] <information>_Activation (ra0/wireless): access point 'TaipeiHOSTEL' is unencrypted, no key needed._
Mar 27 17:51:37 [NetworkManager] <information>_SUP: sending command 'INTERFACE_ADD ra0__wext_/var/lib/run/wpa_supplicant_'_
Mar 27 17:51:37 [NetworkManager] <information>_SUP: response was 'OK'_
Mar 27 17:51:37 [NetworkManager] <information>_SUP: sending command 'AP_SCAN 2'_Mar 27 17:51:37 [NetworkManager] <information>_SUP: response was 'OK'_
Mar 27 17:51:37 [NetworkManager] <information>_SUP: sending command 'ADD_NETWORK'_
Mar 27 17:51:37 [NetworkManager] <information>_SUP: response was '0'_
Mar 27 17:51:37 [NetworkManager] <information>_SUP: sending command 'SET_NETWORK 0 ssid 546169706569484f5354454c'_
Mar 27 17:51:37 [NetworkManager] <information>_SUP: response was 'OK'_
Mar 27 17:51:37 [NetworkManager] <information>_SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'_
Mar 27 17:51:37 [NetworkManager] <information>_SUP: response was 'OK'_
Mar 27 17:51:37 [NetworkManager] <information>_SUP: sending command 'ENABLE_NETWORK 0'_
Mar 27 17:51:37 [NetworkManager] <information>_SUP: response was 'OK'_
Mar 27 17:51:37 [NetworkManager] <information>_Activation (ra0) Stage 2 of 5 (Device Configure) complete._
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Global control interface '/var/lib/run/wpa_supplicant-global'_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): RX global ctrl_iface - hexdump_ascii(len=52):_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): 49 4e 54 45 52 46 41 43 45 5f 41 44 44 20 72 61 INTERFACE_ADD ra_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): 30 09 09 77 65 78 74 09 2f 76 61 72 2f 6c 69 62 0__wext_/var/lib_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): 2f 72 75 6e 2f 77 70 61 5f 73 75 70 70 6c 69 63 /run/wpa_supplic_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): 61 6e 74 09 ant_ _
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): CTRL_IFACE GLOBAL INTERFACE_ADD 'ra0__wext_/var/lib/run/wpa_supplicant_'_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Initializing interface 'ra0' conf 'N/A' driver 'wext' ctrl_interface '/var/lib/run/wpa_supplicant' bridge 'N/A'_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Initializing interface (2) 'ra0'_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): EAPOL: SUPP_PAE entering state DISCONNECTED_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): EAPOL: KEY_RX entering state NO_KEY_RECEIVE_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): EAPOL: SUPP_BE entering state INITIALIZE_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): EAP: EAP entering state DISABLED_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): EAPOL: External notification - portEnabled=0_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): EAPOL: External notification - portValid=0_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): SIOCGIWRANGE: WE(compiled)=19 WE(source)=14 enc_capa=0x0_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): capabilities: key_mgmt 0x0 enc 0x3_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Own MAC address: 00:11:09:17:24:12_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): wpa_driver_wext_set_wpa_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): does not support WPA._
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): wpa_driver_wext_set_countermeasures_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): wpa_driver_wext_set_drop_unencrypted_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Setting scan request: 0 sec 100000 usec_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Added interface ra0_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): RX ctrl_iface - hexdump_ascii(len=9):_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): 41 50 5f 53 43 41 4e 20 32 AP_SCAN 2 _
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): RX ctrl_iface - hexdump_ascii(len=11):_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): 41 44 44 5f 4e 45 54 57 4f 52 4b ADD_NETWORK _
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): CTRL_IFACE: ADD_NETWORK_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): RX ctrl_iface - hexdump_ascii(len=43): [REMOVED]_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): CTRL_IFACE: SET_NETWORK id=0 name='ssid'_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): _IFACE: value - hexdump_ascii(len=24): [REMOVED]_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): ssid - hexdump_ascii(len=12):_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): 54 61 69 70 65 69 48 4f 53 54 45 4c TaipeiHOSTEL _
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): RX ctrl_iface - hexdump_ascii(len=27): [REMOVED]_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): CTRL_IFACE: SET_NETWORK id=0 name='key_mgmt'_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): CTRL_IFACE: value - hexdump_ascii(len=4): [REMOVED]_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): key_mgmt: 0x4_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): RX ctrl_iface - hexdump_ascii(len=16):_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): 45 4e 41 42 4c 45 5f 4e 45 54 57 4f 52 4b 20 30 ENABLE_NETWORK 0_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): CTRL_IFACE: ENABLE_NETWORK id=0_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Setting scan request: 0 sec 0 usec_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): State: DISCONNECTED -> SCANNING_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Trying to associate with SSID 'TaipeiHOSTEL'_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Cancelling scan request_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): WPA: clearing own WPA/RSN IE_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Automatic auth_alg selection: 0x1_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): WPA: clearing AP WPA IE_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): WPA: clearing AP RSN IE_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): No keys have been configured - skip key clearing_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): wpa_driver_wext_set_drop_unencrypted_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): State: SCANNING -> ASSOCIATING_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): wpa_driver_wext_associate_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): WEXT: Driver did not support SIOCSIWAUTH for AUTH_ALG, trying SIOCSIWENCODE_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Association request to the driver failed_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): sec 0 usec_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): EAPOL: External notification - portControl=ForceAuthorized_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): CTRL_IFACE monitor attached - hexdump(len=44): 2f 76 61 72 2f 6c 69 62 2f 72 75 6e 2f 4e 65 74 77 6f 72 6b 4d 61 6e 61 67 65 72 2f 77 70 61 5f 63 74 72 6c 5f 35 34 37 37 2d 31 00_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Authentication with 00:00:00:00:00:00 timed out._
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): CTRL_IFACE monitor send - hexdump(len=44): 2f 76 61 72 2f 6c 69 62 2f 72 75 6e 2f 4e 65 74 77 6f 72 6b 4d 61 6e 61 67 65 72 2f 77 70 61 5f 63 74 72 6c 5f 35 34 37 37 2d 31 00_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Added BSSID 00:00:00:00:00:00 into blacklist_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): State: ASSOCIATING -> DISCONNECTED_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): No keys have been configured - skip key clearing_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): EAPOL: External notification - portEnabled=0_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): EAPOL: External notification - portValid=0_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Setting scan request: 0 sec 0 usec_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): State: DISCONNECTED -> SCANNING_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Trying to associate with SSID 'TaipeiHOSTEL'_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): CTRL_IFACE monitor send - hexdump(len=44): 2f 76 61 72 2f 6c 69 62 2f 72 75 6e 2f 4e 65 74 77 6f 72 6b 4d 61 6e 61 67 65 72 2f 77 70 61 5f 63 74 72 6c 5f 35 34 37 37 2d 31 00_
Mar 27 17:51:42 [NetworkManager] <information>_wpa_supplicant(5635): Cancelling scan request_
Mar 27 17:51:57 [NetworkManager] <information>_Activation (ra0/wireless): association took too long (>20s), failing activation._
Mar 27 17:51:57 [NetworkManager] <information>_Activation (ra0) failure scheduled..._
Mar 27 17:51:57 [NetworkManager] <information>_Activation (ra0) failed for access point (TaipeiHOSTEL)_
Mar 27 17:51:57 [NetworkManager] <information>_Activation (ra0) failed._
Mar 27 17:51:57 [NetworkManager] <information>_Deactivating device ra0._
|
Does anybody have an idea why it is failing? I don't even know what to check based on this output. The only thing looking like an error message is this notice about
Code: |
message handler not found under /com/redhat/dhcp/ra0 for sub-path ra0.dbus.get.reason
|
I have no problems associating witht that network using dhcpcd. |
|
Back to top |
|
|
neonblind n00b
Joined: 13 Nov 2004 Posts: 47
|
Posted: Tue Apr 11, 2006 5:20 pm Post subject: |
|
|
well, thanks to this thread I got networkmanager to run properly except for one thing: dhcp won't work. I've tried just about anything I can think of, but still, no luck...
here is the log:
Quote: | Apr 11 18:59:08 Schweizer NetworkManager: <information> Activation (eth1) Beginning DHCP transaction.
Apr 11 18:59:08 Schweizer dhcdbd: Unrequested down ?:2
Apr 11 18:59:08 Schweizer dhclient: Internet Systems Consortium DHCP Client V3.0.3-Gentoo-r6
Apr 11 18:59:08 Schweizer dhclient: Copyright 2004-2005 Internet Systems Consortium.
Apr 11 18:59:08 Schweizer dhclient: All rights reserved.
Apr 11 18:59:08 Schweizer dhclient: For info, please visit http://www.isc.org/products/DHCP
Apr 11 18:59:08 Schweizer dhclient: Usage: dhclient [-1dqr] [-nw] [-p <port>] [-s server]
Apr 11 18:59:08 Schweizer dhclient: [-cf config-file] [-lf lease-file][-pf pid-file] [-e VAR=val]
Apr 11 18:59:08 Schweizer dhclient: [-sf script-file] [interface]
Apr 11 18:59:08 Schweizer dhclient: exiting.
Apr 11 18:59:08 Schweizer NetworkManager: <information> DHCP daemon state is now 14 (normal exit) for interface eth1 |
this is networkmanager-0.6.2
any ideas?
thanks in advance! |
|
Back to top |
|
|
seiichiro0185 Tux's lil' helper
Joined: 18 Dec 2005 Posts: 115 Location: Berlin, Germany
|
Posted: Tue Apr 11, 2006 5:43 pm Post subject: |
|
|
make sure you use dhcp from the gentopia overlay and have dbus USE-flag enabled, I had the same message with dhcp from portage and without dbus in USE for dhcp.
seiichiro0185 _________________ Desktop: AMD Athlon64 4850e@2,9GHz| 2GB RAM | 500GB HDD
Laptop: Dell Vostro 1310: C2D 2.1GHz | 4GB RAM | 250GB HDD
Server: Via C7D 1,5GHz | 512MB RAM | 1TB HDD |
|
Back to top |
|
|
neonblind n00b
Joined: 13 Nov 2004 Posts: 47
|
Posted: Tue Apr 11, 2006 6:55 pm Post subject: |
|
|
thanks! that did it!
but now, it seems that dhcp does not get any response from the router.
here is the log:
Code: | Apr 11 20:40:53 Schweizer NetworkManager: <information> DHCP daemon state is now 1 (starting) for interface eth1
Apr 11 20:40:53 Schweizer dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
Apr 11 20:40:58 Schweizer dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
Apr 11 20:41:03 Schweizer dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
Apr 11 20:41:08 Schweizer dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
Apr 11 20:41:18 Schweizer dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 17
Apr 11 20:41:35 Schweizer dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 16
Apr 11 20:41:38 Schweizer NetworkManager: <information> Device 'eth1' DHCP transaction took too long (>45s), stopping it.
Apr 11 20:41:39 Schweizer NetworkManager: <information> Activation (eth1) Stage 4 of 5 (IP Configure Timeout) scheduled...
Apr 11 20:41:39 Schweizer NetworkManager: <information> DHCP daemon state is now 14 (normal exit) for interface eth1
Apr 11 20:41:39 Schweizer NetworkManager: <information> DHCP daemon state is now 14 (normal exit) for interface eth1
Apr 11 20:41:39 Schweizer NetworkManager: <information> Activation (eth1) Stage 4 of 5 (IP Configure Timeout) started...
Apr 11 20:41:39 Schweizer NetworkManager: <debug info> [1144780899.963449] real_act_stage4_ip_config_timeout (): Activation (eth1/wireless): could not get IP configuration info for 'Heikes', asking for new key.
Apr 11 20:41:39 Schweizer NetworkManager: <information> Activation (eth1) New wireless user key requested for network 'Heikes'.
Apr 11 20:41:39 Schweizer NetworkManager: <information> Activation (eth1) Stage 4 of 5 (IP Configure Timeout) complete.
Apr 11 20:41:41 Schweizer NetworkManager: <WARNING> nm_dbus_get_user_key_for_network_cb (): nm_dbus_get_user_key_for_network_cb(): dbus returned an error. (org.freedesktop.DBus.Error.NoReply) Message did not receive a reply (timeout by message bus)
Apr 11 20:41:41 Schweizer NetworkManager: <information> Deactivating device eth1. |
this is rather strange since it works when running dhclient "manually" via Code: | /etc/init.d/net.eth1 start
* Caching service dependencies ... [ ok ]
* Starting eth1
* Configuring wireless network for eth1
* eth1 connected to ESSID "Heikes" at 00:01:E3:42:09:CF
* in managed mode on channel 11 (WEP enabled - open)
* Configuration not set for eth1 - assuming DHCP
* Bringing up eth1
* dhcp
* Running dhclient ... [ ok ]
* eth1 received address 192.168.1.8/24 |
am I missing something?
thanks again... |
|
Back to top |
|
|
vladanian n00b
Joined: 17 Aug 2005 Posts: 3 Location: San Francisco, CA
|
Posted: Mon May 01, 2006 5:20 pm Post subject: dhcp isn't in gentopia |
|
|
I'm having trouble with dhcp and networkmanager from gentopia -- I've seen this suggestion about using dhcp from gentopia's overlay, but there's no dhcp in gentopia's overlay right now. Right? |
|
Back to top |
|
|
seiichiro0185 Tux's lil' helper
Joined: 18 Dec 2005 Posts: 115 Location: Berlin, Germany
|
Posted: Mon May 01, 2006 8:23 pm Post subject: |
|
|
just checked gentopia overlay and you are right, there is no ebuild for dhcp in gentopia right now. I dont know which dhcp version is supposed to work with NM or why they took it out.
[UPDATE] dhcp-3.0.3_p1 from BreakMyGentoo overlay works with networkmanager [/UPDATE]
seiichiro0185 _________________ Desktop: AMD Athlon64 4850e@2,9GHz| 2GB RAM | 500GB HDD
Laptop: Dell Vostro 1310: C2D 2.1GHz | 4GB RAM | 250GB HDD
Server: Via C7D 1,5GHz | 512MB RAM | 1TB HDD |
|
Back to top |
|
|
UberLord Retired Dev
Joined: 18 Sep 2003 Posts: 6835 Location: Blighty
|
|
Back to top |
|
|
vladanian n00b
Joined: 17 Aug 2005 Posts: 3 Location: San Francisco, CA
|
Posted: Tue May 02, 2006 8:25 pm Post subject: bmg's dhcp didn't do it |
|
|
The gentopia guys might be right, because bmg's dhcp didn't fix my problem. I'm failing to get an IP address from my router in exactly the same way I was with the most recent portage dhcp.
One thing -- when dbus starts, it complains about unknown user "named" -- I don't know if this has anything to do with the trouble I'm having...
sudo /etc/init.d/dbus restart
* Stopping NetworkManager ... [ ok ]
* Stopping dhcdbd ... [ ok ]
* Stopping Hardware Abstraction Layer daemon ... [ ok ]
* Stopping D-BUS system messagebus ... [ ok ]
* Starting D-BUS system messagebus ...
Unknown username "named" in message bus configuration file [ ok ]
* Starting dhcdbd ... [ ok ]
* Starting Hardware Abstraction Layer daemon ... [ ok ]
* Starting NetworkManager ... [ ok ] |
|
Back to top |
|
|
vladanian n00b
Joined: 17 Aug 2005 Posts: 3 Location: San Francisco, CA
|
Posted: Tue May 09, 2006 1:18 am Post subject: the solution to my wifi+networkmanager problem |
|
|
In case anyone has the same wifi+networkmanager+dhcp problem I did, my solution was upgrading to the ~x86 wpa_supplicant, net-wireless/wpa_supplicant-0.5.3.
I don't think the missing named user had anything to do with it, but I created one to match the named user on one of my dapper drake boxes anyway. |
|
Back to top |
|
|
Stormblazer Tux's lil' helper
Joined: 28 Jan 2005 Posts: 76 Location: Colorado
|
Posted: Sun Jul 09, 2006 2:03 am Post subject: |
|
|
Same problem it won't connect, but I don't use DHCP (don't ask me too, I personally hate dhcp with a passion, simply because it gets in the way of everything, especially port forwarding).
I can get the applet to load and it lists connections etc, it just refuses to connect. _________________ The vast majority of errors are stupid mistakes that you end up kicking yourself for later. |
|
Back to top |
|
|
tane_stelzer Apprentice
Joined: 30 Dec 2005 Posts: 263 Location: Edinburgh, Scotland and Kempen, Germany
|
|
Back to top |
|
|
tomkro n00b
Joined: 10 Jul 2006 Posts: 7 Location: Ffm
|
Posted: Tue Jul 18, 2006 6:52 am Post subject: |
|
|
hi,
I got the same problem. netwokmanager lists the interfaces but gives me always an IP: 169.x.x.x where it should be 192.168.x.x. When I ran dhclient manually from command prommt it gives the correct IP and I am connectet.
Any ideas?
Thanks.
tom |
|
Back to top |
|
|
frozenJim Guru
Joined: 18 Jun 2004 Posts: 341 Location: Montreal, Quebec, Canada
|
Posted: Thu Jul 20, 2006 9:22 pm Post subject: Will it ever be in Portage? |
|
|
These NetworkManager threads have been around since 2002. Originally the problem was something to do with the "gentoo backend" not being compatible (or some such techno-jargon). Apparently that is no longer the case.
Uberlord wrote: | dhcp-3.0.3-r7 and newer in Gentoo's portage work with NetworkManager. At least that's what one of the Gentopia guys told me. |
Does anyone know if a package is being prepared for Portage? I am green with envy when I see my colleagues running netmanager on their "lesser distros" and switching effortlessly from cat5 to wifi to cat5 on ANOTHER network, with just the click of a mouse... Meantime, I site here and tweak my net.eth0 and resolv.conf files like a troglodyte just to get my day started on my at-work network .
I'm not quite willing to go the BMG or Gentopia routes, I will wait until it is at LEAST masked ~x86.
Is anyone working on it, and is it a realistic hope? _________________ Who controls the past, controls the future. Who controls the present, controls the past. |
|
Back to top |
|
|
UberLord Retired Dev
Joined: 18 Sep 2003 Posts: 6835 Location: Blighty
|
Posted: Fri Jul 21, 2006 9:25 am Post subject: Re: Will it ever be in Portage? |
|
|
frozenJim wrote: | Does anyone know if a package is being prepared for Portage? I am green with envy when I see my colleagues running netmanager on their "lesser distros" and switching effortlessly from cat5 to wifi to cat5 on ANOTHER network, with just the click of a mouse... |
My colleagues go green with envy that my networking just works without any mouse clicks
Quote: | Meantime, I site here and tweak my net.eth0 and resolv.conf files like a troglodyte just to get my day started on my at-work network . |
So look into netplug, wpa_supplicant, resolvconf-gentoo and baselayout-1.12.1 - those are the tools you need for NetworkManager functionality without the GUI.
The only step we currently lack is a GUI to set things up - but once things are setup it's just a case of watching the interfaces come up and work in whichever environment you are in. I take my laptop around a lot, and it works in all locations. The first time I changed network settings was when I went to the Gentoo UK conference - and that was just informing wpa_supplicant about a new access point and WEP key.
Quote: | I'm not quite willing to go the BMG or Gentopia routes, I will wait until it is at LEAST masked ~x86.
Is anyone working on it, and is it a realistic hope? |
People are working on it - go bug steev on one of our many IRC channels. _________________ Use dhcpcd for all your automated network configuration needs
Use dhcpcd-ui (GTK+/Qt) as your System Tray Network tool |
|
Back to top |
|
|
sepp Guru
Joined: 11 Jul 2002 Posts: 330
|
Posted: Mon Jul 31, 2006 8:22 pm Post subject: |
|
|
It seems like network manager is only good for managing dhcp networks. but how about custom configured wired connections? I often shift places with my laptop but need to have a fixed IP at those places. dhcd is not an option. so network manger won't help me here, right? |
|
Back to top |
|
|
UberLord Retired Dev
Joined: 18 Sep 2003 Posts: 6835 Location: Blighty
|
Posted: Tue Aug 01, 2006 8:45 am Post subject: |
|
|
sepp wrote: | It seems like network manager is only good for managing dhcp networks. but how about custom configured wired connections? I often shift places with my laptop but need to have a fixed IP at those places. dhcd is not an option. so network manger won't help me here, right? |
Correct.
However, all is not lost as Gentoo's network scripts support arping. So provided there is an fixed IP unqiue to each network like say a gateway/router then you can configure IP, dns, routing and anything else we support quite easily _________________ Use dhcpcd for all your automated network configuration needs
Use dhcpcd-ui (GTK+/Qt) as your System Tray Network tool |
|
Back to top |
|
|
|