RE: ppp support naming
De: Will Stephenson Enviado el: mié 05/03/2008 8:56 Para: networkmanager Asunto: Re: ppp support naming On Monday 03 March 2008 19:38:23 Tambet Ingo wrote: On Mon, Mar 3, 2008 at 12:18 PM, Vitja Makarov [EMAIL PROTECTED] wrote: I see it in the tree but I don't see it works, correct me if i'm wrong. It works for GSM and CDMA. As far as I know, GSM and CDMA are instances of certain classes of cellular networks, but GSM and CDMA themselves are not used globally. If I 'm right in this, it would make sense to internally name this support something generic, like 2GCellular and 3GCellular and then the GUI can sort out whether it refers to it as CDMA in EN_us or 3G in EN_gb or UMTS in de. The flipside is users doing a CDMA wtf? when they try to use their cellular card. HSDPA would be included in the 3GCellular name? (it is 3.5 G and HSUPA is 3.75 G). Logically, the speed is bigger in 3.5 than in 3G (one can see changing the modem lights from green to blue when a 3.5G connection is stablished). Regards. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ppp support naming
On Wed, 2008-03-05 at 08:56 +0100, Will Stephenson wrote: On Monday 03 March 2008 19:38:23 Tambet Ingo wrote: On Mon, Mar 3, 2008 at 12:18 PM, Vitja Makarov [EMAIL PROTECTED] wrote: I see it in the tree but I don't see it works, correct me if i'm wrong. It works for GSM and CDMA. As far as I know, GSM and CDMA are instances of certain classes of cellular networks, but GSM and CDMA themselves are not used globally. If I 'm right in this, it would make sense to internally name this support something generic, like 2GCellular and 3GCellular and then the GUI can sort out whether it refers to it as CDMA in EN_us or 3G in EN_gb or UMTS in de. The flipside is users doing a CDMA wtf? when they try to use their cellular card. They're different protocols, and use different command sets. And those strings don't appear in the UI either. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ppp support naming
On Wednesday 05 March 2008, Bastien Nocera said: On Wed, 2008-03-05 at 08:56 +0100, Will Stephenson wrote: On Monday 03 March 2008 19:38:23 Tambet Ingo wrote: On Mon, Mar 3, 2008 at 12:18 PM, Vitja Makarov [EMAIL PROTECTED] wrote: I see it in the tree but I don't see it works, correct me if i'm wrong. It works for GSM and CDMA. As far as I know, GSM and CDMA are instances of certain classes of cellular networks, but GSM and CDMA themselves are not used globally. If I 'm right in this, it would make sense to internally name this support something generic, like 2GCellular and 3GCellular and then the GUI can sort out whether it refers to it as CDMA in EN_us or 3G in EN_gb or UMTS in de. The flipside is users doing a CDMA wtf? when they try to use their cellular card. They're different protocols, and use different command sets. And those strings don't appear in the UI either. Does that mean that we need extra development to support HDSPA/UTMS networks? Does CDMA in NetworkManager only literally support CDMA networks? If that's the case, obviously the API naming is fine as is. Otherwise we should make it more generic. Will ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ppp support naming
On Wed, 2008-03-05 at 11:58 +0100, Will Stephenson wrote: snip Does that mean that we need extra development to support HDSPA/UTMS networks? Does CDMA in NetworkManager only literally support CDMA networks? No, they're already supported. The CDMA and GSM bits in NetworkManager refer to the command sets used by the different technologies, not to the over-the-air technologies. If that's the case, obviously the API naming is fine as is. Otherwise we should make it more generic. More generic for what? They have different command sets, so they use different implementations in NM. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ppp support naming
On Wednesday 05 March 2008, Bastien Nocera said: On Wed, 2008-03-05 at 11:58 +0100, Will Stephenson wrote: snip Does that mean that we need extra development to support HDSPA/UTMS networks? Does CDMA in NetworkManager only literally support CDMA networks? No, they're already supported. The CDMA and GSM bits in NetworkManager refer to the command sets used by the different technologies, not to the over-the-air technologies. Then I misunderstood. If that's the case, obviously the API naming is fine as is. Otherwise we should make it more generic. More generic for what? They have different command sets, so they use different implementations in NM. I mean that when a class of cellular technologies are served by one NetworkManager component, the name of that component should be a generic name, not the name of one of a member of that class. Will ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ppp support naming
On Wed, 2008-03-05 at 14:46 +0100, Will Stephenson wrote: On Wednesday 05 March 2008, Bastien Nocera said: On Wed, 2008-03-05 at 11:58 +0100, Will Stephenson wrote: snip Does that mean that we need extra development to support HDSPA/UTMS networks? Does CDMA in NetworkManager only literally support CDMA networks? No, they're already supported. The CDMA and GSM bits in NetworkManager refer to the command sets used by the different technologies, not to the over-the-air technologies. Then I misunderstood. Well, they do sort of refer to the over-the-air technologies. Ideally we'd be able to figure out the provider of service, or the name of the card if it wasn't locked to a provider, and show that string in the UI. We do show CDMA/GSM in the gnome applet UI right now, but that's something we can change. If that's the case, obviously the API naming is fine as is. Otherwise we should make it more generic. More generic for what? They have different command sets, so they use different implementations in NM. I mean that when a class of cellular technologies are served by one NetworkManager component, the name of that component should be a generic name, not the name of one of a member of that class. We're probably gonna have a WiMAX device class at some point too. Since most WiMAX devices are real network devices and don't hide behind PPP, it's a completely different story there. The NM _implementation_ will expose WiMAX, but the applets don't have to show that in the UI if they don't want to. An applet could show all mobile broadband connections as Mobile Broadband Connection and if there is more than one mobile broadband device available, identify each one by it's device name. I'm probably going to make the NM applet do that at some point soon rather than splitting them out by technology, because the user shouldn't care what type it really is. I consider GSM to be the generic name for every technology in the following list, because all these technologies are GSM-derived, or all have GSM as a direct ancestor. Furthermore, all devices implementing these technologies use the same AT command sets (GSM-07.07 and GSM-07.05): GSM HSCSD GPRS EDGE UMTS (WCDMA) HSDPA HSUPA HSPA+ I consider CDMA to be the generic name for every technology in the following list, because all these technologies have IS-95 as a direct ancestor. Furthermore, all devices implementing these technologies use the same AT command sets (IS-707-A): IS-95 (cdmaOne) CDMA2000 1x EVDO rev 0 EVDO rev A It remains to be seen where LTE will fall; but it's likely to be a GSM-class technology because GSM was it's ancestor. But we don't have to care for at least 2 years :) Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ppp support naming
On Wed, 2008-03-05 at 08:56 +0100, Will Stephenson wrote: On Monday 03 March 2008 19:38:23 Tambet Ingo wrote: On Mon, Mar 3, 2008 at 12:18 PM, Vitja Makarov [EMAIL PROTECTED] wrote: I see it in the tree but I don't see it works, correct me if i'm wrong. It works for GSM and CDMA. As far as I know, GSM and CDMA are instances of certain classes of cellular networks, but GSM and CDMA themselves are not used globally. If I 'm right in this, it would make sense to internally name this support something generic, like 2GCellular and 3GCellular and then the GUI can sort out whether it refers to it as CDMA in EN_us or 3G in EN_gb or UMTS in de. The flipside is users doing a CDMA wtf? when they try to use their cellular card. Just a quick point; _nothing_ should ever use or expose the 2G/3G/4G names anywhere to the user. Those classifications are pretty loose and essentially meaningless. Are we going to expose EDGE cards as 2.5G instead of 2G? Are we going to expose CDMA2000 1x as 2.5G? No. But they aren't 2G or 3G either. This classification just breaks down. They are all Mobile Broadband. I purposely didn't use cellular anywhere because even though that's technically what it is, that term is only used in the US. I'm not going to use mobile phone anywhere either, because everyone in the use uses cellphone or cell. Where possible, we should display model and manufacturer strings in the UI because people usually know they have a Nokia or an LG or a Samsung phone. They don't care if they have a Nokia CDMA phone or a Nokia GSM phone. It's a phone. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Problems with NM initial setup on FC6
Hello, I am trying to set up Network Manager for the first time. Here is a sequence of events I have gone through: 1) Enabled Network Manager by starting the service in /etc/init.d 2) Clicked on the icon to see a list of SSIDs 3) Clicked on the desired SSID 4) Entered the WPA key 5) The icon went through its thinking phase, and then it gave me the red circle with the line through it 6) I thought that there might be a collision between the eth1 device set up with the Network Configuration Manager so i delete the eth1 entry in the devices list (but did not delete it in the hardware tab) 7) I clicked on the Network Manager icon again, entered the WPA key. 8) I was prompted for a key ring manager password. I entered a password 9) Network Manager told me that was successfully connected to the desired SSID 10) However, I couldn't access any websites 11) I rebooted my computer 12) I restarted the Network Manager service 13) I tried to access the desired SSID 14) I am never able to connect. I just get the red circle with the line through it. Here is my /var/log/messages log: Mar 5 12:31:27 localhost NetworkManager: information User Switch: /org/freedesktop/NetworkManager/Devices/_5f__5f_tmp342535111 / bengi Mar 5 12:31:27 localhost NetworkManager: information Deactivating device __tmp342535111. Mar 5 12:31:27 localhost NetworkManager: information Device __tmp342535111 activation scheduled... Mar 5 12:31:27 localhost NetworkManager: information Activation (__tmp342535111) started... Mar 5 12:31:27 localhost NetworkManager: information Activation (__tmp342535111) Stage 1 of 5 (Device Prepare) scheduled... Mar 5 12:31:27 localhost NetworkManager: information Activation (__tmp342535111) Stage 1 of 5 (Device Prepare) started... Mar 5 12:31:27 localhost NetworkManager: information Activation (__tmp342535111) Stage 2 of 5 (Device Configure) scheduled... Mar 5 12:31:27 localhost NetworkManager: information Activation (__tmp342535111) Stage 1 of 5 (Device Prepare) complete. Mar 5 12:31:27 localhost NetworkManager: information Activation (__tmp342535111) Stage 2 of 5 (Device Configure) starting... Mar 5 12:31:27 localhost NetworkManager: information Activation (__tmp342535111/wireless): access point 'bengi' is encrypted, but NO valid key exists. New key needed. Mar 5 12:31:27 localhost NetworkManager: information Activation (__tmp342535111) New wireless user key requested for network 'bengi'. Mar 5 12:31:27 localhost NetworkManager: information Activation (__tmp342535111) Stage 2 of 5 (Device Configure) complete. Mar 5 12:31:27 localhost NetworkManager: information Activation (__tmp342535111) New wireless user key for network 'bengi' received. Mar 5 12:31:27 localhost NetworkManager: information Activation (__tmp342535111) Stage 1 of 5 (Device Prepare) scheduled... Mar 5 12:31:27 localhost NetworkManager: information Activation (__tmp342535111) Stage 1 of 5 (Device Prepare) started... Mar 5 12:31:27 localhost NetworkManager: information Activation (__tmp342535111) Stage 2 of 5 (Device Configure) scheduled... Mar 5 12:31:27 localhost NetworkManager: information Activation (__tmp342535111) Stage 1 of 5 (Device Prepare) complete. Mar 5 12:31:27 localhost NetworkManager: information Activation (__tmp342535111) Stage 2 of 5 (Device Configure) starting... Mar 5 12:31:27 localhost NetworkManager: information Activation (__tmp342535111/wireless): access point 'bengi' is encrypted, and a key exists. No new key needed. Mar 5 12:31:27 localhost NetworkManager: information SUP: sending command 'INTERFACE_ADD __tmp342535111 wext/var/run/wpa_supplicant ' Mar 5 12:31:27 localhost NetworkManager: information SUP: response was 'OK' Mar 5 12:31:27 localhost NetworkManager: information SUP: sending command 'AP_SCAN 1' Mar 5 12:31:27 localhost NetworkManager: information SUP: response was 'OK' Mar 5 12:31:27 localhost NetworkManager: information SUP: sending command 'ADD_NETWORK' Mar 5 12:31:27 localhost NetworkManager: information SUP: response was '0' Mar 5 12:31:27 localhost NetworkManager: information SUP: sending command 'SET_NETWORK 0 ssid 62656e6769' Mar 5 12:31:27 localhost NetworkManager: information SUP: response was 'OK' Mar 5 12:31:27 localhost NetworkManager: information SUP: sending command 'SET_NETWORK 0 proto WPA' Mar 5 12:31:27 localhost NetworkManager: information SUP: response was 'OK' Mar 5 12:31:27 localhost NetworkManager: information SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK' Mar 5 12:31:27 localhost NetworkManager: information SUP: response was 'OK' Mar 5 12:31:27 localhost NetworkManager: information SUP: sending command 'SET_NETWORK 0 psk key' Mar 5 12:31:27 localhost NetworkManager: information SUP: response was 'OK' Mar 5 12:31:27 localhost NetworkManager: information SUP: sending command 'ENABLE_NETWORK 0' Mar 5 12:31:27 localhost NetworkManager: information SUP: response was 'OK' Mar 5 12:31:27 localhost NetworkManager:
Re: ppp support
Vitja Makarov wrote: Hi! I'm working on project called ppp-manager. It aims to support many types of ppp connections. I'm mostly intrested in pptp, pppoe, pppoatm, ppp over br2684 and gprs. The most important thing for me(and many of my friend) is to replace default route correctly. For example many local networks in russia are lan based, dhcp assign you IP,mask and gateway. Then when you try to establish PPTP or PPPoE connection you are running in a problem: what to do with the old one default? In PPTP case you can't just delete it, as it holds route to pptp server. ppp-manager gives an option replacedefault a list of networks plus VPN server one, that will be still routed via default old. Now the service part is almost ready(it can handle pptp, gprs wired or wireless for now, and routing). There is simple GUI applet, that can acitvate/deactivate profiles, stored in gconf, but no configuration tool. I'm thinking about possibility of integration in NM. If you are interested I'll send you sources to talk next. vitja. ___ Dan! Can Vitja Makarov or his code help speeding up support for PPTP (VPN) into NM. Best regards Johann B. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: ppp support
On Wed, Mar 5, 2008 at 3:35 PM, Johann B. Gudmundsson [EMAIL PROTECTED] wrote: Can Vitja Makarov or his code help speeding up support for PPTP (VPN) into NM. So what exactly are we still discussing here? I've repeatedly assured here that we can change NMPppManager to do exactly what is needed. Let's stop this thread and produce some patches! Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
does current svn version networkmanager support WPA (PEAP-MSCHAPV2)?
Hi, I am tired trying wpa_supplicant and xsupplicant. Does current svn version networkmanager support WPA? I mean, I want a GUI to configure the connection to PEAP-MSCHAPv2-enabled Wi-fi. Thanks, Forrest -- Forrest Sheng Bao Ph.D. student, Dept. of Computer Science M.Sc. student, Dept. of Electrical Computer Engineering Texas Tech University, USA http://fsbao.net 1-806-577-4592 Forrest is an equal opportunity Email sender. 1. You are encouraged to use the language you prefer. Beyond English, I can also read traditional/simplified Chinese and a bit German. 2. I will only send you files readable to free or open source software. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: does current svn version networkmanager support WPA (PEAP-MSCHAPV2)?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It would appear that my 0.6.5 with KNetworkManager 0.2.0 allows that. I'm not 100% sure of how phase 2 and all of that works, or if this even IS phase 2, but I can set the options you described anyhow. =R Forrest Sheng Bao wrote: Hi, I am tired trying wpa_supplicant and xsupplicant. Does current svn version networkmanager support WPA? I mean, I want a GUI to configure the connection to PEAP-MSCHAPv2-enabled Wi-fi. Thanks, Forrest -- Forrest Sheng Bao Ph.D. student, Dept. of Computer Science M.Sc. student, Dept. of Electrical Computer Engineering Texas Tech University, USA http://fsbao.net 1-806-577-4592 Forrest is an equal opportunity Email sender. 1. You are encouraged to use the language you prefer. Beyond English, I can also read traditional/simplified Chinese and a bit German. 2. I will only send you files readable to free or open source software. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHz29Ymb+gadEcsb4RAu58AKDkXZBtzxGTrQbt2lzSecJTmcmfQgCeOUbr RqLT6e8tLUbl0TuaO6oUzgI= =84Ro -END PGP SIGNATURE- begin:vcard fn:Ryan Novosielski n:Novosielski;Ryan org:UMDNJ;IST/AST adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103 email;internet:[EMAIL PROTECTED] title:Systems Programmer II tel;work:(973) 972-0922 tel;fax:(973) 972-7412 tel;pager:(866) 20-UMDNJ x-mozilla-html:FALSE version:2.1 end:vcard ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: does current svn version networkmanager support WPA (PEAP-MSCHAPV2)?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I don't use GNOME, but I know there is a different applet for GNOME. I also use Gutsy, so it looks like your software likely supports this. Forrest Sheng Bao wrote: So how can I use Knetworkmanager? Do I need to login to a KDE environment? I am now working on GNOME on Ubuntu Gusty. On Wed, Mar 5, 2008 at 10:13 PM, Ryan Novosielski [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: It would appear that my 0.6.5 with KNetworkManager 0.2.0 allows that. I'm not 100% sure of how phase 2 and all of that works, or if this even IS phase 2, but I can set the options you described anyhow. =R Forrest Sheng Bao wrote: Hi, I am tired trying wpa_supplicant and xsupplicant. Does current svn version networkmanager support WPA? I mean, I want a GUI to configure the connection to PEAP-MSCHAPv2-enabled Wi-fi. Thanks, Forrest -- Forrest Sheng Bao Ph.D. student, Dept. of Computer Science M.Sc. student, Dept. of Electrical Computer Engineering Texas Tech University, USA http://fsbao.net 1-806-577-4592 Forrest is an equal opportunity Email sender. 1. You are encouraged to use the language you prefer. Beyond English, I can also read traditional/simplified Chinese and a bit German. 2. I will only send you files readable to free or open source software. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org mailto:NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org mailto:NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list -- Forrest Sheng Bao Ph.D. student, Dept. of Computer Science M.Sc. student, Dept. of Electrical Computer Engineering Texas Tech University, USA http://fsbao.net 1-806-577-4592 Forrest is an equal opportunity Email sender. 1. You are encouraged to use the language you prefer. Beyond English, I can also read traditional/simplified Chinese and a bit German. 2. I will only send you files readable to free or open source software. - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHz3RZmb+gadEcsb4RAij6AJ9o156ID8xBkDqRYvB4yk2JOObEjwCghhcS zUIkFo2mLCZoN+GZbNxORt4= =bLoW -END PGP SIGNATURE- begin:vcard fn:Ryan Novosielski n:Novosielski;Ryan org:UMDNJ;IST/AST adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103 email;internet:[EMAIL PROTECTED] title:Systems Programmer II tel;work:(973) 972-0922 tel;fax:(973) 972-7412 tel;pager:(866) 20-UMDNJ x-mozilla-html:FALSE version:2.1 end:vcard ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
PPPoE
Heya,
After all these ppp manager mails I decided to see what really is
missing from NM to add some new PPP based connections (NM supposedly
supported only PPP over serial line). I chose PPPoE since I need to
implement it anyway. Turns out, it's as easy as I imagined it would
be. Well, almost. There's one issue that needs fixing. The current
interaction between ppp manager and pppd plugin is over dbus and
plugin emits signals when stuff changes and manager listens for these.
It has to be the other way around (manager has to register a
well-known service on dbus and plugin needs to call it's methods).
Otherwise, there's no way the plugin can ask for credentials when it
needs them for CHAP or PAP. So that and UI are missing for now.
Attached are the patches to implement PPPoE. 407 insertions, 16 deletions.
Tambet
From 1d894148f3e561efa47533f68dd36cae8e4ffd69 Mon Sep 17 00:00:00 2001
From: Tambet Ingo [EMAIL PROTECTED]
Date: Wed, 5 Mar 2008 20:48:19 -0600
Subject: [PATCH] Implement NMSettingPPPOE.
diff --git a/libnm-util/Makefile.am b/libnm-util/Makefile.am
index ddbac0b..f95ace6 100644
--- a/libnm-util/Makefile.am
+++ b/libnm-util/Makefile.am
@@ -18,6 +18,7 @@ libnm_util_include_HEADERS = \
nm-setting-connection.h \
nm-setting-ip4-config.h \
nm-setting-ppp.h \
+ nm-setting-pppoe.h \
nm-setting-serial.h \
nm-setting-gsm.h \
nm-setting-cdma.h \
@@ -35,6 +36,7 @@ libnm_util_la_SOURCES= \
nm-setting-connection.c \
nm-setting-ip4-config.c \
nm-setting-ppp.c \
+ nm-setting-pppoe.c \
nm-setting-serial.c \
nm-setting-gsm.c \
nm-setting-cdma.c \
diff --git a/libnm-util/nm-connection.c b/libnm-util/nm-connection.c
index d44dd6a..074a8f0 100644
--- a/libnm-util/nm-connection.c
+++ b/libnm-util/nm-connection.c
@@ -9,6 +9,7 @@
#include nm-setting-connection.h
#include nm-setting-ip4-config.h
#include nm-setting-ppp.h
+#include nm-setting-pppoe.h
#include nm-setting-wired.h
#include nm-setting-wireless.h
#include nm-setting-wireless-security.h
@@ -68,6 +69,7 @@ register_default_settings (void)
{ NM_SETTING_GSM_SETTING_NAME, NM_TYPE_SETTING_GSM },
{ NM_SETTING_CDMA_SETTING_NAME, NM_TYPE_SETTING_CDMA },
{ NM_SETTING_PPP_SETTING_NAME, NM_TYPE_SETTING_PPP },
+ { NM_SETTING_PPPOE_SETTING_NAME, NM_TYPE_SETTING_PPPOE },
{ NM_SETTING_VPN_SETTING_NAME, NM_TYPE_SETTING_VPN },
{ NM_SETTING_VPN_PROPERTIES_SETTING_NAME,NM_TYPE_SETTING_VPN_PROPERTIES },
{ NULL }
diff --git a/libnm-util/nm-setting-pppoe.c b/libnm-util/nm-setting-pppoe.c
new file mode 100644
index 000..3bbe2e4
--- /dev/null
+++ b/libnm-util/nm-setting-pppoe.c
@@ -0,0 +1,123 @@
+/* -*- Mode: C; tab-width: 5; indent-tabs-mode: t; c-basic-offset: 5 -*- */
+
+#include nm-setting-pppoe.h
+
+G_DEFINE_TYPE (NMSettingPPPOE, nm_setting_pppoe, NM_TYPE_SETTING)
+
+enum {
+ PROP_0,
+ PROP_USERNAME,
+ PROP_PASSWORD,
+
+ LAST_PROP
+};
+
+NMSetting *
+nm_setting_pppoe_new (void)
+{
+ return (NMSetting *) g_object_new (NM_TYPE_SETTING_PPPOE, NULL);
+}
+
+static gboolean
+verify (NMSetting *setting, GSList *all_settings)
+{
+ NMSettingPPPOE *self = NM_SETTING_PPPOE (setting);
+
+ if (!self-username) {
+ g_warning (Missing username);
+ return FALSE;
+ }
+
+ return TRUE;
+}
+
+static GPtrArray *
+need_secrets (NMSetting *setting)
+{
+ NMSettingPPPOE *self = NM_SETTING_PPPOE (setting);
+ GPtrArray *secrets;
+
+ if (self-password)
+ return NULL;
+
+ secrets = g_ptr_array_sized_new (1);
+ g_ptr_array_add (secrets, NM_SETTING_PPPOE_PASSWORD);
+
+ return secrets;
+}
+
+static void
+nm_setting_pppoe_init (NMSettingPPPOE *setting)
+{
+ ((NMSetting *) setting)-name = g_strdup (NM_SETTING_PPPOE_SETTING_NAME);
+}
+
+static void
+set_property (GObject *object, guint prop_id,
+ const GValue *value, GParamSpec *pspec)
+{
+ NMSettingPPPOE *setting = NM_SETTING_PPPOE (object);
+
+ switch (prop_id) {
+ case PROP_USERNAME:
+ g_free (setting-username);
+ setting-username = g_value_dup_string (value);
+ break;
+ case PROP_PASSWORD:
+ g_free (setting-password);
+ setting-password = g_value_dup_string (value);
+ break;
+ default:
+ G_OBJECT_WARN_INVALID_PROPERTY_ID (object, prop_id, pspec);
+ break;
+ }
+}
+
+static void
+get_property (GObject *object, guint prop_id,
+ GValue *value, GParamSpec *pspec)
+{
+ NMSettingPPPOE *setting = NM_SETTING_PPPOE (object);
+
+ switch (prop_id) {
+ case PROP_USERNAME:
+ g_value_set_string (value, setting-username);
+ break;
+ case PROP_PASSWORD:
+ g_value_set_string (value, setting-password);
+ break;
+ default:
+ G_OBJECT_WARN_INVALID_PROPERTY_ID (object, prop_id, pspec);
+ break;
+ }
+}
+
+static void
+nm_setting_pppoe_class_init (NMSettingPPPOEClass *setting_class)
+{
+ GObjectClass *object_class = G_OBJECT_CLASS (setting_class);
+ NMSettingClass *parent_class = NM_SETTING_CLASS (setting_class);
+
+ /* virtual methods */
+ object_class-set_property = set_property;
+ object_class-get_property =
Re: PPPoE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kudos, Tambet! Thanks for all of the easy work. ;) It really is something when working with NetworkManager appears to be less complex these days than the Windows equivalent. Tambet Ingo wrote: Heya, After all these ppp manager mails I decided to see what really is missing from NM to add some new PPP based connections (NM supposedly supported only PPP over serial line). I chose PPPoE since I need to implement it anyway. Turns out, it's as easy as I imagined it would be. Well, almost. There's one issue that needs fixing. The current interaction between ppp manager and pppd plugin is over dbus and plugin emits signals when stuff changes and manager listens for these. It has to be the other way around (manager has to register a well-known service on dbus and plugin needs to call it's methods). Otherwise, there's no way the plugin can ask for credentials when it needs them for CHAP or PAP. So that and UI are missing for now. Attached are the patches to implement PPPoE. 407 insertions, 16 deletions. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHz3csmb+gadEcsb4RAhRRAJ0TLJwNFd8iWcYcsEs68epQDIRzTACgwCBI eAuX1uKsFXTwfrB+YH94wMw= =SooT -END PGP SIGNATURE- begin:vcard fn:Ryan Novosielski n:Novosielski;Ryan org:UMDNJ;IST/AST adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103 email;internet:[EMAIL PROTECTED] title:Systems Programmer II tel;work:(973) 972-0922 tel;fax:(973) 972-7412 tel;pager:(866) 20-UMDNJ x-mozilla-html:FALSE version:2.1 end:vcard ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: does current svn version networkmanager support WPA (PEAP-MSCHAPV2)?
Hi, I am using Knetworkmanager now. I have found those options you mentioned. But later there is a popup balloon said Could not connect to the network blah blah blah. Is there any configuration files I need to edit? Do I need to turn on other daemons like wpa_applicant? On Wed, Mar 5, 2008 at 10:45 PM, Ryan Novosielski [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You could, but I don't think it is necessary. I'm sure the equivalent GNOME applet would work, I just don't know anything about it. Forrest Sheng Bao wrote: Hi, So do you mean you use KDE and run the KNetworkManager on KDE environment? On Wed, Mar 5, 2008 at 10:34 PM, Ryan Novosielski [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I don't use GNOME, but I know there is a different applet for GNOME. I also use Gutsy, so it looks like your software likely supports this. - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHz3bemb+gadEcsb4RArgpAJ9SJrZbMB5Km3QPscFqmmPAJEGhSwCgz2xo dxeGIiK6Wd0bukSMn5tHjIU= =lI7Q -END PGP SIGNATURE- -- Forrest Sheng Bao Ph.D. student, Dept. of Computer Science M.Sc. student, Dept. of Electrical Computer Engineering Texas Tech University, USA http://fsbao.net 1-806-577-4592 Forrest is an equal opportunity Email sender. 1. You are encouraged to use the language you prefer. Beyond English, I can also read traditional/simplified Chinese and a bit German. 2. I will only send you files readable to free or open source software. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: does current svn version networkmanager support WPA (PEAP-MSCHAPV2)?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 AFAIK, it should just work. Perhaps someone else on the list can help. Forrest Sheng Bao wrote: Hi, I am using Knetworkmanager now. I have found those options you mentioned. But later there is a popup balloon said Could not connect to the network blah blah blah. Is there any configuration files I need to edit? Do I need to turn on other daemons like wpa_applicant? On Wed, Mar 5, 2008 at 10:45 PM, Ryan Novosielski [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: You could, but I don't think it is necessary. I'm sure the equivalent GNOME applet would work, I just don't know anything about it. Forrest Sheng Bao wrote: Hi, So do you mean you use KDE and run the KNetworkManager on KDE environment? On Wed, Mar 5, 2008 at 10:34 PM, Ryan Novosielski [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I don't use GNOME, but I know there is a different applet for GNOME. I also use Gutsy, so it looks like your software likely supports this. -- Forrest Sheng Bao Ph.D. student, Dept. of Computer Science M.Sc. student, Dept. of Electrical Computer Engineering Texas Tech University, USA http://fsbao.net 1-806-577-4592 Forrest is an equal opportunity Email sender. 1. You are encouraged to use the language you prefer. Beyond English, I can also read traditional/simplified Chinese and a bit German. 2. I will only send you files readable to free or open source software. - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHz3uGmb+gadEcsb4RAnEhAKDkRilGsDEuV6RLsvC47qSUZHNt3QCgrJmX 0B93DQVU6PUG+uYmPOBl5W8= =f7I4 -END PGP SIGNATURE- begin:vcard fn:Ryan Novosielski n:Novosielski;Ryan org:UMDNJ;IST/AST adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103 email;internet:[EMAIL PROTECTED] title:Systems Programmer II tel;work:(973) 972-0922 tel;fax:(973) 972-7412 tel;pager:(866) 20-UMDNJ x-mozilla-html:FALSE version:2.1 end:vcard ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: does current svn version networkmanager support WPA (PEAP-MSCHAPV2)?
On Thu, 2008-03-06 at 00:05 -0500, Ryan Novosielski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 AFAIK, it should just work. Perhaps someone else on the list can help. My University uses this WPA+TKIP and PEAP-MSCHAP v2 and I have never got it to work with Network Manager. Let me know if you have any success John Forrest Sheng Bao wrote: Hi, I am using Knetworkmanager now. I have found those options you mentioned. But later there is a popup balloon said Could not connect to the network blah blah blah. Is there any configuration files I need to edit? Do I need to turn on other daemons like wpa_applicant? On Wed, Mar 5, 2008 at 10:45 PM, Ryan Novosielski [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: You could, but I don't think it is necessary. I'm sure the equivalent GNOME applet would work, I just don't know anything about it. Forrest Sheng Bao wrote: Hi, So do you mean you use KDE and run the KNetworkManager on KDE environment? On Wed, Mar 5, 2008 at 10:34 PM, Ryan Novosielski [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I don't use GNOME, but I know there is a different applet for GNOME. I also use Gutsy, so it looks like your software likely supports this. -- Forrest Sheng Bao Ph.D. student, Dept. of Computer Science M.Sc. student, Dept. of Electrical Computer Engineering Texas Tech University, USA http://fsbao.net 1-806-577-4592 Forrest is an equal opportunity Email sender. 1. You are encouraged to use the language you prefer. Beyond English, I can also read traditional/simplified Chinese and a bit German. 2. I will only send you files readable to free or open source software. - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHz3uGmb+gadEcsb4RAnEhAKDkRilGsDEuV6RLsvC47qSUZHNt3QCgrJmX 0B93DQVU6PUG+uYmPOBl5W8= =f7I4 -END PGP SIGNATURE- ___ 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
RE: ppp support naming
De: Dan Williams Enviado el: mié 05/03/2008 19:51 Para: Will Stephenson CC: networkmanager-list Asunto: Re: ppp support naming I consider GSM to be the generic name for every technology in the following list, because all these technologies are GSM-derived, or all have GSM as a direct ancestor. Furthermore, all devices implementing these technologies use the same AT command sets (GSM-07.07 and GSM-07.05): GSM HSCSD GPRS EDGE UMTS (WCDMA) HSDPA HSUPA HSPA+ I agree. We could use HSPA as the generic name for the subclases HSDPA and HSUPA. Regards. Pedro. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: ppp support naming
De: [EMAIL PROTECTED] en nombre de Dan Williams Enviado el: mié 05/03/2008 19:55 Para: Will Stephenson CC: networkmanager-list@gnome.org Asunto: Re: ppp support naming Just a quick point; _nothing_ should ever use or expose the 2G/3G/4G names anywhere to the user. It could be shown optionally, if the user marks the option. Where possible, we should display model and manufacturer strings in the UI because people usually know they have a Nokia or an LG or a Samsung phone. They don't care if they have a Nokia CDMA phone or a Nokia GSM phone. It's a phone. For me and more people, this is important. It is not the same use a GSM phone than a HDPA phone, that can upload and download quicklier (broadband phone or broadband mobile modem, as Huawaei E220). Now, when I have to buy a new mobile phone I wouldn´t buy one older than HSPA . Regards. Pedro. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: does current svn version networkmanager support WPA (PEAP-MSCHAPV2)?
De: Forrest Sheng Bao Enviado el: jue 06/03/2008 5:04 Para: networkmanager-list@gnome.org Asunto: does current svn version networkmanager support WPA (PEAP-MSCHAPV2)? Hi, I am tired trying wpa_supplicant and xsupplicant. Does current svn version networkmanager support WPA? I mean, I want a GUI to configure the connection to PEAP-MSCHAPv2-enabled Wi-fi. I think NM would include a good and easy WPA support. Regards. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
