On Fri, 2009-04-24 at 10:21 -0500, Hooker, Jonathan wrote: > 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.
Right, since secrets are stored in the files, they shouldn't be readable by an unprivileged user. Dan > 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}!="<your vid>", GOTO="fake_mac_end" > > SUBSYSTEMS=="usb", ATTRS{idProduct}!="<your pid>", 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 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
