On Thu, 2008-10-02 at 07:03 -0400, Jon Masters wrote: > Hi folks, > > I just installed a test server running F9. For once, I let > NetworkManager run and left the install fairly alone. I statically > configured a set of network settings in anaconda and those are present > in the sysconfig network scripts. But NetworkManager decides it knows > better and reconfigures the interface with DHCP anyway[0]. What version of NM are you running? You'll want whatever is in F9-updates, which should be svn4022 or later. > How is static interface config supposed to work with NetworkManager? > Does this actually work in F9 today? nm-system-settings reads ifcfg files and if those files are minimally valid provides those connections to NM, which uses them. If that's not working for you and you have latest F9 updates installed (again, svn4022 or later) then I'd love to see your ifcfg-eth0 file. Please send and I'll be sure to fix whatever's wrong! > [0] It actually does this even when you create a new "wired network" in > NetworkManager with the correct config (so now you have it in two > places) - it always wants to use its own "Auto eth0" regardless. Looks like the system settings service can't parse the ifcfg file; and if there aren't any valid ethernet connections on the system (unmanaged devices are counted as valid) then nm-system-settings provides an "auto ethernet" connection so that you'll at least get some connectivity when you plug in the cable. Dan -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
