ipw3945 fails to associate
Hi, My system: Asus Aspire 5570 laptop with ipw3945 wireless card. Using Fedora Core 6 I can't make NetworkManager to associate to either encrypted or unencrypted wireless access points. Using a terminal and iwconfg at the same location associates instantly and dhclient works fine. NetworkManager in the same laptop, same access point but using Ubuntu works perfectly. I would like to get FC6 to work bcause it's the distro I want to use. This are the logs I get in /var/log/messages Apr 2 18:10:48 localhost NetworkManager: information User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / TPLwireless Apr 2 18:10:48 localhost NetworkManager: information Deactivating device eth1. Apr 2 18:10:48 localhost NetworkManager: information Activation (eth1): cancelling... Apr 2 18:10:48 localhost NetworkManager: information Activation (eth1) cancellation handler scheduled... Apr 2 18:10:48 localhost NetworkManager: information Activation (eth1): waiting for device to cancel activation. Apr 2 18:10:48 localhost dhclient: DHCPRELEASE on eth1 to 10.255.1.1 port 67 Apr 2 18:10:48 localhost dhclient: send_packet: Network is unreachable Apr 2 18:10:48 localhost dhclient: send_packet: please consult README file regarding broadcast address. Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1) cancellation handled. Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1): cancelled. Apr 2 18:10:49 localhost NetworkManager: information Device eth1 activation scheduled... Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1) started... Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1) Stage 1 of 5 (Device Prepare) started... Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1) Stage 1 of 5 (Device Prepare) complete. Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1) Stage 2 of 5 (Device Configure) starting... Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1/wireless): access point 'TPLwireless' is unencrypted, no key needed. Apr 2 18:10:49 localhost NetworkManager: information SUP: sending command 'INTERFACE_ADD eth1 wext/var/run/wpa_supplicant ' Apr 2 18:10:49 localhost NetworkManager: information SUP: response was 'OK' Apr 2 18:10:49 localhost NetworkManager: information SUP: sending command 'AP_SCAN 1' Apr 2 18:10:49 localhost NetworkManager: information SUP: response was 'OK' Apr 2 18:10:49 localhost NetworkManager: information SUP: sending command 'ADD_NETWORK' Apr 2 18:10:49 localhost NetworkManager: information SUP: response was '0' Apr 2 18:10:49 localhost NetworkManager: information SUP: sending command 'SET_NETWORK 0 ssid 54504c776972656c657373' Apr 2 18:10:49 localhost NetworkManager: information SUP: response was 'OK' Apr 2 18:10:49 localhost NetworkManager: information SUP: sending command 'SET_NETWORK 0 key_mgmt NONE' Apr 2 18:10:49 localhost NetworkManager: information SUP: response was 'OK' Apr 2 18:10:49 localhost NetworkManager: information SUP: sending command 'ENABLE_NETWORK 0' Apr 2 18:10:49 localhost NetworkManager: information SUP: response was 'OK' Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1) Stage 2 of 5 (Device Configure) complete. Apr 2 18:10:53 localhost NetworkManager: information Old device 'eth1' activating, won't change. Apr 2 18:10:59 localhost NetworkManager: information eth1: link timed out. Apr 2 18:10:59 localhost NetworkManager: information Old device 'eth1' activating, won't change. Apr 2 18:11:29 localhost NetworkManager: information Activation (eth1/wireless): association took too long (40s), failing activation. Apr 2 18:11:29 localhost NetworkManager: information Activation (eth1) failure scheduled... Apr 2 18:11:29 localhost NetworkManager: information Activation (eth1) failed for access point (TPLwireless) Apr 2 18:11:29 localhost NetworkManager: information Activation (eth1) failed. Apr 2 18:11:29 localhost NetworkManager: information Deactivating device eth1. The only changes I've done to the network configuration was to disable IPv6 following this guide http://www.mjmwired.net/resources/mjm-fedora-fc6.html#ipv6 Any help would be greatly appreciated! Please let me know what extra information should I provide. Hector -- === http://www.hcenteno.net ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NetworkManager firewall policy
Hi, Network Manager might be an elegant solution to basic network management. But are there any policies on how network manager handles firewall policy? For example, in a scenario like: 1) When accessing at home I want ssh port allowed. 2) When at office, I want rdp allowed. 3) When outside, don't allow anything. I can set a generic firewall policy to block/allow connections but for specific connections how does network manager handle firewalling policies ? Thanks, Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. Stealing logic from one person is plagiarism, stealing from many is research. The great are those who achieve the impossible, the petty are those who cannot - rrs ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager firewall policy
On 4/3/07, Ritesh Raj Sarraf [EMAIL PROTECTED] wrote: Hi, Network Manager might be an elegant solution to basic network management. But are there any policies on how network manager handles firewall policy? For example, in a scenario like: 1) When accessing at home I want ssh port allowed. 2) When at office, I want rdp allowed. 3) When outside, don't allow anything. I can set a generic firewall policy to block/allow connections but for specific connections how does network manager handle firewalling policies ? Thanks, Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. Stealing logic from one person is plagiarism, stealing from many is research. The great are those who achieve the impossible, the petty are those who cannot - rrs At this time Network-Manager does not have a Firewall/IPtables plugin (Though that would be a great addition), but you can use NetworkManagerDispatcher and whereami to update your iptables rules when you connect. Networkmanagerdispatcher will run scripts after an interface comes up or goes down, more specifics and examples on it are available in the man page or from searching the archives. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM and ipw3945 once again
Tuesday 13 March 2007 14:28:56 Derek Atkins napisał(a): I'll also note that when I just use ifup directly (after I shutdown NM) then I don't see these log messages and I don't have disconnect events. But obviously this only works with unsecured networks. But this certainly leads me to believe it's a problem in wpa_supplicant and/or NM and NOT a driver bug. It seems that it was a problem of wpa_supplicant. After I had updated the wpa_supplicant to the newest version 0.5.7, NM started working perfectly. I checked with wpa_cli, and it seems that this time supplicant connects to my router already at the first time, and gets no disconnect event. Best regards Piotr. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ipw3945 fails to associate
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I had a similar problem right after updating from Kubuntu 6.10 to 7.04. My resolution for the problem was to reboot, having never touched the card with iwconfig. I did not run complicated tests, since I was in a hurry, but checking iwconfig on the card when NM was failing to associated showed that it was turning encryption on and off repeatedly. Conversely, if I've ever touched the device with NM, wpa_supplicant will not work on the card (only finds access points with all-zero MAC's) until a reboot where NM never touched the device. I was running 2.6.17-11 until recently, but now I'm running a 2.6.20 series kernel. I haven't done much testing since I upgraded, so I don't know if it will make a difference. Hector Centeno wrote: Hi, My system: Asus Aspire 5570 laptop with ipw3945 wireless card. Using Fedora Core 6 I can't make NetworkManager to associate to either encrypted or unencrypted wireless access points. Using a terminal and iwconfg at the same location associates instantly and dhclient works fine. NetworkManager in the same laptop, same access point but using Ubuntu works perfectly. I would like to get FC6 to work bcause it's the distro I want to use. This are the logs I get in /var/log/messages Apr 2 18:10:48 localhost NetworkManager: information User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / TPLwireless Apr 2 18:10:48 localhost NetworkManager: information Deactivating device eth1. Apr 2 18:10:48 localhost NetworkManager: information Activation (eth1): cancelling... Apr 2 18:10:48 localhost NetworkManager: information Activation (eth1) cancellation handler scheduled... Apr 2 18:10:48 localhost NetworkManager: information Activation (eth1): waiting for device to cancel activation. Apr 2 18:10:48 localhost dhclient: DHCPRELEASE on eth1 to 10.255.1.1 port 67 Apr 2 18:10:48 localhost dhclient: send_packet: Network is unreachable Apr 2 18:10:48 localhost dhclient: send_packet: please consult README file regarding broadcast address. Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1) cancellation handled. Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1): cancelled. Apr 2 18:10:49 localhost NetworkManager: information Device eth1 activation scheduled... Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1) started... Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1) Stage 1 of 5 (Device Prepare) started... Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1) Stage 1 of 5 (Device Prepare) complete. Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1) Stage 2 of 5 (Device Configure) starting... Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1/wireless): access point 'TPLwireless' is unencrypted, no key needed. Apr 2 18:10:49 localhost NetworkManager: information SUP: sending command 'INTERFACE_ADD eth1 wext/var/run/wpa_supplicant ' Apr 2 18:10:49 localhost NetworkManager: information SUP: response was 'OK' Apr 2 18:10:49 localhost NetworkManager: information SUP: sending command 'AP_SCAN 1' Apr 2 18:10:49 localhost NetworkManager: information SUP: response was 'OK' Apr 2 18:10:49 localhost NetworkManager: information SUP: sending command 'ADD_NETWORK' Apr 2 18:10:49 localhost NetworkManager: information SUP: response was '0' Apr 2 18:10:49 localhost NetworkManager: information SUP: sending command 'SET_NETWORK 0 ssid 54504c776972656c657373' Apr 2 18:10:49 localhost NetworkManager: information SUP: response was 'OK' Apr 2 18:10:49 localhost NetworkManager: information SUP: sending command 'SET_NETWORK 0 key_mgmt NONE' Apr 2 18:10:49 localhost NetworkManager: information SUP: response was 'OK' Apr 2 18:10:49 localhost NetworkManager: information SUP: sending command 'ENABLE_NETWORK 0' Apr 2 18:10:49 localhost NetworkManager: information SUP: response was 'OK' Apr 2 18:10:49 localhost NetworkManager: information Activation (eth1) Stage 2 of 5 (Device Configure) complete. Apr 2 18:10:53 localhost NetworkManager: information Old device 'eth1' activating, won't change. Apr 2 18:10:59 localhost NetworkManager: information eth1: link timed out. Apr 2 18:10:59 localhost NetworkManager: information Old device 'eth1' activating, won't change. Apr 2 18:11:29 localhost NetworkManager: information Activation (eth1/wireless): association took too long (40s), failing activation.
Re: Unable to connect to wireless
On 04/02/07 11:42:13, Ryan Novosielski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Geoffrey Leach wrote: On 04/02/07 09:42:07, Patrick Bogen wrote: On 4/2/07, Geoffrey Leach [EMAIL PROTECTED] wrote: NetworkManager fails to connect to my Netgear router. Hardware function has been confirmed (Windoze (sigh!)) I expect that's its a config problem - where should I look? Here's the relevant section of the log. NetworkManager: information SUP: sending command 'SET_NETWORK 0 ssid 4e657467656172' My first guess would be that 'NetworkManager: information SUP: sending command 'SET_NETWORK 0 ssid 4e657467656172'' is causing problems.. Since, from what I can tell, 'Netgear' is your SSID, not 4e657 I don't know why this might be happening, however. If you associate manually (stop networkmanager, then: iwconfig eth0 ssid Netgear; dhclient eth0) does it work and give you an IP? No joy, but perhaps some data. Listening on LPF/eth0/00:19:d2:2d:f2:76 Sending on LPF/eth0/00:19:d2:2d:f2:76 Sending on Socket/fallback DHCPREQUEST on eth0 to 255.255.255.255 port 67 ip length 326 disagrees with bytes received 534. accepting packet with data after udp payload. DHCPACK from 192.168.10.1 bound to 192.168.10.2 -- renewal in 42837 seconds. and in the kernel log, this is repeated. Apr 2 11:15:47 mtranch-mobile kernel: Unknown OutputIN= OUT=eth0 SRC=192.168.10.2 DST=64.97.131.50 LEN=44 TOS=0x00 PREC=0x00 TTL=64 ID=8188 DF PROTO=TCP SPT=36661 DPT=110 WINDOW=5840 RES=0x00 SYN URGP=0 The last part is from IPTables. My problem apparently results from an incompatibly between Fedora Network Manager and the wireless card installed on the laptop and open wireless networks. The vendor could have mentioned this earlier, I suppose. :-( ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: rt73 driver trouble
Em Sexta 30 Março 2007 20:57, Bastien Nocera escreveu:
On Fri, 2007-03-30 at 19:10 -0300, Lamarque Vieira Souza wrote:
Hi,
I am also trying to configure rt73 card to use WPA. I found in
this link
http://www.suseforums.net/lofiversion/index.php/t31193.html that
it can be done using iwpriv commands:
iwconfig rausb0 mode managed
iwpriv rausb0 set AuthMode=WPAPSK
iwpriv rausb0 set EncrypType=TKIP
iwconfig rausb0 essid essid
iwpriv rausb0 set WPAPSK=WPA key
dhclient rausb0
It seems the rt73 driver does not use Linux Wireless Extensions
to implement WPA. Is there a way to add the iwpriv commans above
to NetworkManager and get it working with rt73 driver?
No idea, I use WEP, and my distro's config files, and it works for
my usage...
Good news,
I managed to make NetworkManager to work with rt73 driver. The two
patches I used are attached. The wpa_supplicant-0.4.8-ralink.diff
patch is just a patch form of the files supplied by Ralink in
directory RT73_Linux_STA_Drv1.0.3.6/WPA_Supplicant. The first patch
contains my modifications. I do not know why but the fallback
parameter is type DBUS_TYPE_INT32 instead of DBUS_TYPE_BOOLEAN. Of
course just ignoring the fallback parameter is not a fix :-)
Do you think the wpa_supplicant-0.4.8-ralink.diff can be applied to
main wpa_supplicant? There is not indication of which license the
code in RT73_Linux_STA_Drv1.0.3.6/WPA_Supplicant uses, the code in
RT73_Linux_STA_Drv1.0.3.6/Module is GPL.
The change to make wpa_supplicant use ralink driver when dealing with
rt73 chipset is simple and I think it can be added to NetworkManager.
What do you think? Of course it will only work if the
wpa_supplicant-0.4.8-ralink.diff is applied to wpa_supplicant first.
--
Lamarque Vieira Souza
Senior Architect and Developer - Metasys
http://www.metasys.com.br
Tel.: +55 31 3296-9040 - Ramal 244
International Syst S/A
diff -Nru NetworkManager-0.6.4/src/nm-dbus-nm.c NetworkManager-0.6.4-lvs/src/nm-dbus-nm.c
--- NetworkManager-0.6.4/src/nm-dbus-nm.c 2007-04-03 15:11:36.0 -0300
+++ NetworkManager-0.6.4-lvs/src/nm-dbus-nm.c 2007-04-03 15:30:21.0 -0300
@@ -281,12 +281,16 @@
if (!dbus_message_iter_next (iter) || (dbus_message_iter_get_arg_type (iter) != DBUS_TYPE_BOOLEAN))
{
nm_warning (Invalid argument type (fallback);
- goto out;
+ // Lamarque 30/03/2007: type == DBUS_TYPE_INT32.
+// goto out;
}
/* grab the fallback bit */
dbus_message_iter_get_basic (iter, fallback);
+ // Lamarque 30/03/2007: type == DBUS_TYPE_INT32.
+ fallback = FALSE;
+
/* If there's security information, we use that. If not, we
* make some up from the scan list.
*/
diff -Nru NetworkManager-0.6.4/src/nm-device-802-11-wireless.c NetworkManager-0.6.4-lvs/src/nm-device-802-11-wireless.c
--- NetworkManager-0.6.4/src/nm-device-802-11-wireless.c 2007-04-03 15:11:44.0 -0300
+++ NetworkManager-0.6.4-lvs/src/nm-device-802-11-wireless.c 2007-04-03 14:48:13.0 -0300
@@ -2954,6 +2954,11 @@
wpa_driver = madwifi;
else if (!strcmp (kernel_driver, prism54))
wpa_driver = prism54;
+
+ /* Lamarque 03/04/2007 */
+ else if (!strcmp (kernel_driver, rt73))
+ wpa_driver = ralink;
+
else
wpa_driver = wext;
diff -Nru wpa_supplicant-0.4.8/defconfig wpa_supplicant-0.4.8-lvs/defconfig
--- wpa_supplicant-0.4.8/defconfig 2005-09-24 15:30:43.0 -0300
+++ wpa_supplicant-0.4.8-lvs/defconfig 2007-04-03 15:28:04.0 -0300
@@ -93,6 +93,9 @@
# Driver interface for wired Ethernet drivers
CONFIG_DRIVER_WIRED=y
+# Driver interface for Ralink driver
+CONFIG_DRIVER_RALINK=y
+
# Enable IEEE 802.1X Supplicant (automatically included if any EAP method is
# included)
CONFIG_IEEE8021X_EAPOL=y
diff -Nru wpa_supplicant-0.4.8/driver_ralink.c wpa_supplicant-0.4.8-lvs/driver_ralink.c
--- wpa_supplicant-0.4.8/driver_ralink.c 1969-12-31 21:00:00.0 -0300
+++ wpa_supplicant-0.4.8-lvs/driver_ralink.c 2007-04-03 15:21:44.0 -0300
@@ -0,0 +1,1274 @@
+/*
+ * WPA Supplicant - driver interaction with Ralink rt73.o driver
+ */
+
+#include stdlib.h
+#include stdio.h
+#include unistd.h
+#include string.h
+#include sys/ioctl.h
+#include errno.h
+#include sys/socket.h
+#include net/if_arp.h
+
+#include linux/if_packet.h
+#include linux/if_ether.h /* The L2 protocols */
+#include netinet/in.h
+//#include linux/wireless.h
+#include wireless_copy.h
+
+#include common.h
+#include driver.h
+#include l2_packet.h
+#include eloop.h
+#include wpa_supplicant.h
+#include priv_netlink.h
+#include wpa.h
+#include driver_ralink.h
+#include wpa_supplicant_i.h
+#include config_ssid.h
+#include config.h
+
+static int scanning_done = 1;
+
+struct wpa_driver_ralink_data {
+ void *ctx;
+ int ioctl_sock;
+ int event_sock;
+ char ifname[IFNAMSIZ + 1];
+ u8 *assoc_req_ies;
+ size_t assoc_req_ies_len;
+ u8 *assoc_resp_ies;
+ size_t assoc_resp_ies_len;
+ int no_of_pmkid;
+ struct ndis_pmkid_entry
Re: rt73 driver trouble
On Tue, 2007-04-03 at 15:52 -0300, Lamarque Vieira Souza wrote: Em Sexta 30 Março 2007 20:57, Bastien Nocera escreveu: On Fri, 2007-03-30 at 19:10 -0300, Lamarque Vieira Souza wrote: Hi, I am also trying to configure rt73 card to use WPA. I found in this link http://www.suseforums.net/lofiversion/index.php/t31193.html that it can be done using iwpriv commands: iwconfig rausb0 mode managed iwpriv rausb0 set AuthMode=WPAPSK iwpriv rausb0 set EncrypType=TKIP iwconfig rausb0 essid essid iwpriv rausb0 set WPAPSK=WPA key dhclient rausb0 It seems the rt73 driver does not use Linux Wireless Extensions to implement WPA. Is there a way to add the iwpriv commans above to NetworkManager and get it working with rt73 driver? No idea, I use WEP, and my distro's config files, and it works for my usage... Good news, I managed to make NetworkManager to work with rt73 driver. The two patches I used are attached. The wpa_supplicant-0.4.8-ralink.diff patch is just a patch form of the files supplied by Ralink in directory RT73_Linux_STA_Drv1.0.3.6/WPA_Supplicant. The first patch contains my modifications. I do not know why but the fallback parameter is type DBUS_TYPE_INT32 instead of DBUS_TYPE_BOOLEAN. Of course just ignoring the fallback parameter is not a fix :-) Custom wpa_supplicant drivers are not the answer. The answer is to fix the driver to work correctly with the WEXT driver. That's why NetworkManager _only_ uses the WEXT driver with wpa_supplicant, because there needs to be standardization on _one_ interface so that we don't need to re-write stuff 50 times for each driver. So even if the ralink driver did get into wpa_supplicant, NetworkManager will not use that custom driver. Dan Do you think the wpa_supplicant-0.4.8-ralink.diff can be applied to main wpa_supplicant? There is not indication of which license the code in RT73_Linux_STA_Drv1.0.3.6/WPA_Supplicant uses, the code in RT73_Linux_STA_Drv1.0.3.6/Module is GPL. The change to make wpa_supplicant use ralink driver when dealing with rt73 chipset is simple and I think it can be added to NetworkManager. What do you think? Of course it will only work if the wpa_supplicant-0.4.8-ralink.diff is applied to wpa_supplicant first. ___ 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
