Re: NM Drops Connections
On 7/4/06, jim lawrence <[EMAIL PROTECTED]> wrote: > Updated to kernel 2.6.17-1.2139_FC5 & have NetowrkManager version > NetworkManager-0.6.3-1.fc5 > > > Updated the Firmware to 3.0 cuz the 2.4 would not work with the > newer kernel. > > I have a dump from /var/log/messages if needed where it shows all is > well and a hour later drops the connection. I then have to add my AP > again. also is there a way of running NetworkManager --No Daemon and pipe to a text file while it is running ? -- Registered Linux User: #376813 www.fedorajim.homelinux.com ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NM Drops Connections
Updated to kernel 2.6.17-1.2139_FC5 & have NetowrkManager version NetworkManager-0.6.3-1.fc5 Updated the Firmware to 3.0 cuz the 2.4 would not work with the newer kernel. I have a dump from /var/log/messages if needed where it shows all is well and a hour later drops the connection. I then have to add my AP again. -- Registered Linux User: #376813 www.fedorajim.homelinux.com Jul 4 10:29:26 localhost NetworkManager: Retrieved the following IP4 configuration from the DHCP daemon: Jul 4 10:29:26 localhost NetworkManager:address 192.168.1.51 Jul 4 10:29:26 localhost NetworkManager:netmask 255.255.255.0 Jul 4 10:29:26 localhost NetworkManager:broadcast 192.168.1.255 Jul 4 10:29:26 localhost NetworkManager:gateway 192.168.1.49 Jul 4 10:29:26 localhost NetworkManager:nameserver 24.92.226.9 Jul 4 10:29:26 localhost NetworkManager:nameserver 24.92.226.102 Jul 4 10:29:26 localhost NetworkManager:domain name 'rochester.rr.com' Jul 4 10:29:26 localhost NetworkManager: Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... Jul 4 10:29:26 localhost NetworkManager: Activation (eth0) Stage 4 of 5 (IP Configure Get) complete. Jul 4 10:29:26 localhost NetworkManager: Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... Jul 4 10:29:26 localhost dhclient: bound to 192.168.1.51 -- renewal in 35355 seconds. Jul 4 10:29:27 localhost NetworkManager: Activation (eth0) successful, device activated. Jul 4 10:29:27 localhost NetworkManager: Activation (eth0) Finish handler scheduled. Jul 4 10:29:27 localhost NetworkManager: Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. Jul 4 11:27:33 localhost named[1664]: listening on IPv4 interface eth0, 192.168.1.51#53 Jul 4 11:31:24 localhost gconfd (root-3054): starting (version 2.14.0), pid 3054 user 'root' Jul 4 11:31:25 localhost gconfd (root-3054): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 Jul 4 11:31:25 localhost gconfd (root-3054): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1 Jul 4 11:31:25 localhost gconfd (root-3054): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2 Jul 4 11:31:26 localhost bonobo-activation-server (root-3057): Duff env. var '' Jul 4 11:31:55 localhost gconfd (root-3054): GConf server is not in use, shutting down. Jul 4 11:31:55 localhost gconfd (root-3054): Exiting Jul 4 11:53:48 localhost NetworkManager: SWITCH: terminating current connection 'eth0' because it's no longer valid. Jul 4 11:53:48 localhost NetworkManager: Deactivating device eth0. Jul 4 11:53:48 localhost dhclient: DHCPRELEASE on eth0 to 192.168.1.49 port 67 Jul 4 11:53:51 localhost NetworkManager: nm_device_is_802_3_ethernet: assertion `dev != NULL' failed Jul 4 11:53:51 localhost NetworkManager: nm_device_is_802_11_wireless: assertion `dev != NULL' failed Jul 4 11:54:14 localhost NetworkManager: User Switch: /org/freedesktop/NetworkManager/Devices/eth0 / HomeWireless Jul 4 11:54:14 localhost NetworkManager: Deactivating device eth0. Jul 4 11:54:16 localhost NetworkManager: Device eth0 activation scheduled... Jul 4 11:54:16 localhost NetworkManager: Activation (eth0) started... Jul 4 11:54:16 localhost NetworkManager: Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... Jul 4 11:54:16 localhost NetworkManager: Activation (eth0) Stage 1 of 5 (Device Prepare) started... Jul 4 11:54:16 localhost NetworkManager: Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... Jul 4 11:54:16 localhost NetworkManager: Activation (eth0) Stage 1 of 5 (Device Prepare) complete. Jul 4 11:54:16 localhost NetworkManager: Activation (eth0) Stage 2 of 5 (Device Configure) starting... Jul 4 11:54:16 localhost NetworkManager: Activation (eth0/wireless): access point 'HomeWireless' is encrypted, and a key exists. No new key needed. Jul 4 11:54:17 localhost NetworkManager: SUP: sending command 'INTERFACE_ADD eth0wext/var/run/wpa_supplicant ' Jul 4 11:54:17 localhost NetworkManager: SUP: response was 'OK' Jul 4 11:54:17 localhost NetworkManager: SUP: sending command 'AP_SCAN 2' Jul 4 11:54:17 localhost NetworkManager: SUP: response was 'OK' Jul 4 11:54:17 localhost NetworkManager: SUP: sending command 'ADD_NETWORK' Jul 4 11:54:17 localhost NetworkManager: SUP: response was '0' Jul 4 11:54:17 localhost NetworkManager: SUP: sending command 'SET_NETWORK 0 ssid 486f6d65576972656c657373' Jul 4 11:54:17 localhost NetworkManager: SUP: response was 'OK' Jul 4 11:54:17 localhost NetworkManager: SUP: sending command 'SET_NETWORK 0 scan_ssid 1' Jul 4 11:54:17 localhost NetworkManager: SUP: response was 'OK' Jul 4 11:54:17 localhost NetworkManager: SUP: sending command 'SET_NETWORK 0 key_mgmt NON
Re: Unable to Connect Using WPA
On 4/6/06, Mike Bydalek <[EMAIL PROTECTED]> wrote: > Hello all. > > I know there's been a lot of work going on in the wpa_supplicant area, > so I finally decided to give it a try as I would *really* love to > implement it into our network. > > My testbed is on a WRTG54G using WPA Personal with TKIP and a plain > password. When I try to connect, it just sits there and the logging > just stops. The problem is, I don't know if this is a NM issue or in > WPA Supplicant. > > I'm using NM 0.6.2 and WPASupplicant 0.4.8. I attached my log to make > it easier to read. > > Anyone have any ideas what I can do to get more information and/or how > to solve this? > > Thanks! > > -Mike > > > NetworkManager: [1144364185.834729] > nm_device_802_11_wireless_get_activation_ap (): Forcing AP 'secure' > NetworkManager:User Switch: > /org/freedesktop/NetworkManager/Devices/eth1 / secure > NetworkManager:Deactivating device eth1. > NetworkManager:Device eth1 activation scheduled... > NetworkManager:Activation (eth1) started... > NetworkManager:Activation (eth1) Stage 1 of 5 (Device > Prepare) scheduled... > NetworkManager:Activation (eth1) Stage 1 of 5 (Device > Prepare) started... > NetworkManager:Activation (eth1) Stage 2 of 5 (Device > Configure) scheduled... > NetworkManager:Activation (eth1) Stage 1 of 5 (Device > Prepare) complete. > NetworkManager:Activation (eth1) Stage 2 of 5 (Device > Configure) starting... > NetworkManager:Activation (eth1/wireless): access point > 'secure' is encrypted, and a key exists. No new key needed. > NetworkManager:SUP: sending command 'INTERFACE_ADD eth1 > wext/var/run/wpa_supplicant ' > NetworkManager:SUP: response was 'OK' > NetworkManager:SUP: sending command 'AP_SCAN 2' > NetworkManager:SUP: response was 'OK' > NetworkManager:SUP: sending command 'ADD_NETWORK' > NetworkManager:SUP: response was '0' > NetworkManager:SUP: sending command 'SET_NETWORK 0 ssid > 736563757265' > NetworkManager:SUP: response was 'OK' > NetworkManager:SUP: sending command 'SET_NETWORK 0 scan_ssid > 1' > NetworkManager:SUP: response was 'OK' > NetworkManager:SUP: sending command 'SET_NETWORK 0 proto WPA' > NetworkManager:SUP: response was 'OK' > NetworkManager:SUP: sending command 'SET_NETWORK 0 key_mgmt > WPA-PSK' > NetworkManager:SUP: response was 'OK' > NetworkManager:SUP: sending command 'SET_NETWORK 0 psk ' > NetworkManager:SUP: response was 'OK' > NetworkManager:SUP: sending command 'ENABLE_NETWORK 0' > NetworkManager:SUP: response was 'OK' > NetworkManager:Activation (eth1) Stage 2 of 5 (Device > Configure) complete. > NetworkManager:wpa_supplicant(30747): Global control > interface '/var/run/wpa_supplicant-global' > NetworkManager:wpa_supplicant(30747): RX global ctrl_iface - > hexdump_ascii(len=49): > NetworkManager:wpa_supplicant(30747): 49 4e 54 45 52 46 > 41 43 45 5f 41 44 44 20 65 74 INTERFACE_ADD et > NetworkManager:wpa_supplicant(30747): 68 31 09 09 77 65 > 78 74 09 2f 76 61 72 2f 72 75 h1__wext_/var/ru > NetworkManager:wpa_supplicant(30747): 6e 2f 77 70 61 5f > 73 75 70 70 6c 69 63 61 6e 74 n/wpa_supplicant > NetworkManager:wpa_supplicant(30747): 09 > _ > NetworkManager:wpa_supplicant(30747): CTRL_IFACE GLOBAL > INTERFACE_ADD 'eth1wext/var/run/wpa_supplicant ' > NetworkManager:wpa_supplicant(30747): Initializing interface > 'eth1' conf 'N/A' driver 'wext' ctrl_interface '/var/run/wpa_supplicant' > NetworkManager:wpa_supplicant(30747): Initializing interface > (2) 'eth1' > NetworkManager:wpa_supplicant(30747): EAPOL: SUPP_PAE > entering state DISCONNECTED > NetworkManager:wpa_supplicant(30747): EAPOL: KEY_RX entering > state NO_KEY_RECEIVE > NetworkManager:wpa_supplicant(30747): EAPOL: SUPP_BE > entering state INITIALIZE > NetworkManager:wpa_supplicant(30747): EAP: EAP entering > state DISABLED > NetworkManager:wpa_supplicant(30747): EAPOL: External > notification - portEnabled=0 > NetworkManager:wpa_supplicant(30747): EAPOL: External > notification - portValid=0 > NetworkManager:wpa_supplicant(30747): SIOCGIWRANGE: > WE(compiled)=19 WE(source)=18 enc_capa=0xf > NetworkManager:wpa_supplicant(30747): capabilities: > key_mgmt 0xf enc 0xf > NetworkManager:wpa_supplicant(30747): Own MAC address: > 00:13:ce:12:db:b1 > NetworkManager:wpa_supplicant(30747): wpa_driver_wext_set_wpa > NetworkManager:wpa_supplicant(30747): =0 key_idx=0 set_tx=0 > seq_len=0 key_len=0 > NetworkManager:wpa_supplicant(30747): > wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0 > NetworkManager:wpa_supplicant(30747): > wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0 > NetworkManager:wpa_supplicant(30747): > wpa_driver_wext_set_key: al
Re: Nearly there
On 4/4/06, Antony Gelberg <[EMAIL PROTECTED]> wrote: > Hi all, > > I'm trying to configure NM for a customer. He has a laptop with an > ipw2200, and is running Ubuntu Dapper (NM 0.6x). > > We finally got it running after > https://launchpad.net/distros/ubuntu/+source/network-manager/+bug/37084 > pointed out that we needed to prune existing config from > /etc/network/interfaces. Not a gripe, but it would be great to point > this out somewhere (unless it's in the docs and I missed it in which > case I apologise). > > It works fine with an Ethernet connection. However, when the wire is > pulled out, the icon goes red, but there is no question regarding moving > to the wireless which is nearby, and which is detected by Kismet. > > How can I debug this? I am new to NM and don't exactly have an in-depth > knowledge of dbus and hal. > > Antony > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > service NetworkManager stop NetworkManager --no-daemon -- Registered Linux User: #376813 www.fedorajim.homelinux.com ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
change the gnome keyring manager password
as the title states... How can I change the gnome keyring manager password ?? -- Registered Linux User: #376813 www.fedorajim.homelinux.com ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Will it work under Fedora Core 5?
On 3/29/06, Eli Criffield <[EMAIL PROTECTED]> wrote: > > 2 minute wireless > > > > installed ipw2200 FW from source forge > > rmmod ipw2200 > > modprobe ipw2200 > > Just curious, what kinda access point is that? WPA-PSK or WPA enterprise? > > oh and from the instructions on the link: > --- > mkdir tmp > mv ~/Desktop/*-2.4.tgz ~/tmp > tar -zxvf ipw2200-fw-2.4.tgz > cp * /lib/firmware > rmmod ipw2200 > modprobe ipw2200 > iwconfig > --- > you mite want to add a "cd tmp" or two in there before someone copies > there home directory to /lib/firmware. > > Eli Thanks ! fixed it -- Registered Linux User: #376813 www.fedorajim.homelinux.com ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Will it work under Fedora Core 5?
On 3/29/06, Peter Jones <[EMAIL PROTECTED]> wrote: > On Wed, 2006-03-29 at 07:53 +0200, Trond Husø wrote: > > Hi list, > > > > Fedora Core 5 has just been released, and I might concider upgrading > > from FC4. But before I do, I need to know if some of my favorite > > programs works. One of these are Network Manager. > > So: Does it work under FC5? > > We ship it and it works. It's not started by default, nor is nm-applet > running by default. > > -- > Peter > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > 2 minute wireless installed ipw2200 FW from source forge rmmod ipw2200 modprobe ipw2200 started NM Connect to my AP Here is the directions I wrote for others http://easylinux.info/wiki/Fedora_fc5#how_to_get_wireless_working_Intel_IPW2200_b.2Cg -- Registered Linux User: #376813 www.fedorajim.homelinux.com ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wpa_supplicant
On 3/28/06, Dan Williams <[EMAIL PROTECTED]> wrote:
> On Tue, 2006-03-28 at 16:58 -0500, jim lawrence wrote:
> > Hello Folks First post
> > I would like to enable the wpa_supplicant support into my wireless. I
> > can change the AP's Security settings to the attahed image. When
> > doing so i cannot connect. The applet just sits and spins. I start
> > the wpasupplicant service and still unable to connect.
> >
> > NetworkManager-gnome-0.6.0-3
> > NetworkManager-0.6.0-3
> > NetworkManager-glib-0.6.0-3
> >
> > Wireless Device ipw2200
>
> Can you provide output from NetworkManager and wpa_supplicant, either by
> attaching syslog output or running NM with the "--no-daemon" argument
> and trying to connect?
>
The attached img is the settings on the AP
[EMAIL PROTECTED] jim]# su -
[EMAIL PROTECTED] ~]# NetworkManager --no-daemon
NetworkManager:starting...
NetworkManager: nm_dbus_init (): nm_dbus_init() could
not acquire the NetworkManager service as it is already taken (ret=3).
Is the daemon already running?
NetworkManager: [1143630876.840500] main (): nm_dbus_init()
failed, exiting. Either dbus is not running, or the NetworkManager
dbus security policy was not loaded.
NetworkManager: traceback:
NetworkManager: NetworkManager(main+0x44a) [0x8067eba]
NetworkManager: /lib/libc.so.6(__libc_start_main+0xdc) [0x13a7e4]
NetworkManager: NetworkManager [0x80530c1]
Trace/breakpoint trap
[EMAIL PROTECTED] ~]#
NM will not even try to connect with my AP with the attchched settings
wpa_supplicant.conf
[QUOTE]
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
ap_scan=1
update_config=1
network={
ssid="HomeWireless"
key_mgmt=WPA-PSK
proto=WPA
pairwise=TKIP
psk="*"
#disabled=1
}[/QUOTE]
wpa_supplicant
[QUOTE]
# wlan0 and wifi0
# INTERFACES="-iwlan0 -iwifi0"
INTERFACES="-eth1"
# ndiswrapper and prism
# DRIVERS="-Dndiswrapper -Dprism"
DRIVERS="-Dwext" <--- have tried Dipw as well
[/QUOTE]
--
Registered Linux User: #376813
www.fedorajim.homelinux.com
SEC-Settings.png
Description: PNG image
Mar 29 06:21:53 localhost NetworkManager: wpa_supplicant(3394):
Setting scan request: 5 sec 0 usec
Mar 29 06:21:53 localhost NetworkManager: wpa_supplicant(3394):
Starting AP scan (broadcast SSID)
Mar 29 06:21:53 localhost NetworkManager: wpa_supplicant(3394):
Scan timeout - try to get results
Mar 29 06:21:53 localhost NetworkManager: wpa_supplicant(3394):
Received 623 bytes of scan results (3 BSSes)
Mar 29 06:21:53 localhost NetworkManager: wpa_supplicant(3394):
Scan results: 3
Mar 29 06:21:53 localhost NetworkManager: wpa_supplicant(3394):
Selecting BSS from priority group 0
Mar 29 06:21:53 localhost NetworkManager: wpa_supplicant(3394):
0: 00:0f:66:21:10:45 ssid='HomeWireless' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
Mar 29 06:21:53 localhost NetworkManager: wpa_supplicant(3394):
skip WPA IE - key mgmt mismatch
Mar 29 06:21:53 localhost NetworkManager: wpa_supplicant(3394):
1: 00:14:bf:d2:54:f6 ssid='AngryBunnies' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
Mar 29 06:21:55 localhost NetworkManager: wpa_supplicant(3394):
Mar 29 06:22:01 localhost NetworkManager: Activation
(eth0/wireless): association took too long (>20s), failing activation.
Mar 29 06:22:01 localhost NetworkManager: Activation (eth0)
failure scheduled...
Mar 29 06:22:01 localhost NetworkManager: Activation (eth0)
failed for access point (HomeWireless)
Mar 29 06:22:01 localhost NetworkManager: Activation (eth0)
failed.
Mar 29 06:22:01 localhost NetworkManager: Deactivating device
eth0.
Mar 29 06:22:03 localhost NetworkManager: SWITCH: no current
connection, found better connection 'eth0'.
Mar 29 06:22:03 localhost NetworkManager: Will activate
connection 'eth0/linksys'.
Mar 29 06:22:03 localhost NetworkManager: Device eth0 activation
scheduled...
Mar 29 06:22:03 localhost NetworkManager: Activation (eth0)
started...
Mar 29 06:22:03 localhost NetworkManager: Activation (eth0) Stage
1 of 5 (Device Prepare) scheduled...
Mar 29 06:22:03 localhost NetworkManager: Activation (eth0) Stage
1 of 5 (Device Prepare) started...
Mar 29 06:22:03 localhost NetworkManager: Activation (eth0) Stage
2 of 5 (Device Configure) scheduled...
Mar 29 06:22:03 localhost NetworkManager: Activation (eth0) Stage
1 of 5 (Device Prepare) complete.
Mar 29 06:22:03 localhost NetworkManager: Activation (eth0) Stage
2 of 5 (Device Configure) starting...
Mar 29 06:22:03 localhost NetworkManager: Activation
(eth0/wireless): access point 'linksys' is unencrypted, no key needed.
Mar 29 06:22:04 localhost NetworkManager: SUP: sending command
'INTERFACE_ADD eth0
Re: Will it work under Fedora Core 5?
I did a fresh instal of FC5 and was connect with my wireless in 2 minutes after loading the firmware for my wireless device. On 3/29/06, Trond Husø <[EMAIL PROTECTED]> wrote: > Hi list, > > Fedora Core 5 has just been released, and I might concider upgrading > from FC4. But before I do, I need to know if some of my favorite > programs works. One of these are Network Manager. > So: Does it work under FC5? > > Still. Since FC5 is so fresh it is wise to wait some to get the ugliest > bugs out of the way. > > trond > > > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > -- Registered Linux User: #376813 www.fedorajim.homelinux.com ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
wpa_supplicant
Hello Folks First post I would like to enable the wpa_supplicant support into my wireless. I can change the AP's Security settings to the attahed image. When doing so i cannot connect. The applet just sits and spins. I start the wpasupplicant service and still unable to connect. NetworkManager-gnome-0.6.0-3 NetworkManager-0.6.0-3 NetworkManager-glib-0.6.0-3 Wireless Device ipw2200 firmware V 2.4 from Sourceforge # ls /lib/firmware ipw2200-fw-2.4.tgz ipw-2.4-bss_ucode.fw ipw-2.4-sniffer.fw ipw-2.4-boot.fw ipw-2.4-ibss.fwipw-2.4-sniffer_ucode.fw ipw-2.4-bss.fw ipw-2.4-ibss_ucode.fw LICENSE Am I missing something? -- Registered Linux User: #376813 www.fedorajim.homelinux.com SEC-Settings.png Description: PNG image ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
