Re: Newbie question
Alternatively are there any examples/tutorials for version 0.8? Dave. On 07/07/2011 12:21 PM, Alex Pyattaev wrote: The problem is that the examples in GIT are for networkmanager version 0.9, and you probably have version 0.8. Check if 0.9 is available for your distro, or try to locate old examples. If the 0.9 is not available for your distro, you could try to build it yourself, its not very hard to do, but you'll need to build wpa-supplicant's dev version as well, otherwise you will get some nasty bugs with WPA. If you just want to test the wired interfaces you don't need to bother though. Alex ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Newbie question
They used to be there, indeed. Try to look through older versions in the repository. I have no idea if it will give any results though. And anyway, 0.8 will probably be dropped quite soon, and new api is alot better. On Friday 08 July 2011 13:12:36 David Lambert wrote: Alternatively are there any examples/tutorials for version 0.8? Dave. On 07/07/2011 12:21 PM, Alex Pyattaev wrote: The problem is that the examples in GIT are for networkmanager version 0.9, and you probably have version 0.8. Check if 0.9 is available for your distro, or try to locate old examples. If the 0.9 is not available for your distro, you could try to build it yourself, its not very hard to do, but you'll need to build wpa-supplicant's dev version as well, otherwise you will get some nasty bugs with WPA. If you just want to test the wired interfaces you don't need to bother though. Alex ___ 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: Newbie question
The problem is that the examples in GIT are for networkmanager version 0.9, and you probably have version 0.8. Check if 0.9 is available for your distro, or try to locate old examples. If the 0.9 is not available for your distro, you could try to build it yourself, its not very hard to do, but you'll need to build wpa-supplicant's dev version as well, otherwise you will get some nasty bugs with WPA. If you just want to test the wired interfaces you don't need to bother though. Alex On Thursday 07 July 2011 09:53:04 David Lambert wrote: I am a newbie to NetworkManager/dbus and in order to learn the interface am attempting to run the python script: http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/examples/pyth on/nm-state.py I get the error: dlambert@development:~/Desktop$ python nm-state.py Device eth0 is activated Traceback (most recent call last): File nm-state.py, line 58, in module con_details = con_iface.GetSettings() File /usr/lib/pymodules/python2.6/dbus/proxies.py, line 68, in __call__ return self._proxy_method(*args, **keywords) File /usr/lib/pymodules/python2.6/dbus/proxies.py, line 140, in __call__ **keywords) File /usr/lib/pymodules/python2.6/dbus/connection.py, line 620, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method GetSettings with signature on interface org.freedesktop.NetworkManager.Settings.Connection doesn't exist Any pointers as to where I can get details of the Python API or a tutorial would be appreciated. Regards, Dave. ___ 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: newbie question on svn release version
On Thu, 2009-05-14 at 12:46 +0530, saurav barik wrote: Hi All, I am using NetworkManager version - svnr2984-r8. Could anybody please tell me which official version can it be mapped to? I mean is it 0.6.* or is it a 0.7.* release. That appears to correspond to a date of 2007-10-18. That's really, really old :) It looks like a very early cut of something off the trunk 0.7 development branch. It's definitely not an actual release of anything. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Newbie question on occasional NM problem
On Sat, 2009-04-25 at 13:41 +0100, Timothy Murphy wrote: I'm running Fedora-10/KDE on a few laptops, and have just joined the NM mailing list, having moaned about (and sometimes praised) NM on the Fedora mailing list for several years. I'm currently using a Thinkpad T43 with a PCMCIA classic Orinoco gold WiFi card. I guess NM connects fine about 85% of the time when I boot up. The other 15% of the time it doesn't connect, and I have to re-boot. It then connects about 75% of the time; in the remaining cases it connects on the third try. Looks like the orinoco card isn't returning your AP in the scan results perhaps? Can you run 'nm-tool' when you notice NM not connecting to your AP automatically, and report what it says for the wireless networks that 'eth1' can see? Do you see your AP if you run 'iwlist eth1 scan' (as root)? Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: newbie question about NAT and bridging.
Anyone should feel free to correct me if I'm wrong about any of the following. David Moffatt wrote: Is there a good FAQ? I need to find out about how to make bridging and/or NAT work with NM. Specifically I want to find out 1) Is there an easy way to figure out what the current interface is? The dbus interface allows you to query which interfaces are active. 2) Are there any scripts run when an interface is brought up or down that I could use to change my NAT routing? NetworkManagerDispatcher calls each of the scripts in /etc/NetworkManager/dispatcher.d/ directory whenever an interface goes up or down. I believe these scripts are called with the name of the changing interface as an argument. 3) Does anyone know why the interface goes to lala land when it is controlled by NM and you attach and remove a software bridge from it? What in particular happens? 4) Are there any other hidden gotcha with NAT and NM? Thanks for your time, David Moffatt. ___ 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: newbie question about NAT and bridging.
On Mon, 2008-09-08 at 16:26 -0700, David Moffatt wrote: Is there a good FAQ? I need to find out about how to make bridging and/or NAT work with NM. I'd like to add support for bridging in the near future to NM, if just to help make virutalization a more pleasant experience. That probably means support for adding devices to a specified bridge or something like that, since the bridge device itself doesn't have attributes that anyone cares about. Specifically I want to find out 1) Is there an easy way to figure out what the current interface is? The D-Bus interface exports a list of ActiveConnection objects, a property of which is Devices, which is a list of the network devices currently associated with the active connection. Each ActiveConnection also has a 'default' property, and the one that has 'default=True' is the one you'll care about. This is the preferred method, since in the future more than one device might be associated with an active connection. Alternatively, you can ask for the list of devices and check whether each device's state is NM_DEVICE_STATE_ACTIVATED, but that doesn't tell you if it's the default device or not. 2) Are there any scripts run when an interface is brought up or down that I could use to change my NAT routing? NM will run scripts in the /etc/NetworkManager/dispatcher.d directory with two arguments (interface name, and up/down). The script's environment will also contain various details about the IP4 and DHCP configuration the device is using. 3) Does anyone know why the interface goes to lala land when it is controlled by NM and you attach and remove a software bridge from it? That's interesting; I haven't heard that before but then I haven't tried this specific configuration. 4) Are there any other hidden gotcha with NAT and NM? There shouldn't be besides what would normally be encountered with a configured device and bridging. NM takes over the default route and will of course bring the device up and take it down when the user tells NM to, or when the cable is unplugged, but besides that you should be able to use dispatcher scripts to get what you want done. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Newbie question: advice in adding a new feature to network manager...
I don't know how you should get started ... but here is my vote for that as a a worthy feature. P On 8/16/07, Doug Anson [EMAIL PROTECTED] wrote: Hi: I'm new to NetworkManager and have an interest in coding up a new feature into it. I think it would be great to have the ability to partition out adhoc networks from infrastructure networks in the available wireless network list. That way, if it happens to be the case that there is a lurking adhoc network called say foo and an infrastructure network called foo, the user can differentiate between the two and choose which one they want to associate with. Additionally, with that kind of segmentation, it would be nice to ONLY see adhoc networks or infrastructure networks in the list (as a configurable option). For a managed network environment, users may only be interested in seeing one kind of network at a given time. So, any advice on how I can quickly ramp up into the design aspects of NetworkManager? Any advice on where I would likely begin to experiment with changes? Thanks! Doug ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list -- Everything is vague to a degree you do not realize till you have tried to make it precise. Bertrand Russell www.the-brights.net ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Newbie question: advice in adding a new feature to network manager...
On Thu, 2007-08-16 at 00:54 -0500, Doug Anson wrote: Hi: I’m new to NetworkManager and have an interest in coding up a new feature into it. I think it would be great to have the ability to partition out adhoc networks from infrastructure networks in the available wireless network list. That way, if it happens to be the case that there is a lurking adhoc network called say “foo” and an infrastructure network called “foo”, the user can differentiate between the two and choose which one they want to associate with. Right. There are two pieces to this. The first is that NM currently aggregrates networks together based on SSID, which we need to change. I believe for 0.7 we should have NM expose a list of _all_ BSSIDs via D-Bus, and leave the UI side to sort out what exactly it wishes to connect to, and to aggregate that list on it's own. So that's the first piece; it means ripping out all the aggregation code in NM that happens in src/nm-device-802-11-wireless.c when the scan results come in. We should weed out duplicates on BSSID _only_. The second piece is to aggregate APs in the GUI menus. If you define a tuple of: (band, mode, security) and aggregate APs based on that, I believe that's sufficient to capture the behavior we want. This allows the applet to know exactly what options to default to when showing the Need your Key dialog, or what Connection object to pass to NM when you click on the network. This is a bit harder since some matching has to occur to pick the applicable connection object. This is all based on NM 0.7 (trunk) BTW, I don't think this should be done for 0.6.x since that's the stable branch. Additionally, with that kind of segmentation, it would be nice to ONLY see adhoc networks or infrastructure networks in the list (as a configurable option). For a managed network environment, users may only be interested in seeing one kind of network at a given time. You could do that with the scheme above, yes. Obviously by default it should any BSSID, but a sysadmin could lock down what networks the user sees by default quite easily by setting GConf keys or something that the applet reads. So, any advice on how I can quickly ramp up into the design aspects of NetworkManager? Any advice on where I would likely begin to experiment with changes? I think we can dig up some design docs somewhere for 0.7, which includes in the interface design all the lessons learned over the past few years. libnm-glib/* are good source files to read (especially the header files) and we should make Tambet clean up the modular diagram he did long ago and put it up somewhere. You could probably start with src/nm-device-802-11-wireless.c in the function merge_scanned_ap(). That does the actual merge, and we probably want to just rip this function out. That gets called by supplicant_iface_scanned_ap_cb(), which is triggered whenever wpa_supplicant reports a new scanned BSSID. Instead of doing the following: /* Add the AP to the device's AP list */ merge_scanned_ap (self, ap); /* Once we have the list, copy in any relevant information from our Allowed list. */ nm_ap_list_copy_properties (nm_device_802_11_wireless_ap_list_get (self), app_data-allowed_ap_list); NM should just search through the list returned by nm_device_802_11_wireless_ap_list_get() and if the BSSID of the scanned AP is already in that list, copy the properties of the newly scanned AP over top of the one that's already in the list. If it's a completely new AP, it should just add the AP to the device's scan list. app_data-allowed_ap_list will be going away quite soon, so the nm_ap_list_copy_properties() should die as well once that happens. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
