PEAP with GTC in NetworkManager-0.7.0-0.12.svn4326.fc10.x86_64
Hi,
I am trying to use Fedora 10/Intel 5300 on a Cisco based wireless network,
which uses GTC for the inner authentication. I see this option no longer
exists in the version of NM that I have:
NetworkManager-0.7.0-0.12.svn4326.fc10.x86_64.
Out of curiosity, I used GIT to get the latest source, and see the following
in libnm-util/nm-setting-8021x.c:
950 { gtc, NULL, NULL }, // FIXME: implement
So, it appears GTC is not implemented in NM, even though wpa_supplicant
supports it. Are there any patches available that allow this to work? This
seems to be a regression from version 0.6.x (I don't know the exact version
I was using before).
I've seen various bugs filed at the distribution level regarding this, but I
didn't see one with this specific problem in the Gnome bugtracker. However,
seeing the comment in the source, it seems to be a known-issue. Is this
actually the case, and will this actually be implimented? Do I need to
actually file a bug? Are there any known workarounds?
Respectfully,
David
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: DBus Properties 0.7.0 Device question
On Thu, Dec 18, 2008 at 11:34, Simon Schampijer si...@schampijer.de wrote: Tambet Ingo wrote: On Wed, Dec 17, 2008 at 22:39, Simon Schampijer si...@schampijer.de wrote: Philip Culver wrote: Some addtional information. If I execute: dbus-send --system --dest=org.freedesktop.NetworkManager --print-reply /org/freedesktop/Hal/devices/net_00_13_02_06_6d_ee org.freedesktop.DBus.Properties.Get string:'org.freedesktop.NetworkManager.Device.Wireless' string:'HwAddress' I get the proper value with a Get call. If I execute the GetAll method I always get the generic the Device properties. That is an interesting one. I actually saw the same problem with using the dbus python interface when doing an GetAll on a wired device. It's a bug in dbus-glib. It never even looks at the DBus interface (it only needs to be a string) which is passed to GetAll() method: http://cgit.freedesktop.org/dbus/dbus-glib/tree/dbus/dbus-gobject.c#n1442 Tambet ok, makes sense - Dan was so kind to file it: http://bugs.freedesktop.org/show_bug.cgi?id=19145 I was even kinder, I just fixed it. :) Attached the patch to the bugzilla. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WPA Enterprise (EAP-TLS) system connection
John S. Skogtvedt skrev: Dan Williams skrev: Once you have a connection set up in the connection editor, and you have the keyfile plugin enabled, you should be able to check the make available to all users checkbox, hit apply, and it'll be a keyfile. It's quite likely you'll want to be using the final 0.7 NetworkManager release, as a lot of the effort in November went into making this sort of thing actually work, but the Ubuntu snapshots are from mid October. Dan Thanks, once I've been able to test the final 0.7 version I'll get back to you on the the other questions (if still applicable). (The debian experimental package I tested is 0.7.0~svn4191-1 and is from Oct 18.) John. I finally got around to doing more testing today, this time using version 0.7.0-1 from http://debs.michaelbiebl.de/network-manager/. Settings used in nm-connection-editor: SSID: dd-wrt Wireless security: Security: WPA and WPA2 enterprise Authentication: TLS Identity: omni User Certificate: client_cert.pem CA Certificate: cacert.pem Private Key: client_key.pem Private Key Password: (the correct password) If the Available to all users option is _not_ selected, network-manager connects without problems. But if it is selected, I get the message network disconnected. The created keyfile looks like this: [802-11-wireless-security] key-mgmt=wpa-eap wep-tx-keyidx=0 [connection] id=dd-wrt uuid=bdc78c4d-bae8-4b6a-a287-6271cf208307 type=802-11-wireless autoconnect=true timestamp=0 [802-11-wireless] ssid=100;100;45;119;114;116; mode=infrastructure channel=0 rate=0 tx-power=0 mtu=0 security=802-11-wireless-security [ipv4] method=auto ignore-auto-routes=false ignore-auto-dns=false [802-1x] eap=tls; identity=omni ca-cert=... client-cert=... system-ca-certs=false As you can see, the private key is not saved. In syslog, I get the following messages: Dec 18 14:22:15 omni NetworkManager: info Activation (wlan0) starting connect ion 'dd-wrt' Dec 18 14:22:15 omni NetworkManager: info (wlan0): device state change: 3 - 4 Dec 18 14:22:15 omni NetworkManager: info Activation (wlan0) Stage 1 of 5 (De vice Prepare) scheduled... Dec 18 14:22:15 omni NetworkManager: info Activation (wlan0) Stage 1 of 5 (De vice Prepare) started... Dec 18 14:22:15 omni NetworkManager: info Activation (wlan0) Stage 2 of 5 (De vice Configure) scheduled... Dec 18 14:22:15 omni NetworkManager: info Activation (wlan0) Stage 1 of 5 (De vice Prepare) complete. Dec 18 14:22:15 omni NetworkManager: info Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Dec 18 14:22:15 omni NetworkManager: info (wlan0): device state change: 4 -5 Dec 18 14:22:15 omni NetworkManager: info Activation (wlan0/wireless): access point 'dd-wrt' has security, but secrets are required. Dec 18 14:22:15 omni NetworkManager: info (wlan0): device state change: 5 -6 Dec 18 14:22:15 omni NetworkManager: info Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Dec 18 14:22:15 omni nm-system-settings: add_secrets: unhandled secret private-key type GArray_guchar_ Dec 18 14:22:15 omni nm-system-settings: add_secrets: unhandled secret phase2-private-key type GArray_guchar_ Hope this helps, John. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Connection works with plain openvpn, fails with networkmanager
Hoi everyone, I have an old openvpn script that I'm trying to convert to a NetworkManager configuration on Ubuntu Intrepid. I've got it mostly working, and I've verified that nm passes the same parameters to openvpn as my (working) script does (besides --resolv-retry infinite and --ns-cert-type server, which shouldn't affect this). Apparently NM is doing something extra that's breaking things, but I haven't been able to find a useable solution. After some looking in the logs and routing table and some playing around I found that I can make the connection started by networkmanager work by executing this command: route del -host vpn.company.nl dev tap0 Where vpn.company.nl is the vpn server I'm connecting to. I'm not really sure why that route was added in the first place, since to me it seems like it would try to route the vpn connection over the vpn. The interesting part of my syslog looks like this (public ip addresses anonymised): Dec 18 13:10:57 mypc NetworkManager: info VPN connection 'Company' (IP Config Get) reply received. Dec 18 13:10:57 mypc NetworkManager: info VPN Gateway: XX.XX.64.74 Dec 18 13:10:57 mypc NetworkManager: info Internal Gateway: 192.168.168.1 Dec 18 13:10:57 mypc NetworkManager: info Tunnel Device: tap0 Dec 18 13:10:57 mypc NetworkManager: info Internal IP4 Address: 192.168.170.229 Dec 18 13:10:57 mypc NetworkManager: info Internal IP4 Prefix: 32 Dec 18 13:10:57 mypc NetworkManager: info Internal IP4 Point-to-Point Address: 0.0.0.0 Dec 18 13:10:57 mypc NetworkManager: info Maximum Segment Size (MSS): 0 Dec 18 13:10:57 mypc NetworkManager: info Static Route: XX.XX.64.74/32 Next Hop: XX.XX.64.74 Dec 18 13:10:57 mypc NetworkManager: info Static Route: XX.XX.64.64/27 Next Hop: XX.XX.64.64 Dec 18 13:10:57 mypc NetworkManager: info Static Route: YY.YY.228.0/22 Next Hop: YY.YY.228.0 Dec 18 13:10:57 mypc NetworkManager: info Static Route: YY.ZZ.255.11/32 Next Hop: YY.ZZ.255.11 Dec 18 13:10:57 mypc NetworkManager: info Internal IP4 DNS: YY.ZZ.231.73 Dec 18 13:10:57 mypc NetworkManager: info DNS Domain: '(none)' Dec 18 13:10:57 mypc NetworkManager: info Login Banner: Dec 18 13:10:57 mypc NetworkManager: info - Dec 18 13:10:57 mypc NetworkManager: info (null) Dec 18 13:10:57 mypc NetworkManager: info - The rest of the networkmanager entries in the log are about the 192.168 range. I saw nothing strange there, but I can post it if needed. My openvpn command line is: /usr/sbin/openvpn --client --dev tap --proto udp --remote vpn.company.nl 1195 --nobind --persist-key --persist-tun --ca /etc/vpn/ca.crt --ns-cert-type server --comp-lzo --verb 3 --auth-user-pass --user me --group nogroup --daemon Thanks for your time! Greetings, Ronald. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
[PATCH] Remove timeout when freeing data
The patch below is needed on my system when the device_added method is called twice. On the second call, the call to g_object_set_data_full() causes the data struct from the first call to be destroyed but the timeout function may still run. Comments? Drew Index: src/applet-device-wifi.c === --- src/applet-device-wifi.c(revision 1076) +++ src/applet-device-wifi.c(working copy) @@ -1060,6 +1060,9 @@ struct ap_notification_data *data = user_data; NMSettings *settings = applet_get_settings (data-applet); + if (data-id != 0) + g_source_remove(data-id); + if (settings) g_signal_handler_disconnect (settings, data-new_con_id); memset (data, 0, sizeof (*data)); ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: PEAP with GTC in NetworkManager-0.7.0-0.12.svn4326.fc10.x86_64
Filed a bug in Gnome's bugtracker in case anybody else runs across this
thread with the same issue: http://bugzilla.gnome.org/show_bug.cgi?id=565065
Thanks,
David
On Thu, Dec 18, 2008 at 4:09 AM, David Orman orma...@corenode.com wrote:
Hi,
I am trying to use Fedora 10/Intel 5300 on a Cisco based wireless network,
which uses GTC for the inner authentication. I see this option no longer
exists in the version of NM that I have:
NetworkManager-0.7.0-0.12.svn4326.fc10.x86_64.
Out of curiosity, I used GIT to get the latest source, and see the
following in libnm-util/nm-setting-8021x.c:
950 { gtc, NULL, NULL }, // FIXME: implement
So, it appears GTC is not implemented in NM, even though wpa_supplicant
supports it. Are there any patches available that allow this to work? This
seems to be a regression from version 0.6.x (I don't know the exact version
I was using before).
I've seen various bugs filed at the distribution level regarding this, but
I didn't see one with this specific problem in the Gnome bugtracker.
However, seeing the comment in the source, it seems to be a known-issue. Is
this actually the case, and will this actually be implimented? Do I need to
actually file a bug? Are there any known workarounds?
Respectfully,
David
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Detection for ZTE AC8700 usb modem - provider BSNL India
Hi, Could you please add the following entry to hal-info for the BSNL usb modem for EVDO broadband ? The make of the modem is ZTE AC8700. file : 10-modem.fdi Content to be put after !--Novatel-- entry. !-- BSNL -- match key=@info.parent:usb.vendor_id int=0x5c6 !-- ZTE EVDO AC8700 -- match key=@info.parent:usb.product_id int_outof=0x3197 match key=@info.parent:usb.interface.number int=0 append key=modem.command_sets type=strlistIS-707-A/append /match /match /match Do let me know if you need a patch. It currently works. I can request more tests via LUG groups if you need, however I am sure it'll work :) regards, Chetan Shringarpure ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: DBus Properties 0.7.0 Device question
Tambet Ingo wrote: On Thu, Dec 18, 2008 at 11:34, Simon Schampijer si...@schampijer.de wrote: Tambet Ingo wrote: On Wed, Dec 17, 2008 at 22:39, Simon Schampijer si...@schampijer.de wrote: Philip Culver wrote: Some addtional information. If I execute: dbus-send --system --dest=org.freedesktop.NetworkManager --print-reply /org/freedesktop/Hal/devices/net_00_13_02_06_6d_ee org.freedesktop.DBus.Properties.Get string:'org.freedesktop.NetworkManager.Device.Wireless' string:'HwAddress' I get the proper value with a Get call. If I execute the GetAll method I always get the generic the Device properties. That is an interesting one. I actually saw the same problem with using the dbus python interface when doing an GetAll on a wired device. It's a bug in dbus-glib. It never even looks at the DBus interface (it only needs to be a string) which is passed to GetAll() method: http://cgit.freedesktop.org/dbus/dbus-glib/tree/dbus/dbus-gobject.c#n1442 Tambet ok, makes sense - Dan was so kind to file it: http://bugs.freedesktop.org/show_bug.cgi?id=19145 I was even kinder, I just fixed it. :) Attached the patch to the bugzilla. Tambet Thanks, this is the right spirit! Cheers, Simon ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
