date:20080606

Re: Network Manager for embedded Linux

2008-06-06 Thread Nitin Mahajan

Hello Dan,

--- On Thu, 5/6/08, Dan Williams [EMAIL PROTECTED] wrote:

 From: Dan Williams [EMAIL PROTECTED]
 Subject: Re: Network Manager for embedded Linux
 To: [EMAIL PROTECTED]
 Cc: networkmanager-list@gnome.org
 Date: Thursday, 5 June, 2008, 11:10 PM
 On Thu, 2008-06-05 at 00:13 -0700, Nitin Mahajan wrote:
  HI!

  I am planning to build and test the Network Manager
 0.6.5 for embedded Linux for a MIPS based CPU.

 Any particular reason you wouldn't use 0.7? 

There is no specific reason to use 0.6.5, its just that I found it to be the 
latest release. If you suggest that 0.7 would be more suitable for embedded 
system, then I will try 0.7 instead.

 0.7 is a
 lot more flexible
 and probably more suited for embedded systems where you
 likely want more
 control over the network configuration.

 Also, are you planning on just using the NM daemon, or do
 you want to
 use the GNOME applet too?

I just want to use the NM daemon, assuming that it would be enough of automatic 
network configuration. I would be using it on a single user embedded Linux 
device, no use case of multiuser. In this case, still do I need the gnome 
applet? More over I would not have Gnome environment on the device nor I would 
have GTK.

But I would like to have the authentication mechanism for the wireless, atleast 
WEP and WPA to begin with.
With this use case scenario, can you please tell me if I can use the Network 
Manager and by excluding and including which components in configuration? Do I 
also need some kind of Keyring Manager? Which one would be suitable if I don't 
have Gnome?

  Can anyone give me some inputs about configuration and
 dependencies when trying to do so? What do I specify for
 --with-distro in configuration?

 You could create your own distro target.  It mainly affects
 what backend
 is used for some IP configuration (see src/backends/*) and
 not much
 else.  On 0.7 the distro-specific backends are pretty much
 empty because
 we've been able to generalize most of it, so you
 wouldn't have to do
 much work on 0.7.

 If you're just using NetworkManager, then you'll
 need bits like libnl,
 glib2, and dbus-glib.  The configure script will tell you
 if you're
 missing anything.  I could go into more details about the
 dependencies,
 but that would depend on whether you'd like to use
 0.6.6 or 0.7-pre.

In a reply to my previous post someone pointed out that I would also need a 
cryptographic library. Can I avoid the functionality that needs the 
cryptographic libraries, to begin with. I do have OpenSSL on my device but dont 
have GNU TLS or Mozillaa NSS. Did you guys find GNU TLS and Mozialla NSS to be 
better than OpenSSL?

Thanks for all your valuable inputs,

regards

-Nitin

Send instant messages to your online friends http://uk.messenger.yahoo.com 
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: nm-tool showing default route

2008-06-06 Thread Dan Williams

On Tue, 2008-06-03 at 08:46 +0200, Markus Becker wrote:
 Hi Dan,
 
 below is a patch that shows the default route in nm-tool. Feel free to 
 modify it.

r3723, thanks!

Dan

 Markus
 
 Index: test/nm-tool.c
 ===
 --- test/nm-tool.c(revision 3715)
 +++ test/nm-tool.c(working copy)
 @@ -198,11 +198,14 @@
   detail_device (gpointer data, gpointer user_data)
   {
   NMDevice *device = NM_DEVICE (data);
 + NMClient *client = NM_CLIENT (user_data);
   char *tmp;
   NMDeviceState state;
   guint32 caps;
   guint32 speed;
   const GArray *array;
 + const GPtrArray *connections;
 + int j;
 
   state = nm_device_get_state (device);
 
 @@ -223,6 +226,21 @@
 
   print_string (State, get_dev_state_string (state));
 
 + connections = nm_client_get_active_connections (client);
 + for (j = 0; connections  (j  connections-len); j++) {
 + NMActiveConnection *candidate = g_ptr_array_index (connections, 
 j);
 + const GPtrArray *devices = nm_active_connection_get_devices 
 (candidate);
 + NMDevice *candidate_dev;
 +
 + if (!devices || !devices-len)
 + continue;
 + candidate_dev = g_ptr_array_index (devices, 0);
 +
 + if ( candidate_dev == device 
 +  nm_active_connection_get_default(candidate))
 + print_string (Route, IPv4 Default Route);
 + }
 +
   tmp = NULL;
   if (NM_IS_DEVICE_802_3_ETHERNET (device))
   tmp = g_strdup (nm_device_802_3_ethernet_get_hw_address 
 (NM_DEVICE_802_3_ETHERNET (device)));
 @@ -362,7 +380,7 @@
   }
 
   devices = nm_client_get_devices (client);
 - g_ptr_array_foreach ((GPtrArray *) devices, detail_device, NULL);
 + g_ptr_array_foreach ((GPtrArray *) devices, detail_device, client);
 
   g_object_unref (client);

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: corrected typo in nm-applet

2008-06-06 Thread Dan Williams

On Tue, 2008-06-03 at 11:39 -0400, Miner, Jonathan W (US SSA) wrote:
 I noticed that the IP Address label was misspelled in the Connection 
 Information dialog.  Here are `diff -u` output for patches to the three 
 files that need to be corrected.  If there is a better way to submit patches, 
 please let me know.

applet r745, thanks!

Dan

 --- ./src/applet-dialogs.c.orig   2008-06-02 08:28:05.0 -0400
 +++ ./src/applet-dialogs.c2008-06-03 11:26:29.0 -0400
 @@ -337,7 +337,7 @@
  
   /* Address */
   gtk_table_attach_defaults (table,
 -create_info_label 
 (_(IP Adrress:)),
 +create_info_label 
 (_(IP Address:)),
  0, 1, row, row + 1);
   gtk_table_attach_defaults (table,
  create_info_label 
 (ip4_address_as_string (def_addr-address)),
 
 --- ./po/ru.po.orig   2008-06-02 08:28:05.0 -0400
 +++ ./po/ru.po2008-06-03 11:26:20.0 -0400
 @@ -308,7 +308,7 @@
  msgstr ??:
  
  #: ../src/applet-dialogs.c:340
 -msgid IP Adrress:
 +msgid IP Address:
  msgstr IP-?:
  
  #: ../src/applet-dialogs.c:353
 
 --- ./po/es.po.orig   2008-06-02 08:28:05.0 -0400
 +++ ./po/es.po2008-06-03 11:26:08.0 -0400
 @@ -312,7 +312,7 @@
  msgstr Seguridad:
  
  #: ../src/applet-dialogs.c:340
 -msgid IP Adrress:
 +msgid IP Address:
  msgstr Dirección IP:
  
  #: ../src/applet-dialogs.c:353
 
 ___
 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: patch to applet-dialogs

2008-06-06 Thread Dan Williams

On Tue, 2008-06-03 at 11:52 -0400, Miner, Jonathan W (US SSA) wrote:
 If the default gateway is not explicitly set, then it currently is displayed 
 as 0.0.0.0 in the Connection Information box. This patch disables the 
 display of the Default Route tag if it isn't set.

applet r746, thanks!

Dan

 --- src/applet-dialogs.c.orig 2008-06-02 08:28:05.0 -0400
 +++ src/applet-dialogs.c  2008-06-03 11:47:59.0 -0400
 @@ -367,13 +367,15 @@
   row++;
  
   /* Gateway */
 - gtk_table_attach_defaults (table,
 + if ( def_addr-gateway != 0 ) {
 + gtk_table_attach_defaults (table,
  create_info_label 
 (_(Default Route:)),
  0, 1, row, row + 1);
 - gtk_table_attach_defaults (table,
 + gtk_table_attach_defaults (table,
  create_info_label 
 (ip4_address_as_string (def_addr-gateway)),
  1, 2, row, row + 1);
 - row++;
 + row++;
 + }
  
   /* DNS */
   dns = nm_ip4_config_get_nameservers (ip4_config);
 
 ___
 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: Service Provider Database

2008-06-06 Thread Antti Kaijanmäki

ma, 2008-06-02 kello 14:39 +0300, Antti Kaijanmäki kirjoitti:
 Hello,
 
 one part of my project is to create and specify a database for service
 provider specific settings. I've created an example page in
 live.gnome.org[1]. Please, comment if you find something missing or you
 disagree. I will begin with the implementation next week. 

I updated the page. There's now a DTD + some other changes.

 -- Antti



signature.asc
Description: Digitaalisesti allekirjoitettu viestin osa
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Network Manager for embedded Linux

2008-06-06 Thread Dan Williams

On Thu, 2008-06-05 at 20:21 -0700, Nitin Mahajan wrote:
 Hello Dan,

 --- On Thu, 5/6/08, Dan Williams [EMAIL PROTECTED] wrote:

  From: Dan Williams [EMAIL PROTECTED]
  Subject: Re: Network Manager for embedded Linux
  To: [EMAIL PROTECTED]
  Cc: networkmanager-list@gnome.org
  Date: Thursday, 5 June, 2008, 11:10 PM
  On Thu, 2008-06-05 at 00:13 -0700, Nitin Mahajan wrote:
   HI!

   I am planning to build and test the Network Manager
  0.6.5 for embedded Linux for a MIPS based CPU.

  Any particular reason you wouldn't use 0.7? 

 There is no specific reason to use 0.6.5, its just that I found it to be the 
 latest release. If you suggest that 0.7 would be more suitable for embedded 
 system, then I will try 0.7 instead.

I think 0.7 would be the better choice going forward since you'd have a
lot more control over the network configuration (if you need it).

  0.7 is a
  lot more flexible
  and probably more suited for embedded systems where you
  likely want more
  control over the network configuration.

  Also, are you planning on just using the NM daemon, or do
  you want to
  use the GNOME applet too?

 I just want to use the NM daemon, assuming that it would be enough of 
 automatic network configuration. I would be using it on a single user 
 embedded Linux device, no use case of multiuser. In this case, still do I 
 need the gnome applet? More over I would not have Gnome environment on the 
 device nor I would have GTK.

Nope, you can just use the NM daemon.  You shouldn't need GTK or GNOME.
NM has the ability to grab connections from the system settings service
(nm-system-settings) as well as user connections (normally nm-applet on
GNOME or knetworkmanager on KDE).  Since you're not using GNOME or KDE,
you can just use system connections instead.

 But I would like to have the authentication mechanism for the wireless, 
 atleast WEP and WPA to begin with.
 With this use case scenario, can you please tell me if I can use the Network 
 Manager and by excluding and including which components in configuration? Do 
 I also need some kind of Keyring Manager? Which one would be suitable if I 
 don't have Gnome?

You can just use system connections with the keyfile plugin for the
system settings service.  You shouldn't need a keyring at all.  Were you
planning on allowing the user to configure the connections, or just to
select between preconfigured connections, or just have everything be as
automatic as possible?

NM will spawn nm-system-settings via dbus service activation, and
nm-system-settings will look for connections, read them in, and send
them to NetworkManager.  NM can then bring those connections up or take
them down based on network conditions.

You'll create a /etc/nm-system-settings.conf file that contains:

[main]
plugins=keyfile

this causes nm-system-settings to load the keyfile plugin, which looks
for connections in /etc/NetworkManager/system-connections.  Each file in
that directory is a .ini-style file describing the connection.  When you
get to that point, we can post some examples of keyfile connections for
you.  The connection files would contain the WPA or WEP key for
connection to your network.

   Can anyone give me some inputs about configuration and
  dependencies when trying to do so? What do I specify for
  --with-distro in configuration?

  You could create your own distro target.  It mainly affects
  what backend
  is used for some IP configuration (see src/backends/*) and
  not much
  else.  On 0.7 the distro-specific backends are pretty much
  empty because
  we've been able to generalize most of it, so you
  wouldn't have to do
  much work on 0.7.

  If you're just using NetworkManager, then you'll
  need bits like libnl,
  glib2, and dbus-glib.  The configure script will tell you
  if you're
  missing anything.  I could go into more details about the
  dependencies,
  but that would depend on whether you'd like to use
  0.6.6 or 0.7-pre.

 In a reply to my previous post someone pointed out that I would also need a 
 cryptographic library. Can I avoid the functionality that needs the 
 cryptographic libraries, to begin with. I do have OpenSSL on my device but 
 dont have GNU TLS or Mozillaa NSS. Did you guys find GNU TLS and Mozialla NSS 
 to be better than OpenSSL?

The crypto libraries are used for reading certificates and private keys
for connections to 802.1x/802.11i networks.  If you don't need that
functionality you could safely comment out that code in NM.  It does
look like OpenSSL has the functionality required, but there's no code
for that yet.  I can write that if you'd like (or you could too :).

The one caveat with OpenSSL is that it's not GPL-compatible; which means
that you can't link OpenSSL with NetworkManager and distribute the
result outside your company.  If you're just using NM linked with
OpenSSL _inside_ your company, that's fine.  You just couldn't
distribute/sell/whatever the combination due to the license

SELinux is preventing NetworkManager (NetworkManager_t) getattr access to device /dev/noz0.

2008-06-06 Thread Steve Baker

The error comes up when I try to connect using Option GTMAX broadband card.


Jun  6 17:35:45 localhost NetworkManager: info  (noz0): device state
change: 3 - 4
Jun  6 17:35:45 localhost NetworkManager: info  Activation (noz0) Stage 1
of 5 (Device Prepare) scheduled...
Jun  6 17:35:45 localhost NetworkManager: info  Activation (noz0) Stage 1
of 5 (Device Prepare) started...
Jun  6 17:35:45 localhost NetworkManager: WARN  nm_serial_device_open():
(noz0) cannot open device (errno 13)
Jun  6 17:35:45 localhost NetworkManager: info  (noz0): device state
change: 4 - 9
Jun  6 17:35:45 localhost NetworkManager: info  Marking connection 'Att
Mobile Broadband' invalid.
Jun  6 17:35:45 localhost NetworkManager: info  Activation (noz0) failed.
Jun  6 17:35:45 localhost NetworkManager: info  Activation (noz0) Stage 1
of 5 (Device Prepare) complete.
Jun  6 17:35:45 localhost NetworkManager: info  (noz0): device state
change: 9 - 3
Jun  6 17:35:45 localhost NetworkManager: info  (noz0): deactivating
device.
Jun  6 17:35:46 localhost setroubleshoot: SELinux is preventing
NetworkManager (NetworkManager_t) read write access to device noz0. For
complete SELinux messages. run sealert -l
8d48857c-35c1-46ed-9cb1-92eaeacf5d53

NetworkManager-0.7.0-0.9.3.svn3623.fc9
selinux-policy-3.3.1-55.fc9

Thanks!
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: NetworkManager and CNU-550 - modification of 10-modem.fdi to get it working

2008-06-06 Thread Dan Williams

On Tue, 2008-06-03 at 10:37 +0300, Igor wrote:
 Added CMOTECH definition between Anydata and Pantech to 
 /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi

will commit upstream to hal-info, thanks.

dan

   !-- Anydata --
   match key=@info.parent:usb.vendor_id int=0x16d5
 !-- Adu E100a,500a --
 match key=@info.parent:usb.product_id int_outof=0x6501;0x6502
   match key=@info.parent:usb.interface.number int=0
 append key=info.capabilities type=strlistmodem/append
 append key=modem.command_sets 
 type=strlistIS-707-A/append
   /match
 /match
   /match
 
   !-- CMOTECH --
   match key=@info.parent:usb.vendor_id int=0x16d8
 !-- C-motech CNU-550 (USB, EV-DO) --
 match key=@info.parent:usb.product_id int_outof=0x5543
   match key=@info.parent:usb.interface.number int=0
 append key=info.capabilities type=strlistmodem/append
 append key=modem.command_sets 
 type=strlistIS-707-A/append
   /match
 /match
   /match
 
   !-- Pantech --
   match key=@info.parent:usb.vendor_id int=0x106c
 !-- PC5740;PC5750 EVDO rev A card --
 match key=@info.parent:usb.product_id int_outof=0x3701;0x3702
   match key=@info.parent:usb.interface.number int=0
 append key=info.capabilities type=strlistmodem/append
 append key=modem.command_sets 
 type=strlistIS-707-A/append
   /match
 /match
   /match
 ___
 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

Network manager GSM phone via USB HAL Fedora 9

2008-06-06 Thread Steve Baker

Using NM looking to connect my GSM razor v3 via usb for internet access.
Trawling around I found GSM cards defined in
/usr/share/hal/fdi/information/10freedesktop/10-modem.fdi
Should I add it myself here or is there a more elegant / preferred way to do
this?
Thanks
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Network Manager for embedded Linux

Re: nm-tool showing default route

Re: corrected typo in nm-applet

Re: patch to applet-dialogs

Re: Service Provider Database

Re: Network Manager for embedded Linux

SELinux is preventing NetworkManager (NetworkManager_t) getattr access to device /dev/noz0.

Re: NetworkManager and CNU-550 - modification of 10-modem.fdi to get it working

Network manager GSM phone via USB HAL Fedora 9

9 matches

Site Navigation

Mail list logo

Footer information