RE: Headless version for routers...

[Hooker, Jonathan]

At my company we have had a similar question to what Ed is asking. Although it 
stays running in the background, you don't have full control over the software 
without manually editing config files and restarting NM and even then it can be 
flaky. NM does not truly have a CLI. This being the case, I would also pose the 
question, are there any plans to go down the route of providing a CLI that 
would act as a front-end interface to the already running back-end daemon?

Jonathan Hooker
Desktop Support - Linux
Garmin International
jonathan.hoo...@garmin.com

-Original Message-
From: networkmanager-list-boun...@gnome.org 
[mailto:networkmanager-list-boun...@gnome.org] On Behalf Of Marc Herbert
Sent: Monday, July 20, 2009 4:15 AM
To: networkmanager-list@gnome.org
Subject: Re: Headless version for routers...

Ed W wrote :

> Does anyone see any plans to tease the
> frontend and backend completely apart (perhaps with only a dbus
> communication channel between them)?  The idea being that you end up
> with a headless management daemon and a control application (perhaps one
> of several)?

Sorry but... isn't that already the case? I am currently using version
0.7.1. Once I have configured some system connections, the headless NM
daemon stays perfectly alive and kicking even after shutting down X.




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

--
This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient. If you are not the intended recipient, please be 
aware that any disclosure, copying, distribution or use of this e-mail or any 
attachment is prohibited. If you have received this e-mail in error, please 
contact the sender and delete all copies.
Thank you for your cooperation.
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

RE: network status change issue...

[Hooker, Jonathan]

Ok. I guess I am confused. On Fedora 10 it shows that my version is 0.7.0.99. 
Are you referring to the version of the individual file in the source when you 
say 2.6.17?

Jonathan Hooker
Desktop Support - Engineering
Garmin International
jonathan.hoo...@garmin.com
-Original Message-
From: Dan Williams [mailto:d...@redhat.com]
Sent: Thursday, May 07, 2009 10:11 AM
To: Marcel Holtmann
Cc: Hooker, Jonathan; networkmanager-list@gnome.org
Subject: Re: network status change issue...

On Thu, 2009-05-07 at 08:01 -0700, Marcel Holtmann wrote:
> Hi Dan,
>
> > > I am currently having issues with Network Manager. Whenever I unplug
> > > the ethernet cable Network Manager picks up on the fact it is
> > > disconnected. Then it tries to connect to whatever wifi connections I
> > > have setup. This works properly. The issue I am running into is
> > > whenever I plug back in the active network cable Network Manager
> > > continues to see the ethernet card as disconnected. I have to either
> > > restart Network Manager or at least uncheck Enable Networking and
> > > recheck it in the Network Manager menu. Only after I do that does
> >
> > This says that the carrier detection logic with netlink may not be
> > working properly.  Can you check /sys/class/net//carrier
> > after you plug it back in, and what that says?  If it's '1', then
> > proceed to the next step here.  If it's '0', then it's a driver problem
> > in the kernel.
> >
> > If carrier is '1', then it could be a problem with netlink carrier
> > events being delivered to NM.  You'll want to poke around in the NM
> > source in src/nm-netlink-monitor.c, in the
> > netlink_object_message_handler() function, and put some debugging prints
> > in there to see what's going on.  We're especially interested in the
> > 'flags' variable is at this point, and whether it's IFF_UP or
> > IFF_LOWER_UP or what.
>
> actually just calling "ip link" after plugging in that cable would be
> enough. It shows the proper flags.
>
> Jonathan, you might be running an old version of NM that uses IFF_UP for
> carrier detection and that is wrong (not an obvious bug, but neverless a
> bug). For detecting carrier changes via interface flags, IFF_LOWER_UP
> should be used.

It was correct up to 2.6.17, and still works for some drivers that
didn't quite get converted over...  But yes, IFF_LOWER_UP is the real
correct flag, and if something doesn't work with IFF_LOWER_UP then that
driver needs to be fixed.

dan



This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient. If you are not the intended recipient, please be 
aware that any disclosure, copying, distribution or use of this e-mail or any 
attachment is prohibited. If you have received this e-mail in error, please 
contact the sender and delete all copies.

Thank you for your cooperation
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

network status change issue...

[Hooker, Jonathan]

Hey,

I am currently having issues with Network Manager. Whenever I unplug the 
ethernet cable Network Manager picks up on the fact it is disconnected. Then it 
tries to connect to whatever wifi connections I have setup. This works 
properly. The issue I am running into is whenever I plug back in the active 
network cable Network Manager continues to see the ethernet card as 
disconnected. I have to either restart Network Manager or at least uncheck 
Enable Networking and recheck it in the Network Manager menu. Only after I do 
that does Network Manager reconnect to the active ethernet connection... I have 
tried googleing for info on this issue but have come up with nada... Any help 
you could provide would be great. Also, I have setup Network Manager on this 
machine to use a globally configured network config file stored in 
/etc/NetworkManager/system-connections. The config file is setup properly and 
it does work just fine. It just seems that NM stops polling for a change in the 
eth0 device once I unplug it.

Jonathan Hooker
Desktop Support - Engineering (Linux)
Garmin International
jonathan.hoo...@garmin.com


This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient. If you are not the intended recipient, please be 
aware that any disclosure, copying, distribution or use of this e-mail or any 
attachment is prohibited. If you have received this e-mail in error, please 
contact the sender and delete all copies.

Thank you for your cooperation
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

RE: Issue with static ip in NM

[Hooker, Jonathan]

Ok, I found my problem... NetworkManager is super picky on the ownership and 
permissions of the configuration files. They have to be owned by root:root and 
have 0700 permissions.

Jonathan Hooker
Desktop Support - Engineering (Linux)
Garmin International
jonathan.hoo...@garmin.com

-Original Message-
From: Dan Williams [mailto:d...@redhat.com] 
Sent: Friday, April 24, 2009 10:12 AM
To: Hooker, Jonathan
Cc: networkmanager-list@gnome.org
Subject: RE: Issue with static ip in NM

On Fri, 2009-04-24 at 09:05 -0500, Hooker, Jonathan wrote:
> Ok, one last question... NetworkManager is supposed to pick up any changes in 
> the /etc/NetworkManager/system-connections folder assuming the config file is 
> set to plugins=keyfile, correct? If this is the case, why would 
> NetworkManager not be picking up on these changes unless I manually set the 
> file up through the NetworkManager config utility and then overwrite it? So I 
> guess the big question is does NetworkManager pick up on new files put in the 
> system-connections folder as long as they follow the proper syntax?

Yeah, if they follow the proper syntax they should be picked up
automatically.  The keyfile plugin needs some logging.

Dan

> Jonathan Hooker
> Desktop Support - Engineering
> Garmin International
> Office: 913-440-2767
> Need Help? Please Contact the Help Desk: 913-440-2000 or x2000
> jonathan.hoo...@garmin.com
> 
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com] 
> Sent: Thursday, April 23, 2009 9:08 AM
> To: Hooker, Jonathan
> Cc: networkmanager-list@gnome.org
> Subject: RE: Issue with static ip in NM
> 
> On Thu, 2009-04-23 at 07:00 -0500, Hooker, Jonathan wrote:
> > That makes sense. Unfortunately, I am somewhat new to this level of network 
> > management, would it be possible to maybe get an example? Also remembering 
> > that it is possible to have multiple usb devices connected at the same 
> > time...
> 
> Right, which is why NM doesn't use device names, since those change with
> plug/unplug too.  Unfortunately, since most manufacturers seem to ignore
> stuff like the USB serial number and populate that field with zeros or
> some other non-device-unique value, all we've got left is the MAC
> address to uniquely identify a particular device.
> 
> But of course, Garmin sets a valid, globally unique serial number on
> every device, right?  That makes your life a lot easier.
> 
> So you'll put some udev rules files in /etc/udev/rules.d (the
> user-editable rules directory) that detect the presence of your device,
> and run a small helper script which can then assign a MAC to the device
> based off the serial number.  Check out:
> 
> http://reactivated.net/writing_udev_rules.html
> 
> You'll be matching sysfs attributes, so something like:
> 
> ACTION!="add|change", GOTO="fake_mac_end"
> SUBSYSTEM!="usb", GOTO="fake_mac_end"
> 
> SUBSYSTEMS=="usb", ATTRS{idVendor}!="", GOTO="fake_mac_end"
> SUBSYSTEMS=="usb", ATTRS{idProduct}!="", GOTO="fake_mac_end"
> 
> SUBSYSTEMS=="usb", ATTRS{iSerial}=="?*", 
> ENV{ID_FAKE_MAC_USB_SERIAL}="$attr{iSerial}"
> SUBSYSTEMS=="usb", IMPORT{program}="fake-the-mac $env{ID_FAKE_MAC_USB_SERIAL} 
> $tempnode", GOTO="fake_mac_end"
> 
> LABEL="fake_mac_end"
> 
> then in the script /lib/udev/fake-the-mac, you'll assign a MAC of your
> choice (maybe by hashing the serial #) to the device in argv[2] using
> ethtool or whatever.
> 
> Dan
> 
> > These are actually development devices. They do have the capability of 
> > getting out on the network but it is just because of some routing rules 
> > where we route its static ip through the eth0 of the machine to allow it on.
> > 
> > Jonathan Hooker
> > Desktop Support - Engineering (Linux)
> > Garmin International
> > jonathan.hoo...@garmin.com
> > 
> > -Original Message-
> > From: Dan Williams [mailto:d...@redhat.com]
> > Sent: Thursday, April 23, 2009 6:52 AM
> > To: Hooker, Jonathan
> > Cc: networkmanager-list@gnome.org
> > Subject: Re: Issue with static ip in NM
> > 
> > On Thu, 2009-04-23 at 06:09 -0500, Hooker, Jonathan wrote:
> > > Hi,
> > >
> > >
> > >
> > > I am currently having some issues with setting a static ip to a usb0
> > > ethernet device due to the fact that it changes mac addresses every
> > > time I plug it in. Is there any means of predicting this change so
> > > tha

RE: Issue with static ip in NM

[Hooker, Jonathan]

Ok, one last question... NetworkManager is supposed to pick up any changes in 
the /etc/NetworkManager/system-connections folder assuming the config file is 
set to plugins=keyfile, correct? If this is the case, why would NetworkManager 
not be picking up on these changes unless I manually set the file up through 
the NetworkManager config utility and then overwrite it? So I guess the big 
question is does NetworkManager pick up on new files put in the 
system-connections folder as long as they follow the proper syntax?

Jonathan Hooker
Desktop Support - Engineering
Garmin International
Office: 913-440-2767
Need Help? Please Contact the Help Desk: 913-440-2000 or x2000
jonathan.hoo...@garmin.com

-Original Message-
From: Dan Williams [mailto:d...@redhat.com] 
Sent: Thursday, April 23, 2009 9:08 AM
To: Hooker, Jonathan
Cc: networkmanager-list@gnome.org
Subject: RE: Issue with static ip in NM

On Thu, 2009-04-23 at 07:00 -0500, Hooker, Jonathan wrote:
> That makes sense. Unfortunately, I am somewhat new to this level of network 
> management, would it be possible to maybe get an example? Also remembering 
> that it is possible to have multiple usb devices connected at the same time...

Right, which is why NM doesn't use device names, since those change with
plug/unplug too.  Unfortunately, since most manufacturers seem to ignore
stuff like the USB serial number and populate that field with zeros or
some other non-device-unique value, all we've got left is the MAC
address to uniquely identify a particular device.

But of course, Garmin sets a valid, globally unique serial number on
every device, right?  That makes your life a lot easier.

So you'll put some udev rules files in /etc/udev/rules.d (the
user-editable rules directory) that detect the presence of your device,
and run a small helper script which can then assign a MAC to the device
based off the serial number.  Check out:

http://reactivated.net/writing_udev_rules.html

You'll be matching sysfs attributes, so something like:

ACTION!="add|change", GOTO="fake_mac_end"
SUBSYSTEM!="usb", GOTO="fake_mac_end"

SUBSYSTEMS=="usb", ATTRS{idVendor}!="", GOTO="fake_mac_end"
SUBSYSTEMS=="usb", ATTRS{idProduct}!="", GOTO="fake_mac_end"

SUBSYSTEMS=="usb", ATTRS{iSerial}=="?*", 
ENV{ID_FAKE_MAC_USB_SERIAL}="$attr{iSerial}"
SUBSYSTEMS=="usb", IMPORT{program}="fake-the-mac $env{ID_FAKE_MAC_USB_SERIAL} 
$tempnode", GOTO="fake_mac_end"

LABEL="fake_mac_end"

then in the script /lib/udev/fake-the-mac, you'll assign a MAC of your
choice (maybe by hashing the serial #) to the device in argv[2] using
ethtool or whatever.

Dan

> These are actually development devices. They do have the capability of 
> getting out on the network but it is just because of some routing rules where 
> we route its static ip through the eth0 of the machine to allow it on.
> 
> Jonathan Hooker
> Desktop Support - Engineering (Linux)
> Garmin International
> jonathan.hoo...@garmin.com
> 
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com]
> Sent: Thursday, April 23, 2009 6:52 AM
> To: Hooker, Jonathan
> Cc: networkmanager-list@gnome.org
> Subject: Re: Issue with static ip in NM
> 
> On Thu, 2009-04-23 at 06:09 -0500, Hooker, Jonathan wrote:
> > Hi,
> >
> >
> >
> > I am currently having some issues with setting a static ip to a usb0
> > ethernet device due to the fact that it changes mac addresses every
> > time I plug it in. Is there any means of predicting this change so
> > that I can get the its config file
> > in /etc/NetworkManager/system-connections setup properly? Thanks for
> > your help!
> 
> One way to do this is to set up a udev rules file that will always
> assign a custom MAC to the device.  Since the MAC comes up random, the
> device clearly isn't used to connect to a real ethernet network, and
> it's probably a PocketPC/Windows Mobile device?
> 
> Dan
> 
> >
> >
> > Jonathan Hooker
> >
> > Desktop Support – Engineering (Linux)
> >
> > Garmin International
> >
> > jonathan.hoo...@garmin.com
> >
> >
> >
> >
> > __
> > This e-mail and any attachments may contain confidential material for
> > the sole use of the intended recipient. If you are not the intended
> > recipient, please be aware that any disclosure, copying, distribution
> > or use of this e-mail or any attachment is prohibited. If you have
> > received this e-mail in error, please contact the sender and delete
> > all copies.
> >
> > Thank you for your

RE: Issue with static ip in NM

[Hooker, Jonathan]

That makes sense. Unfortunately, I am somewhat new to this level of network 
management, would it be possible to maybe get an example? Also remembering that 
it is possible to have multiple usb devices connected at the same time...

These are actually development devices. They do have the capability of getting 
out on the network but it is just because of some routing rules where we route 
its static ip through the eth0 of the machine to allow it on.

Jonathan Hooker
Desktop Support - Engineering (Linux)
Garmin International
jonathan.hoo...@garmin.com

-Original Message-
From: Dan Williams [mailto:d...@redhat.com]
Sent: Thursday, April 23, 2009 6:52 AM
To: Hooker, Jonathan
Cc: networkmanager-list@gnome.org
Subject: Re: Issue with static ip in NM

On Thu, 2009-04-23 at 06:09 -0500, Hooker, Jonathan wrote:
> Hi,
>
>
>
> I am currently having some issues with setting a static ip to a usb0
> ethernet device due to the fact that it changes mac addresses every
> time I plug it in. Is there any means of predicting this change so
> that I can get the its config file
> in /etc/NetworkManager/system-connections setup properly? Thanks for
> your help!

One way to do this is to set up a udev rules file that will always
assign a custom MAC to the device.  Since the MAC comes up random, the
device clearly isn't used to connect to a real ethernet network, and
it's probably a PocketPC/Windows Mobile device?

Dan

>
>
> Jonathan Hooker
>
> Desktop Support – Engineering (Linux)
>
> Garmin International
>
> jonathan.hoo...@garmin.com
>
>
>
>
> __
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient. If you are not the intended
> recipient, please be aware that any disclosure, copying, distribution
> or use of this e-mail or any attachment is prohibited. If you have
> received this e-mail in error, please contact the sender and delete
> all copies.
>
> Thank you for your cooperation
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list


This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient. If you are not the intended recipient, please be 
aware that any disclosure, copying, distribution or use of this e-mail or any 
attachment is prohibited. If you have received this e-mail in error, please 
contact the sender and delete all copies.

Thank you for your cooperation
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Issue with static ip in NM

[Hooker, Jonathan]

Hi,

I am currently having some issues with setting a static ip to a usb0 ethernet 
device due to the fact that it changes mac addresses every time I plug it in. 
Is there any means of predicting this change so that I can get the its config 
file in /etc/NetworkManager/system-connections setup properly? Thanks for your 
help!

Jonathan Hooker
Desktop Support - Engineering (Linux)
Garmin International
jonathan.hoo...@garmin.com


This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient. If you are not the intended recipient, please be 
aware that any disclosure, copying, distribution or use of this e-mail or any 
attachment is prohibited. If you have received this e-mail in error, please 
contact the sender and delete all copies.

Thank you for your cooperation
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

RE: Issue with Auto eth0

[Hooker, Jonathan]

It was. The problem was that we don't use the MAC address because we are 
creating an image off of this configuration so we want the network manager to 
be smart enough to look for the actual device and identify it without the MAC 
address. We can not use the MAC address because it would be replicated across 
all of the Linux machines across the network. 


Jonathan Hooker
Desktop Support - Engineering
Garmin International
Office: 913-440-2767
Helpdesk: 913-440-2000 or x2000
jonathan.hoo...@garmin.com

-Original Message-
From: Dan Williams [mailto:d...@redhat.com] 
Sent: Wednesday, April 08, 2009 10:34 AM
To: Hooker, Jonathan
Cc: Tambet Ingo; networkmanager-list@gnome.org
Subject: RE: Issue with Auto eth0

On Fri, 2009-04-03 at 02:51 -0500, Hooker, Jonathan wrote:
> Ok, thanks! One more question... My developers use a usb ethernet connection 
> to connect to their development devices. Is there any way to tell NM to 
> default to eth0 always and when the usb0 gets plugged in to automatically 
> connect to it as a second ethernet connection?

nm-system-settings should also pick up existing ifcfg files in 
/etc/sysconfig/network-scripts.  Was that not happening for you?

Dan

> 
> Jonathan Hooker
> Desktop Support - Engineering
> Garmin International
> Office: 913-440-2767
> Helpdesk: 913-440-2000 or x2000
> jonathan.hoo...@garmin.com
> 
> -Original Message-
> From: Tambet Ingo [mailto:tam...@gmail.com]
> Sent: Friday, April 03, 2009 2:33 AM
> To: Hooker, Jonathan
> Cc: networkmanager-list@gnome.org
> Subject: Re: Issue with Auto eth0
> 
> 2009/4/3 Hooker, Jonathan :
> > Hi,
> >
> > I am a system administrator for a large (300+) fedora desktop 
> > environment and am in the process of creating a new image to deploy 
> > to all of my developers. I have been having issues with setting up 
> > NM to connect properly to our dhcp servers so that we can configure 
> > forward dns lookups. Basically what I have done is create an Auto 
> > Ethernet connection which has the following gconf settings:
> >
> >  /system/networking/connections/1/ipv4:
> >   routes = []
> >   addresses = []
> >   method = auto
> >   dhcp-hostname = testd63fed
> >   dhcp-client-id = nixdns-testd63fed
> >   dns-search = [garmin.com,ad.garmin.com,nix.garmin.com]
> >   name = ipv4
> >   dns = []
> >  /system/networking/connections/1/802-3-ethernet:
> >   name = 802-3-ethernet
> >   duplex = full
> >  /system/networking/connections/1/connection:
> >   id = Auto Ethernet
> >   timestamp = 1238728735
> >   type = 802-3-ethernet
> >   uuid = 2d204a05-4c70-4080-ad23-34b53d5a95fe
> >   name = connection
> > The problem is that this does not by default start when the system 
> > does. I have also tried putting these settings in the root user's 
> > gconf. Is there any way I can tell Network Manager to by default 
> > select Auto Ethernet as opposed to the standard System eth0? I know 
> > that System eth0 pulls from my ifcfg-eth0 scripts but there is no 
> > way I can tell of sending the dhcp-hostname and dhcp-client-id back 
> > to the dhcp server without using this or dhclient. I would really 
> > like for all of my network device settings to be managed from the same 
> > program. Any suggestions would be greatly appreciated!
> 
> NetworkManager has two types of setting providers: User settings (from gconf, 
> available only while the user is logged in) and System settings (always 
> available). System settings have different sources (plugins) that allow 
> taking configuration data from multiple sources (distro specific shell script 
> setups, NM's own store, ...). The problem with supporting these different 
> sources is that they never match one to one with NM - Missing variables, 
> extra variables, variables with slightly different meanings, ...
> 
> So you'll want a "System setting" with NM's own store. Here's how you can do 
> it:
> 
> * Modify /etc/NetworkManager/nm-system-settings.conf file's [main] section, 
> 'plugins' keyword so it only has "keyfile" (NM's native settings storage):
> plugins=keyfile
> 
> That'll make sure you have a writable plugin and the distro one (which 
> doesn't provide all the options you require) doesn't interfere. Put that 
> changed configuration to your deployment image.
> 
> * Restart nm-system-settings by issuing 'sudo killall nm-system-settings'. 
> NetworkManager will restart it automatically.
> This step is needed to make the system settings provider use the new 
> configuration from step 1.
> 
> * As any logged in user, open the connectio

RE: Issue with Auto eth0

[Hooker, Jonathan]

Ok. One more question... Is there a reason why I can not just create a file in 
/etc/NetworkManager/system-connections that has all of the right settings and 
NM just pick it up? I am having to change certain fields in the config and I 
just figured I could just use a perl script to replace the whole file...


Jonathan Hooker
Desktop Support - Engineering
Garmin International
Office: 913-440-2767
Helpdesk: 913-440-2000 or x2000
jonathan.hoo...@garmin.com

-Original Message-
From: Tambet Ingo [mailto:tam...@gmail.com]
Sent: Friday, April 03, 2009 3:06 AM
To: Hooker, Jonathan
Cc: networkmanager-list@gnome.org
Subject: Re: Issue with Auto eth0

On Fri, Apr 3, 2009 at 10:51, Hooker, Jonathan  
wrote:
> Ok, thanks! One more question... My developers use a usb ethernet connection 
> to connect to their development devices. Is there any way to tell NM to 
> default to eth0 always and when the usb0 gets plugged in to automatically 
> connect to it as a second ethernet connection?

Yes, that is also the default behavior. If both devices just need to use DHCP, 
then one connection data is enough and both devices can use it. There's a "MAC 
address" field in the connection editor to tie the configuration with specific 
device. If you require different connection settings, create two connections 
and specify the MAC address on both to lock the connection data to specific 
device.

Tambet

This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient. If you are not the intended recipient, please be 
aware that any disclosure, copying, distribution or use of this e-mail or any 
attachment is prohibited. If you have received this e-mail in error, please 
contact the sender and delete all copies.

Thank you for your cooperation
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

RE: Issue with Auto eth0

[Hooker, Jonathan]

Ok, thanks! One more question... My developers use a usb ethernet connection to 
connect to their development devices. Is there any way to tell NM to default to 
eth0 always and when the usb0 gets plugged in to automatically connect to it as 
a second ethernet connection?


Jonathan Hooker
Desktop Support - Engineering
Garmin International
Office: 913-440-2767
Helpdesk: 913-440-2000 or x2000
jonathan.hoo...@garmin.com

-Original Message-
From: Tambet Ingo [mailto:tam...@gmail.com]
Sent: Friday, April 03, 2009 2:33 AM
To: Hooker, Jonathan
Cc: networkmanager-list@gnome.org
Subject: Re: Issue with Auto eth0

2009/4/3 Hooker, Jonathan :
> Hi,
>
> I am a system administrator for a large (300+) fedora desktop
> environment and am in the process of creating a new image to deploy to
> all of my developers. I have been having issues with setting up NM to
> connect properly to our dhcp servers so that we can configure forward
> dns lookups. Basically what I have done is create an Auto Ethernet
> connection which has the following gconf settings:
>
>  /system/networking/connections/1/ipv4:
>   routes = []
>   addresses = []
>   method = auto
>   dhcp-hostname = testd63fed
>   dhcp-client-id = nixdns-testd63fed
>   dns-search = [garmin.com,ad.garmin.com,nix.garmin.com]
>   name = ipv4
>   dns = []
>  /system/networking/connections/1/802-3-ethernet:
>   name = 802-3-ethernet
>   duplex = full
>  /system/networking/connections/1/connection:
>   id = Auto Ethernet
>   timestamp = 1238728735
>   type = 802-3-ethernet
>   uuid = 2d204a05-4c70-4080-ad23-34b53d5a95fe
>   name = connection
> The problem is that this does not by default start when the system
> does. I have also tried putting these settings in the root user's
> gconf. Is there any way I can tell Network Manager to by default
> select Auto Ethernet as opposed to the standard System eth0? I know
> that System eth0 pulls from my ifcfg-eth0 scripts but there is no way
> I can tell of sending the dhcp-hostname and dhcp-client-id back to the
> dhcp server without using this or dhclient. I would really like for
> all of my network device settings to be managed from the same program. Any 
> suggestions would be greatly appreciated!

NetworkManager has two types of setting providers: User settings (from gconf, 
available only while the user is logged in) and System settings (always 
available). System settings have different sources (plugins) that allow taking 
configuration data from multiple sources (distro specific shell script setups, 
NM's own store, ...). The problem with supporting these different sources is 
that they never match one to one with NM - Missing variables, extra variables, 
variables with slightly different meanings, ...

So you'll want a "System setting" with NM's own store. Here's how you can do it:

* Modify /etc/NetworkManager/nm-system-settings.conf file's [main] section, 
'plugins' keyword so it only has "keyfile" (NM's native settings storage):
plugins=keyfile

That'll make sure you have a writable plugin and the distro one (which doesn't 
provide all the options you require) doesn't interfere. Put that changed 
configuration to your deployment image.

* Restart nm-system-settings by issuing 'sudo killall nm-system-settings'. 
NetworkManager will restart it automatically.
This step is needed to make the system settings provider use the new 
configuration from step 1.

* As any logged in user, open the connection editor (nm-applet's right-click 
menu, Edit Connections...), create the configuration you'd like to use, and 
check "Available to all users". The last step is important, that's the switch 
between User connections and System connections. You want system connection, 
aka available to all users.

This last step will create a configuration file in 
/etc/NetworkManager/system-connections/ directory that contains all the 
connection information. Put that to your deployment image.

With these settings, NetworkManager will activate the connection on system 
boot, before any user is logged in, using all the settings known to NM.

Tambet

This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient. If you are not the intended recipient, please be 
aware that any disclosure, copying, distribution or use of this e-mail or any 
attachment is prohibited. If you have received this e-mail in error, please 
contact the sender and delete all copies.

Thank you for your cooperation
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

RE: Issue with Auto eth0

[Hooker, Jonathan]

Also, might there be a way to just add an option: DHCP_CLIENT_ID to ifcfg so 
that NM would just pick up on it and send it to the DHCP server?


Jonathan Hooker
Desktop Support - Engineering
Garmin International
jonathan.hoo...@garmin.com

-Original Message-
From: Hooker, Jonathan
Sent: Thursday, April 02, 2009 11:34 PM
To: networkmanager-list@gnome.org
Subject: Issue with Auto eth0

Hi,

I am a system administrator for a large (300+) fedora desktop environment and 
am in the process of creating a new image to deploy to all of my developers. I 
have been having issues with setting up NM to connect properly to our dhcp 
servers so that we can configure forward dns lookups. Basically what I have 
done is create an Auto Ethernet connection which has the following gconf 
settings:

 /system/networking/connections/1/ipv4:
  routes = []
  addresses = []
  method = auto
  dhcp-hostname = testd63fed
  dhcp-client-id = nixdns-testd63fed
  dns-search = [garmin.com,ad.garmin.com,nix.garmin.com]
  name = ipv4
  dns = []
 /system/networking/connections/1/802-3-ethernet:
  name = 802-3-ethernet
  duplex = full
 /system/networking/connections/1/connection:
  id = Auto Ethernet
  timestamp = 1238728735
  type = 802-3-ethernet
  uuid = 2d204a05-4c70-4080-ad23-34b53d5a95fe
  name = connection

The problem is that this does not by default start when the system does. I have 
also tried putting these settings in the root user's gconf. Is there any way I 
can tell Network Manager to by default select Auto Ethernet as opposed to the 
standard System eth0? I know that System eth0 pulls from my ifcfg-eth0 scripts 
but there is no way I can tell of sending the dhcp-hostname and dhcp-client-id 
back to the dhcp server without using this or dhclient. I would really like for 
all of my network device settings to be managed from the same program. Any 
suggestions would be greatly appreciated!

Jonathan Hooker
Desktop Support - Engineering
Garmin International
jonathan.hoo...@garmin.com


This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient. If you are not the intended recipient, please be 
aware that any disclosure, copying, distribution or use of this e-mail or any 
attachment is prohibited. If you have received this e-mail in error, please 
contact the sender and delete all copies.

Thank you for your cooperation
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Issue with Auto eth0

[Hooker, Jonathan]

Hi,

I am a system administrator for a large (300+) fedora desktop environment and 
am in the process of creating a new image to deploy to all of my developers. I 
have been having issues with setting up NM to connect properly to our dhcp 
servers so that we can configure forward dns lookups. Basically what I have 
done is create an Auto Ethernet connection which has the following gconf 
settings:

 /system/networking/connections/1/ipv4:
  routes = []
  addresses = []
  method = auto
  dhcp-hostname = testd63fed
  dhcp-client-id = nixdns-testd63fed
  dns-search = [garmin.com,ad.garmin.com,nix.garmin.com]
  name = ipv4
  dns = []
 /system/networking/connections/1/802-3-ethernet:
  name = 802-3-ethernet
  duplex = full
 /system/networking/connections/1/connection:
  id = Auto Ethernet
  timestamp = 1238728735
  type = 802-3-ethernet
  uuid = 2d204a05-4c70-4080-ad23-34b53d5a95fe
  name = connection
The problem is that this does not by default start when the system does. I have 
also tried putting these settings in the root user's gconf. Is there any way I 
can tell Network Manager to by default select Auto Ethernet as opposed to the 
standard System eth0? I know that System eth0 pulls from my ifcfg-eth0 scripts 
but there is no way I can tell of sending the dhcp-hostname and dhcp-client-id 
back to the dhcp server without using this or dhclient. I would really like for 
all of my network device settings to be managed from the same program. Any 
suggestions would be greatly appreciated!

Jonathan Hooker
Desktop Support - Engineering
Garmin International
jonathan.hoo...@garmin.com



This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient. If you are not the intended recipient, please be 
aware that any disclosure, copying, distribution or use of this e-mail or any 
attachment is prohibited. If you have received this e-mail in error, please 
contact the sender and delete all copies.

Thank you for your cooperation
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list