Re: configure NetworkManger-0.7.0 fail, why?
Ok, the problem had been resolved I re-compiled dbus-glib by ./configure -prefix=/usr Don't hesitate to let me know if you have any questions or concerns. Thanks Best Regards scott.lv [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with Ubuntu 8.10 and multiple users (connection closed on log out)
Hi, I kind of partially solved the problem. I've changed the connection setting so that it is a system-wide connection and all users can use it, no matter if the first one logs out. Thanks Dan and Alexander. However, I'm still getting only one Network Manager Applet in the Tray Area. The first user to log has it, but the following users do not. Isn't it possible to have multiple instances of NM applet running? Thanks again, Dídac Alexander Sack wrote: > On Tue, Dec 09, 2008 at 02:01:42PM -0500, Dan Williams wrote: > >> On Mon, 2008-12-08 at 11:42 +0100, Dídac Busquets wrote: >> >>> Hi all, >>> >>> I recently upgraded to Ubuntu 8.10 and since then I have a little >>> problem with nm-applet. >>> >>> When the first user to log in my machine starts his session, >>> nm-applet >>> is started and it automatically connects to my wireless network. Up >>> to >>> here everything is fine. >>> >>> However, if a second user logs in (the first one not loggin out), >>> there >>> is no nm-applet it his session. This is not a huge problem, since the >>> connection still works for both users. >>> >>> The problem comes when the first user logs out, then, his nm-applet >>> shutdowns, and so does the connection, thus leaving the second user >>> non-connected, and without any nm-applet in his session. >>> >> Correct; there are two types of network connections; 'user' and >> 'system'. System connections are available to all users of the machine >> to activate and deactivate, while user connections are available only to >> the user that created them. >> >> It sounds like your primary connection isn't a system connection, and >> thus when your user logs out, your preferences (which contain the >> connection information) go away, and of course the connection is brought >> down. >> >> Try setting up the connection in /etc/network/interfaces, and if that >> doesn't work for some reason, use the keyfile plugin (add ",keyfile" >> to /etc/NetworkManager/nm-system-settings.conf at the end of the >> "plugins=" line, and restart), and create a new system connection in the >> connection editor. >> > > keyfile plugin is enabled by default in ubuntu. So just go to > connection editor, create a new connection and set the system settings > flag there. > > - Alexander > > > > _ Comparte hasta 500 fotos en un solo email con Windows Live http://download.live.com/___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Bluetooth support
Hi Dan, > > > > I'd love to be able to have GPRS over Bluetooth work, even if it > > > > required properly configuring /etc/bluetooth/rfcomm.conf at first > > > > (it's the manual PPP stuff I hate). > > > > > > We've got a plan, and BT is a top work item for NM 0.8, which I'll try > > > to detail soon on this list. It won't involve any mucking with > > > rfcomm.conf since all that can be done automatically with the Bluez > > > D-Bus interface. It may require a fairly recent version of Bluez though > > > (like 3.29 or later). > > > > go more for something like 4.22 :) > > Probably, but Fedora 9, which is the last release I care about, has > 3.36. 3.29 is the latest version I can find that add support for the > "new" interface. except that we changed it in 4.x to make it even simpler. You just have to find the right object path, call Connect() on it and then either get a TTY or network device name as result. Regards Marcel ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Bluetooth support
On Thu, 2008-12-11 at 06:04 +1100, Mikel Ward wrote: > On Thu, Dec 11, 2008 at 4:50 AM, Dan Williams <[EMAIL PROTECTED]> wrote: > > On Wed, 2008-12-10 at 10:45 +1100, Mikel Ward wrote: > >> Hi > >> > >> I'd love to be able to have GPRS over Bluetooth work, even if it > >> required properly configuring /etc/bluetooth/rfcomm.conf at first > >> (it's the manual PPP stuff I hate). > > > > We've got a plan, and BT is a top work item for NM 0.8, which I'll try > > to detail soon on this list. It won't involve any mucking with > > rfcomm.conf since all that can be done automatically with the Bluez > > D-Bus interface. It may require a fairly recent version of Bluez though > > (like 3.29 or later). > > Good to hear! > > >> Is there any way I can help? > > > > We'll need testing at some point, of course. At the moment though, > > we're in the planning stages. What distro are you running and what > > version of the bluez-utils packages do you have? > > Currently running Ubuntu 8.10 x86 with bluez 4.12-0ubuntu5. Speaking of new features, how about L2TP? > > Thanks > > Mike > ___ > 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: Bluetooth support
On Wed, 2008-12-10 at 19:29 +0100, Marcel Holtmann wrote: > Hi Dan, > > > > I'd love to be able to have GPRS over Bluetooth work, even if it > > > required properly configuring /etc/bluetooth/rfcomm.conf at first > > > (it's the manual PPP stuff I hate). > > > > We've got a plan, and BT is a top work item for NM 0.8, which I'll try > > to detail soon on this list. It won't involve any mucking with > > rfcomm.conf since all that can be done automatically with the Bluez > > D-Bus interface. It may require a fairly recent version of Bluez though > > (like 3.29 or later). > > go more for something like 4.22 :) Probably, but Fedora 9, which is the last release I care about, has 3.36. 3.29 is the latest version I can find that add support for the "new" interface. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Bluetooth support
On Thu, Dec 11, 2008 at 4:50 AM, Dan Williams <[EMAIL PROTECTED]> wrote: > On Wed, 2008-12-10 at 10:45 +1100, Mikel Ward wrote: >> Hi >> >> I'd love to be able to have GPRS over Bluetooth work, even if it >> required properly configuring /etc/bluetooth/rfcomm.conf at first >> (it's the manual PPP stuff I hate). > > We've got a plan, and BT is a top work item for NM 0.8, which I'll try > to detail soon on this list. It won't involve any mucking with > rfcomm.conf since all that can be done automatically with the Bluez > D-Bus interface. It may require a fairly recent version of Bluez though > (like 3.29 or later). Good to hear! >> Is there any way I can help? > > We'll need testing at some point, of course. At the moment though, > we're in the planning stages. What distro are you running and what > version of the bluez-utils packages do you have? Currently running Ubuntu 8.10 x86 with bluez 4.12-0ubuntu5. Thanks Mike ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Bluetooth support
Hi Dan, > > I'd love to be able to have GPRS over Bluetooth work, even if it > > required properly configuring /etc/bluetooth/rfcomm.conf at first > > (it's the manual PPP stuff I hate). > > We've got a plan, and BT is a top work item for NM 0.8, which I'll try > to detail soon on this list. It won't involve any mucking with > rfcomm.conf since all that can be done automatically with the Bluez > D-Bus interface. It may require a fairly recent version of Bluez though > (like 3.29 or later). go more for something like 4.22 :) Regards Marcel ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Using libnm-glib issues after dbus and dbus-glib update
On Thu, 2008-12-11 at 00:30 +1100, James . wrote:
> I have a small program which I use to detect device state changes,
> that uses libnm-glib. A couple of days ago i updated dbus to 1.2.6 and
> dbus-glib to 0.78 (this is a slackware base), and now the
> "device-changed" signal among others no longer works, however, other
> applications that use NM seems to work fine such as nm-applet. Here is
> the code I am using, with irrelevant sections cut out:
>
> #include
> #include
> #include
> #include
> #include
> #include
>
> static void device_state_changed_cb(NMDevice *device, NMDeviceState
> new_state, NMDeviceState old_state, NMDeviceStateReason reason,
> gpointer user_data){
> printf("device state changed\n");
> //handle_device(device, new_state);
> }
>
> static void device_update_cb(NMClient *client, NMDevice *device,
> gpointer user_data){
> g_signal_connect(G_OBJECT(device), "state-changed",
> G_CALLBACK(device_state_changed_cb), NULL);
> }
>
> static void init_devices(NMDevice* device, gpointer user_data){
> g_signal_connect(G_OBJECT(device), "state-changed",
> G_CALLBACK(device_state_changed_cb), NULL);
> printf("device added %s\n", nm_device_get_iface(device));
> //handle_device(device, nm_device_get_state(device));
> }
>
> int main(){
> NMClient* nm_client;
> const GPtrArray* devices = NULL;
>
> gtk_init (NULL, NULL);
>
> nm_client = nm_client_new();
>
> g_signal_connect(G_OBJECT(nm_client), "device-added",
> G_CALLBACK(device_update_cb), NULL);
>
> devices = nm_client_get_devices(nm_client);
> if(devices) g_ptr_array_foreach((GPtrArray*)devices,
> (GFunc)init_devices, NULL);
>
> gtk_main();
> return 0;
> }
>
> Before, I could unplug my ethernet and replug it, and it would spam
> "device state changed" all over the screen. Now, nothing happens on
> the "state-changed" signal despite getting a valid connection handler.
>
> Would anyone like to shed light on this strange issue?
The changes to dbus involved the default security policy, including what
messages could be sent to what processes. The fallout from that is
still ongoing. Does slackware use pam_console and the at_console D-Bus
context, or are D-Bus permissions on Slackware normally user-based?
It's probably an issue between
the /etc/dbus-1/system.d/NetworkManager.conf dbus permissions file (can
you attach yours to a reply?) and the new dbus update.
Dan
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Bluetooth support
On Wed, 2008-12-10 at 10:45 +1100, Mikel Ward wrote: > Hi > > I'd love to be able to have GPRS over Bluetooth work, even if it > required properly configuring /etc/bluetooth/rfcomm.conf at first > (it's the manual PPP stuff I hate). We've got a plan, and BT is a top work item for NM 0.8, which I'll try to detail soon on this list. It won't involve any mucking with rfcomm.conf since all that can be done automatically with the Bluez D-Bus interface. It may require a fairly recent version of Bluez though (like 3.29 or later). > Is there any way I can help? We'll need testing at some point, of course. At the moment though, we're in the planning stages. What distro are you running and what version of the bluez-utils packages do you have? Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Using libnm-glib issues after dbus and dbus-glib update
I have a small program which I use to detect device state changes,
that uses libnm-glib. A couple of days ago i updated dbus to 1.2.6 and
dbus-glib to 0.78 (this is a slackware base), and now the
"device-changed" signal among others no longer works, however, other
applications that use NM seems to work fine such as nm-applet. Here is
the code I am using, with irrelevant sections cut out:
#include
#include
#include
#include
#include
#include
static void device_state_changed_cb(NMDevice *device, NMDeviceState
new_state, NMDeviceState old_state, NMDeviceStateReason reason,
gpointer user_data){
printf("device state changed\n");
//handle_device(device, new_state);
}
static void device_update_cb(NMClient *client, NMDevice *device,
gpointer user_data){
g_signal_connect(G_OBJECT(device), "state-changed",
G_CALLBACK(device_state_changed_cb), NULL);
}
static void init_devices(NMDevice* device, gpointer user_data){
g_signal_connect(G_OBJECT(device), "state-changed",
G_CALLBACK(device_state_changed_cb), NULL);
printf("device added %s\n", nm_device_get_iface(device));
//handle_device(device, nm_device_get_state(device));
}
int main(){
NMClient* nm_client;
const GPtrArray* devices = NULL;
gtk_init (NULL, NULL);
nm_client = nm_client_new();
g_signal_connect(G_OBJECT(nm_client), "device-added",
G_CALLBACK(device_update_cb), NULL);
devices = nm_client_get_devices(nm_client);
if(devices) g_ptr_array_foreach((GPtrArray*)devices,
(GFunc)init_devices, NULL);
gtk_main();
return 0;
}
Before, I could unplug my ethernet and replug it, and it would spam
"device state changed" all over the screen. Now, nothing happens on
the "state-changed" signal despite getting a valid connection handler.
Would anyone like to shed light on this strange issue?
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Still VPN routing problems
--On Tuesday, December 09, 2008 13:58:56 -0500 Dan Williams <[EMAIL PROTECTED]> wrote: ¦ ¦ I can't see where the pptp plugin even cares about internal vs. external ¦ gateways. Can you grab some log output from NM when it brings up the ¦ VPN? ¦ Here's the NM log: NetworkManager: VPN connection 'Home' (IP Config Get) reply received. NetworkManager: VPN Gateway: 192.168.7.128 NetworkManager: Tunnel Device: ppp1 NetworkManager: Internal IP4 Address: 192.168.7.9 NetworkManager: Internal IP4 Prefix: 32 NetworkManager: Internal IP4 Point-to-Point Address: 0.0.0.0 NetworkManager: Maximum Segment Size (MSS): 0 NetworkManager: Internal IP4 DNS: 192.168.7.128 NetworkManager: Internal IP4 DNS: 192.168.7.128 NetworkManager: DNS Domain: '(none)' ¦ ¦ Does your route dump mean that the local PTP address for 'ppp1' is ¦ 192.168.7.128 and the remote PTP address is 10.37.79.0? Not quite - see ifconfig output: ppp0 Link encap:Point-to-Point Protocol inet addr:10.37.79.53 P-t-P:10.37.79.0 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:3 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:66 (66.0 B) TX bytes:87 (87.0 B) ppp1 Link encap:Point-to-Point Protocol inet addr:192.168.7.9 P-t-P:192.168.7.9 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1496 Metric:1 RX packets:11 errors:0 dropped:0 overruns:0 frame:0 TX packets:20 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:1473 (1.4 KB) TX bytes:1734 (1.7 KB) The PPTP server is also a NAT gateway for its local network, and its private address is 192.168.7.128. This address only exists within the VPN, so can only be accessed over ppp1. I'm not quite sure why ifconfig doesn't show this as the P-t-P address for ppp1, maybe I'm not getting what ifconfig is telling me. HTH, Rick ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Still VPN routing problems
--On Tuesday, December 09, 2008 13:58:56 -0500 Dan Williams <[EMAIL PROTECTED]> wrote: ¦ ¦ I can't see where the pptp plugin even cares about internal vs. external ¦ gateways. Can you grab some log output from NM when it brings up the ¦ VPN? ¦ Here's the NM log: NetworkManager: VPN connection 'Home' (IP Config Get) reply received. NetworkManager: VPN Gateway: 192.168.7.128 NetworkManager: Tunnel Device: ppp1 NetworkManager: Internal IP4 Address: 192.168.7.9 NetworkManager: Internal IP4 Prefix: 32 NetworkManager: Internal IP4 Point-to-Point Address: 0.0.0.0 NetworkManager: Maximum Segment Size (MSS): 0 NetworkManager: Internal IP4 DNS: 192.168.7.128 NetworkManager: Internal IP4 DNS: 192.168.7.128 NetworkManager: DNS Domain: '(none)' ¦ ¦ Does your route dump mean that the local PTP address for 'ppp1' is ¦ 192.168.7.128 and the remote PTP address is 10.37.79.0? Not quite - see ifconfig output: ppp0 Link encap:Point-to-Point Protocol inet addr:10.37.79.53 P-t-P:10.37.79.0 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:3 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:66 (66.0 B) TX bytes:87 (87.0 B) ppp1 Link encap:Point-to-Point Protocol inet addr:192.168.7.9 P-t-P:192.168.7.9 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1496 Metric:1 RX packets:11 errors:0 dropped:0 overruns:0 frame:0 TX packets:20 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:1473 (1.4 KB) TX bytes:1734 (1.7 KB) The PPTP server is also a NAT gateway for its local network, and its private address is 192.168.7.128. This address only exists within the VPN, so can only be accessed over ppp1. I'm not quite sure why ifconfig doesn't show this as the P-t-P address for ppp1, maybe I'm not getting what ifconfig is telling me. HTH, Rick ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: configure NetworkManger-0.7.0 fail, why?
On Wed, 2008-12-10 at 16:28 +0800, scott.lv wrote: >But I get error when I run pkg-config –modversion dbus-glib-1 > > Package dbus-glib-1 was not found in the pkg-config search path. > > Perhaps you should add the directory containing `dbus-glib-1.pc' > > to the PKG_CONFIG_PATH environment variable > > No package 'dbus-glib-1' found Have you tried doing what the error message says? Your message shows libdbus-glib.so is in /usr/local/lib, so the .pc file is probably in /usr/local/lib/pkgconfig or /usr/local/share/pkgconfig... Simon. signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WPA Enterprise (EAP-TLS) system connection
On Tue, 2008-12-09 at 15:11 -0500, Dan Williams wrote: > On Tue, 2008-12-09 at 13:34 -0500, Dan Williams wrote: > > On Sat, 2008-12-06 at 21:33 +1300, Simon Geard wrote: > > > I know it's a minor thing, but by breaking convention, it makes > writing > > > an automated build just that little bit more complicated, where the > > > directory can't be predicted from the package name... > > > > Sure. > > Updated in trunk and stable (0.7). Thanks for that. Simon. signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE:configure NetworkManger-0.7.0 fail, why?
I export DBUS_CFLAGS=yes and export DBUS_LIBS , then configure can pass, but why? I had installed dbus-glib and dbus Best Regards scott.lv [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
configure NetworkManger-0.7.0 fail, why?
Hi all I run configure shell to networkmanager-0.7.0 ,but fail , following is error message checking for DBUS... configure: error: Package requirements (dbus-glib-1 >= 0.72) were not met: I installed dbus-glib-1. [EMAIL PROTECTED] NetworkManager-0.7.0]# ll /usr/local/lib/libdbus-glib-1.* -rw-r--r-- 1 root root 414996 Dec 9 17:49 /usr/local/lib/libdbus-glib-1.a -rwxr-xr-x 1 root root937 Dec 9 17:49 /usr/local/lib/libdbus-glib-1.la lrwxrwxrwx 1 root root 23 Dec 9 17:49 /usr/local/lib/libdbus-glib-1.so -> libdbus-glib-1.so.2.1.0 lrwxrwxrwx 1 root root 23 Dec 9 17:49 /usr/local/lib/libdbus-glib-1.so.2 -> libdbus-glib-1.so.2.1.0 -rwxr-xr-x 1 root root 323900 Dec 9 17:49 /usr/local/lib/libdbus-glib-1.so.2.1.0 But I get error when I run pkg-config -modversion dbus-glib-1 Package dbus-glib-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `dbus-glib-1.pc' to the PKG_CONFIG_PATH environment variable No package 'dbus-glib-1' found Don't hesitate to let me know if you have any questions or concerns. Thanks Best Regards scott.lv [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
