Re: NM dialup API
Hey, On 4/19/07, Will Stephenson [EMAIL PROTECTED] wrote: I'm working on the Solid API for network management for KDE 4 and am designing the dialup part now. Since NM is the main backend on KDE's major platform, it influences our API design. There don't seem to be any significant changes regarding dialup in SVN trunk yet, so here's my proposal for an NM dialup API. There's no dialup API in the trunk because there will be none. Just as there's common API for wired and wireless devices, a dialup device will be just another device with exactly the same API and semantics as every other device type. A dialup device is actually very similar to wireless: both need a special setup phase (configuration of the device, connection, and authentication). As a result of dialup device activation, just like of any other device type, is a working network connection. There's no reason to duplicate all the API we currently have for wired and wireless devices (get devices, get device properties, activate, activation stages, etc...) for dialup devices. No reason to confuse the public API consumers and have different NM states for connected using wired or wireless and connected using a dialup device. For configuration (of all device types, including dialup) see http://live.gnome.org/NetworkManagerConfiguration The exact list of setting types is not spec'ed out yet. snip Also, what's the plan regarding the VPN API? Trunk seems mostly the same as 0.6.x. I see parallels between dialup and vpn connections that could be merged, using distinct dbus interfaces for each but with a shared 'ConnectionManager'. The VPN API hasn't changed since NM has been in poor state for long enough and we just haven't had enough resources. The same configuration framework should be used for VPN, and it should have it's own list/properties/status/activate/deactivate interfaces. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM dialup API
On Thursday 19 April 2007 10:07:31 Tambet Ingo wrote: There's no dialup API in the trunk because there will be none. Just as there's common API for wired and wireless devices, a dialup device will be just another device with exactly the same API and semantics as Hey, Tambet :) I made this realisation too after sending the first spec (sending something always refreshes the parts actually thinking about it doesn't reach ;)). For configuration (of all device types, including dialup) see http://live.gnome.org/NetworkManagerConfiguration Excellent. I hadn't found this page. The KDE api I wrote to abstract NM and other potential backends is spookily similar - especially having the Connection bound to a type but not an instance of a device. This will make implementing a NM 0.7 backend for Solid easy. The exact list of setting types is not spec'ed out yet. Is anyone working on turning this into a dbus spec yet? I can help with this if needed. Will ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM dialup API
On Thu, 2007-04-19 at 13:18 +0300, Tambet Ingo wrote: Hello Will, On 4/19/07, Will Stephenson [EMAIL PROTECTED] wrote: On Thursday 19 April 2007 10:07:31 Tambet Ingo wrote: There's no dialup API in the trunk because there will be none. Just as there's common API for wired and wireless devices, a dialup device will be just another device with exactly the same API and semantics as Hey, Tambet :) I made this realisation too after sending the first spec (sending something always refreshes the parts actually thinking about it doesn't reach ;)). Sweet, I'm glad we agree on it. Whee, it got worked out without me having to write a long email saying the same thing after I woke up this morning. Tambet's right on. For configuration (of all device types, including dialup) see http://live.gnome.org/NetworkManagerConfiguration Excellent. I hadn't found this page. The KDE api I wrote to abstract NM and other potential backends is spookily similar - especially having the Connection bound to a type but not an instance of a device. This will make implementing a NM 0.7 backend for Solid easy. Sounds like we have a good plan when two groups of people working independently come to a very similar conclusions (I can't take any pride on that though, I didn't even take part of the design) :) The exact list of setting types is not spec'ed out yet. Is anyone working on turning this into a dbus spec yet? I can help with this if needed. The D-Bus spec for the API that info-daemons (the things that pass system-wide and user-scoped configuration to NetworkManager) is pretty much spec'ed out, but comments are certainly welcome and appreciated. I sent a mail to the list back in Feb. that layed out my thoughts on the NM - info-daemon API. What Tambet is saying is unspec'ed are the exact key names and value types. I.e., there is a key seen-bssids that exists in the 802-11-wireless section scope, that is of type array of char[6] or whatever. We don't care where the info-daemon that provides that configuration key/value gets it from, as long as it can coerce that value into the specific D-Bus format that NM requires when you send the save connections to it. There are really 4 pieces to NetworkManager. Only _1_ is really desktop-environment specific: 1) NetworkManager itself - root-level daemon 2) system info-daemon - non-DE-specific, provides system-level configuration (administrator specified settings (lock-down), or settings the user has published to the rest of the system) 3) user info-daemon - provides user-specific configuration 4) GUI bits - obviously DE specific, allows the user to control NM, but does not necessarily provide the configuration It just happens that in the Gnome applet, we've combined 3+4 into the applet for efficiency reasons. Dan I have most of the infrastructure done for getting the configuration to NetworkManager. I'll attach the dbus introspection files to the mail. What still needs to be done is to define all the setting objects and all the possible fields in each setting and um... start using it. Lets do it. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
0.6.5 test results
Hello, I have took some time today to test 0.6.5(svn). Positiv things: EAP-TTLS / WEP-dynamic / MSCHAPV2 (phase2) works[1] No Crashes etc. Bugs: *)When I boot the laptop and login it trys to connect to the wired network (which is _NOT_) connected and succeds.[2] *)When I do [1] via Connect to other network it works just fine, but it does not remember it... when I login again it tryes to connect to it but asks me for a wep key/phrase etc. why? It can find it (its in the list of networks, clicking on it does not help). So I always needs to recreate it if I wants to connect *)There are some apps where nm never connects to (trys until timeout; but wpa_supplicant works). I already talked about this in the nm does not assicotate with ipw3945 thread (same issue as 0.6.4). My Hardware/Software: ipw3945 wifi r8169 (8111) wired nic core 2 duo T 7400 FC6 x86_64 (using nm and wpa_supplicant from current F7 rawhide) [2]: I already reported this before but I got no reply, hope this time someone is able to tell me why this is happening and/or fix it. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NetworkManager Reconnect Attempts
Hi, I am wondering if anyone has implemented a reconnect attempts feature in NM, i.e. instead of failing it would try say 3x to connect using the selected profile. Currently it just launchers wpa_supplicant for a time interval of 20 seconds(or longer if u patch) and if it connects fine, but if wpa_supplicant fails it gives up. This atleast for me would get around the hassle that sometimes it would seem wpa_supplicant needs to launch a couple of times before a connection takes place. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM dialup API
On Thursday 19 April 2007 13:58:34 Dan Williams wrote:
On Thu, 2007-04-19 at 13:18 +0300, Tambet Ingo wrote:
On 4/19/07, Will Stephenson [EMAIL PROTECTED] wrote:
Is anyone working on turning this into a dbus spec yet? I can help
with this if needed.
The D-Bus spec for the API that info-daemons (the things that pass
system-wide and user-scoped configuration to NetworkManager) is pretty
much spec'ed out, but comments are certainly welcome and appreciated. I
sent a mail to the list back in Feb. that layed out my thoughts on the
NM - info-daemon API.
I've reviewed the February thread and had a think about it. Summarising my
reading of it:
*) Less state is to be made available to the client to prevent cross-session
information leakage.
*) Instead the active (according to ConsoleKit) settings service is queried
for policy or notifies when policy changes
Questions:
In a{sa{sv}}, what does the middle 'a' mean? Does the first string key
eg 'ip4-settings' point to an array of dicts containing those settings, and
not a single dict?
Or is that first 's' the identifier of the Connection? In that case what's
the outer array for?
Comments:
I'm seeing question marks about what policy is visible to clients.
*) System-wide configured wireless, vpn, dialup connections should be visible
to clients so that they may control them. Connections added by other clients
should not.
*) a{sa{sv}} dismays me because it's such a low level lump of data. Is the
revised interface on NM for discovering the available devices and connections
going to be similarly barren? I was expecting it would be richer and more
object oriented than the 0.6.x interface. If one call supplies all the
settings data to the daemon from a settings service for all of the
connections, this could be a large amount of data if the user has accumulated
a lot of wireless network settings, so it could take time to marshal.
*) Given a tightly defined set of settings groups and the values available in
them, we could use to define an OO dbus interface on NM to determine Devices,
their Connections and the Settings groups on them depending on their type.
This would be easier for client app authors to target.
Will
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Disable Hostname Changes
Where does SuSE come into play? I am using Gentoo. I thought NM was a Gnome/RH project? I have played w/ all args in my net file, as well as dhclient. Can't seem to get it to stop. And Yes, you are correct, I have to restart X. deface On Wed, 2007-04-18 at 23:07 -0400, Dan Williams wrote: On Wed, 2007-04-18 at 15:28 -0500, deface wrote: I'm not sure how to pass any args to NetworkManagerDispatcher to disable the hostname changes. Nor could I find a list of options, the MAN pages were very limited. For whatever reason, the SuSE guys set the hostname. NM specifically does _not_ do this in all other backends because if screws up X authentication most of the time, leading applications not able to start. Have to ask the SuSE guys... Dan Apr 18 15:06:51 logic NetworkManager: info Activation (eth1) Stage 3 of 5 (IP Configure Start) complete. Apr 18 15:06:51 logic NetworkManager: info DHCP daemon state is now 12 (successfully started) for interface eth1 Apr 18 15:06:52 logic NetworkManager: info DHCP daemon state is now 1 (starting) for interface eth1 Apr 18 15:06:52 logic dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4 Apr 18 15:06:54 logic dhclient: DHCPOFFER from 10.255.57.33 Apr 18 15:06:54 logic dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67 Apr 18 15:06:54 logic dhclient: DHCPACK from 10.255.57.33 Apr 18 15:06:54 logic NetworkManager: info DHCP daemon state is now 2 (bound) for interface eth1 Apr 18 15:06:54 logic NetworkManager: info Activation (eth1) Stage 4 of 5 (IP Configure Get) scheduled... Apr 18 15:06:54 logic NetworkManager: info Activation (eth1) Stage 4 of 5 (IP Configure Get) started... Apr 18 15:06:54 logic dhclient: can't create /var/lib/dhclient/dhclient-eth1.leases: No such file or directory Apr 18 15:06:54 logic dhclient: bound to 10.255.57.60 -- renewal in 445 seconds. Apr 18 15:06:54 logic dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.host_name Apr 18 15:06:54 logic dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.nis_domain Apr 18 15:06:54 logic dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.nis_servers Apr 18 15:06:54 logic NetworkManager: info Retrieved the following IP4 configuration from the DHCP daemon: Apr 18 15:06:54 logic NetworkManager: infoaddress 10.255.57.60 Apr 18 15:06:54 logic NetworkManager: infonetmask 255.255.255.224 Apr 18 15:06:54 logic NetworkManager: infobroadcast 10.255.57.63 Apr 18 15:06:54 logic NetworkManager: infogateway 10.255.57.33 Apr 18 15:06:54 logic NetworkManager: infonameserver 66.94.25.120 Apr 18 15:06:54 logic NetworkManager: infonameserver 66.94.9.120 Apr 18 15:06:54 logic NetworkManager: infodomain name 'cust.hotspot.t-mobile.com' Apr 18 15:06:54 logic NetworkManager: info Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled... Apr 18 15:06:54 logic NetworkManager: info Activation (eth1) Stage 4 of 5 (IP Configure Get) complete. Apr 18 15:06:54 logic NetworkManager: info Activation (eth1) Stage 5 of 5 (IP Configure Commit) started... Apr 18 15:06:55 logic NetworkManager: info Setting hostname to '60' Apr 18 15:06:55 logic NetworkManager: info Activation (eth1) successful, device activated. Apr 18 15:06:55 logic NetworkManager: info Activation (eth1) Finish handler scheduled. Apr 18 15:06:55 logic NetworkManager: info Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete. Apr 18 15:06:55 logic NetworkManager: debug [1176926815.215373] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'tmobile' As you can see - Apr 18 15:06:55 logic NetworkManager: info Setting hostname to '60' -- How do i disable this? deface ___ 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
[v0.6.4] nm-applet crash on detecting wireless network.
Hello. Maybe this will interest some dev :D I have a very weird condition where nm-applet (not NetworkManager) crashes frequenty. Basically, this is the situation: - Turn on nm-applet out of the range of any wireless network (or attached to cable): nm-applet works fine for up to 2 minutes (varies), then dies. - Turn on nm-applet within the range of any wireless network that you havent attached to before: nm-applet works fine for up to 2 minutes (varies), then dies. - Turn on nm-applet within the range of a previously attached network: nm-applet icon never shows up, nothing works, dies after about 60 seconds. Quite frustrating :D Nevertheless, great work on NM, brilliant for laptops. Some generic system info (dev, if you need more info for debug contact me !!) System: Asus F3M Series Laptop Distro: Gentoo Linux i686 unstable HAL Version: 0.5.7.1-r5([EMAIL PROTECTED]:03:08 04/14/07)(USE Flags: acpi crypt debug -dmi -doc -pcmcia -selinux) DBUS Version: 1.0.2-r2([EMAIL PROTECTED]:58:43 04/19/07)(USE Flags: X debug -doc -selinux) NW Version: 0.6.4_pre20061028-r1([EMAIL PROTECTED]:14:04 04/15/07)(USE Flags: crypt debug -doc gnome) It would be brilliant if somebody could tell me whats going on. I am available for further debugging, as well as being able to give ssh access into the machine in question. Regards, Sebastian M Jueges PS: Find attached some debug output: # System: Linux 2.6.20-gentoo-r6-phoenix #1 PREEMPT Tue Apr 17 01:40:10 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 7020 Selinux: No Accessibility: Disabled Memory status: size: 38219776 vsize: 0 resident: 38219776 share: 0 rss: 12210176 rss_rlim: 0 CPU usage: start_time: 1176995865 rtime: 0 utime: 20 stime: 0 cutime:18 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nm-applet' (no debugging symbols found) Using host libthread_db library /lib/libthread_db.so.1. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1224849744 (LWP 4815)] 0xe410 in __kernel_vsyscall () #0 0xe410 in __kernel_vsyscall () #1 0xb7b252c3 in __waitpid_nocancel () from /lib/libpthread.so.0 #2 0xb7f559d5 in ?? () from /usr/lib/libgnomeui-2.so.0 #3 0x136a in ?? () #4 0xbfcabc78 in ?? () #5 0x in ?? () Thread 1 (Thread -1224849744 (LWP 4815)): #0 0xe410 in __kernel_vsyscall () No symbol table info available. #1 0xb7b252c3 in __waitpid_nocancel () from /lib/libpthread.so.0 No symbol table info available. #2 0xb7f559d5 in ?? () from /usr/lib/libgnomeui-2.so.0 No symbol table info available. #3 0x136a in ?? () No symbol table info available. #4 0xbfcabc78 in ?? () No symbol table info available. #5 0x in ?? () No symbol table info available. #0 0xe410 in __kernel_vsyscall () The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] --- .xsession-errors - /usr/lib/libdbus-1.so.3(dbus_connection_dispatch+0x222) [0xb7218152] /usr/lib/libdbus-glib-1.so.2 [0xb774a5cd] /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x181) [0xb7166bb1] /usr/lib/libglib-2.0.so.0 [0xb7169c0f] /usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1b7) [0xb7169fc7] /usr/lib/libgtk-x11-2.0.so.0(gtk_main+0xc1) [0xb7889c11] nm-applet [0x804f24b] /lib/libc.so.6(__libc_start_main+0xd8) [0xb7028838] nm-applet [0x804f0a1] ** (bug-buddy:4971): WARNING **: Couldn't load icon for Bonobo Component Browser ** (bug-buddy:4971): WARNING **: Couldn't load icon for Open Folder ** (bug-buddy:4971): WARNING **: Couldn't load icon for Phone Manager -- # OUTPUT of NetworkManager in syslog Apr 19 17:02:14 [NetworkManager] WARN nm_signal_handler(): Caught signal 11. Generating backtrace..._ Apr 19 17:02:14 [NetworkManager] info Successfully reconnected to the system bus._ Apr 19 17:02:14 [NetworkManager] *** START ** Apr 19 17:02:15 [NetworkManager] (no debugging symbols found) Apr 19 17:02:15 [NetworkManager] Using host libthread_db
Re: Disable Hostname Changes
deface wrote: Where does SuSE come into play? I am using Gentoo. I thought NM was a Gnome/RH project? I have played w/ all args in my net file, as well as dhclient. Can't seem to get it to stop. And Yes, you are correct, I have to restart X. deface sigma ~ # cat /etc/dhcp/dhclient.conf send host-name sigma; supersede host-name sigma; That is what you need. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM dialup API
On Thursday 19 April 2007 17:30:34 Will Stephenson wrote:
In a{sa{sv}}, what does the middle 'a' mean? Does the first string key
eg 'ip4-settings' point to an array of dicts containing those settings, and
not a single dict?
Or is that first 's' the identifier of the Connection? In that case what's
the outer array for?
I figured out how to parse the signature eventually - a{...} == Hash
therefore a{sa{sv}} is Hash of string to Hash of string to variant. :P
Will
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM dialup API
On Thu, 2007-04-19 at 20:07 +0200, Will Stephenson wrote:
On Thursday 19 April 2007 17:30:34 Will Stephenson wrote:
In a{sa{sv}}, what does the middle 'a' mean? Does the first string key
eg 'ip4-settings' point to an array of dicts containing those settings, and
not a single dict?
Or is that first 's' the identifier of the Connection? In that case what's
the outer array for?
I figured out how to parse the signature eventually - a{...} == Hash
therefore a{sa{sv}} is Hash of string to Hash of string to variant. :P
Well, really:
an array of dicts of dicts (the a{sa{sv}} bit is the dict of dicts)
The array is a list of Connection objects
Each Connection object is a dict of Settings objects
Each Settings object is a dict of key/value pairs for each well-defined
setting, like ssid=foobar.
Dan
Will
___
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: Disconnections
If you connect and associate manually (e.g., just using wpa_supplicant), do you get the same symptoms? -- - Patrick Bogen I have not experienced the disconnect in the past when I only used wpa_supplicant. Although I have not tried it by itself on the new OS. Shoot, now I have to dig around to figure out how to configure wpa_sup to test this out :) I'll report in a bit Jay ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NetworkManager and applet 0.6.5 Released
Hey all, It's been a while since we've had NM releases and after talking with Dan, I just made a release of 0.6.5 based on the 0.6 branch. Downloads are available at: http://ftp.gnome.org/pub/gnome/sources/NetworkManager/0.6/ http://ftp.gnome.org/pub/gnome/sources/network-manager-applet/0.6/ Thanks to all who contributed to this release! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
