<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/>  <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> > <o:p></o:p> > SNIP<o:p></o:p> > <o:p></o:p> > >> I think the issue comes when you are not using DHCP as many do. If<o:p></o:p> > over the<o:p></o:p> > >> years, you have used setup scripts the NM default approach is a<o:p></o:p> > problem.<o:p></o:p> > >><o:p></o:p> > >> On this fresh install I had to setup my network info in NM at first.<o:p></o:p> > Then I<o:p></o:p> > >> moved to network services and turned off NM. A two step approach to<o:p></o:p> > get<o:p></o:p> > >> back to the Old way.<o:p></o:p> > >><o:p></o:p> > >> As for network info, I found I had to edit the<o:p></o:p> > /etc/sysconfig/networking<o:p></o:p> > >> manually because system-config-network kept corrupting the settings. I<o:p></o:p> > need<o:p></o:p> > >> to do some testing and file a bug report.<o:p></o:p> > ><o:p></o:p> > ><o:p></o:p> > > On my desktop, I have DHCP available, but i use a static IP.<o:p></o:p> > ><o:p></o:p> > > All I did was use sytem-config-network, and check 'start on boot' and<o:p></o:p> > > uncheck 'controlled by NM'. Does this not work for you guys?<o:p></o:p> > ><o:p></o:p> > ><o:p></o:p> > <o:p></o:p> > I don't have access to DHCP over the wire (YET) but<o:p></o:p> > system-config-network didn't work for me. It wouldn't save the proper<o:p></o:p> > netmask and kept creating it's own. Both here at work and at home.<o:p></o:p> > <o:p></o:p> > As I said, I have to file a bug report. Still trying to get caught up<o:p></o:p> > on email and work from two weeks off for Xmas.<o:p></o:p> > <o:p></o:p> I almost hate to bring this topic up again because it was beaten to death earlier. However…I’m having a problem with NetworkManager scribbling a bizarre netmask into my *SUPPOSEDLY* static address info for eth0.<o:p></o:p> <o:p> </o:p> I get it configured, and it works for a while, then I end up with dns lookup failures. When I go to NetworkManager I find it has duplicated the gateway address (192.168.1.1) into the netmask entry also.<o:p></o:p> <o:p> </o:p> Getting static addressing to work under NetworkManager has been nothing short of a hair-pulling experience. The folks working NetworkManager need to understand that not *ALL* linux boxes will travel…some are single-purpose boxes on networks that have a security policy that mandates static addressing. When one checks the static address button, NetworkManager must absolutely stop scribbling in places it shouldn’t!!!!<o:p></o:p> <o:p> </o:p> Dave McGuffey<o:p></o:p> Principal Information System Security Engineer // NSA-IEM, NSA-IAM<o:p></o:p> SAIC, IISBU, <st1:place w:st="on"><st1:City w:st="on">Columbia</st1:City></st1:place>, <st1:State w:st="on">MD</st1:State><o:p></o:p> <o:p> </o:p> </div> </body> </html>