I have been pulling my hair out over this, but seem to have a work-around after a lot of searching, but I'd like to know if there's a better way. Here's the info:
I'm building a server with F10 that (obviously) needs a static IP address. It seems the best way to handle what's needed is to go ahead and let NetworkManager still control the IP address.
BUT... I need to have that IP address activated at system startup, so it must be configured via system-config-network as System eth0 (and eth1 in this case) and then be controlled by NM.
Unfortunately, this machine - like most systems today - also needs DNS. I'm running named as it's meant to be an internal local DNS server for a bunch of other stuff too, but NM has a VERY nasty habit of overwriting /etc/resolv.conf with something that's basically BLANK. So every reboot, you have problems resolving DNS.
The only solution I have found so far is to: 1) properly re-create /etc/resolv.conf to what it should be 2) set the immutable flag on it (chattr +i /etc/resolv.conf)
This prevents NM from overwriting it.
OK - Fine. This isn't pretty (no work-around is), but it gets me what I need for now.
Since this is a known bug, do we know when there will be a fix for it, preferably in F10? Is there a better way of handling this problem until then?
Cheers,
Chris
-- ==================================== "If you get to thinkin' you're a person of some influence, try orderin' someone else's dog around."
--Cowboy Wisdom
On Sat, 17 Jan 2009 11:10:07 -0700 Christopher A. Williams wrote:
I'm building a server with F10 that (obviously) needs a static IP address. It seems the best way to handle what's needed is to go ahead and let NetworkManager still control the IP address.
Why do you think that's the best way?
NM is great for laptops and stuff that relies on dhcp to obtain an address.
For anything that uses a static address (and especially for a server) use the network service.
On Sat, 2009-01-17 at 11:10 -0700, Christopher A. Williams wrote:
I have been pulling my hair out over this, but seem to have a work-around after a lot of searching, but I'd like to know if there's a better way. Here's the info:
I'm building a server with F10 that (obviously) needs a static IP address. It seems the best way to handle what's needed is to go ahead and let NetworkManager still control the IP address.
BUT... I need to have that IP address activated at system startup, so it must be configured via system-config-network as System eth0 (and eth1 in this case) and then be controlled by NM.
Unfortunately, this machine - like most systems today - also needs DNS. I'm running named as it's meant to be an internal local DNS server for a bunch of other stuff too, but NM has a VERY nasty habit of overwriting /etc/resolv.conf with something that's basically BLANK. So every reboot, you have problems resolving DNS.
The only solution I have found so far is to:
- properly re-create /etc/resolv.conf to what it should be
- set the immutable flag on it (chattr +i /etc/resolv.conf)
This prevents NM from overwriting it.
OK - Fine. This isn't pretty (no work-around is), but it gets me what I need for now.
Since this is a known bug, do we know when there will be a fix for it, preferably in F10? Is there a better way of handling this problem until then?
---- chkconfig NetworkManager off chkconfig network on service NetworkManager stop service network start
Craig
On Sat, 2009-01-17 at 11:10 -0700, Christopher A. Williams wrote:
I have been pulling my hair out over this, but seem to have a work-around after a lot of searching, but I'd like to know if there's a better way. Here's the info:
I'm building a server with F10 that (obviously) needs a static IP address. It seems the best way to handle what's needed is to go ahead and let NetworkManager still control the IP address.
BUT... I need to have that IP address activated at system startup, so it must be configured via system-config-network as System eth0 (and eth1 in this case) and then be controlled by NM.
Unfortunately, this machine - like most systems today - also needs DNS. I'm running named as it's meant to be an internal local DNS server for a bunch of other stuff too, but NM has a VERY nasty habit of overwriting /etc/resolv.conf with something that's basically BLANK. So every reboot, you have problems resolving DNS.
You can tell NetworkManager which DNS servers to use, so that when it overwrites /etc/resolv.conf it does so with the correct information.
If you've installed a GUI on your server, right click on NM, then Edit Connections. Choose System ethX (where X is your interface number), then set the DNS servers to the ones you want.
If your server is text only, edit /etc/sysconfig/network-scripts/ifcfg-ethX, and add the lines DNS1=xxx.xxx.xxx.xxx and DNS2=xxx.xxx.xxx.xxx (where the x's are the IP addresses of your DNS servers; you could set it to 127.0.0.1 if you're running named locally).
Jonathan
On Sat, 17 Jan 2009 11:10:07 -0700 Christopher A. Williams wrote:
The only solution I have found so far is to:
- properly re-create /etc/resolv.conf to what it should be
- set the immutable flag on it (chattr +i /etc/resolv.conf)
That works in fedora, but even better (as others have said) is disabling NetworkManager service and enabling network instead (i.e. go back to the old and unimproved days :-).
I have had to use the chattr thing as the best I could find on various different flavors of linux distributions. I've been doing battle with a host of virtual machines we use for testing software on different distros, and to get networking up and NFS filesystems mounted on all of them at boot time has been like herding cats - every one of them has some different quirk to work around. The most interesting was openSUSE - if you try the chattr trick there, the whole boot comes to a screeching halt and it prints a console message saying "Oh No! I can't screw up your /etc/resolv.conf file, what should I do?"
Fortunately the /etc/resolv.conf file itself on SUSE contains generated comments telling you exactly how to fix it the "official" way. So SUSE are idiots for checking for an error they can't handle, but they are geniuses for actually putting the information you are gonna want to know right in the resolv.conf file instead of just leaving you hopelessly lost.
On Sat, 2009-01-17 at 16:10 -0500, Tom Horsley wrote:
On Sat, 17 Jan 2009 11:10:07 -0700 Christopher A. Williams wrote:
The only solution I have found so far is to:
- properly re-create /etc/resolv.conf to what it should be
- set the immutable flag on it (chattr +i /etc/resolv.conf)
That works in fedora, but even better (as others have said) is disabling NetworkManager service and enabling network instead (i.e. go back to the old and unimproved days :-).
I understand that. The entire point of this exercise was:
1) Not to go back to the old ways 2) Find out if any fixes to NM were known of that will fix this
Fortunately the /etc/resolv.conf file itself on SUSE contains generated comments telling you exactly how to fix it the "official" way. So SUSE are idiots for checking for an error they can't handle, but they are geniuses for actually putting the information you are gonna want to know right in the resolv.conf file instead of just leaving you hopelessly lost.
Nice... That would have saved me a couple of hours of googling.
Cheers,
Chris
-- ================================== By all means marry; If you get a good wife, you'll be happy. If you get a bad one, you'll become a philosopher.
--Socrates
On Sat, 2009-01-17 at 20:39 +0200, Jonathan Dieter wrote:
On Sat, 2009-01-17 at 11:10 -0700, Christopher A. Williams wrote:
I have been pulling my hair out over this, but seem to have a work-around after a lot of searching, but I'd like to know if there's a better way. Here's the info:
I'm building a server with F10 that (obviously) needs a static IP address. It seems the best way to handle what's needed is to go ahead and let NetworkManager still control the IP address.
BUT... I need to have that IP address activated at system startup, so it must be configured via system-config-network as System eth0 (and eth1 in this case) and then be controlled by NM.
Unfortunately, this machine - like most systems today - also needs DNS. I'm running named as it's meant to be an internal local DNS server for a bunch of other stuff too, but NM has a VERY nasty habit of overwriting /etc/resolv.conf with something that's basically BLANK. So every reboot, you have problems resolving DNS.
You can tell NetworkManager which DNS servers to use, so that when it overwrites /etc/resolv.conf it does so with the correct information.
If you've installed a GUI on your server, right click on NM, then Edit Connections. Choose System ethX (where X is your interface number), then set the DNS servers to the ones you want.
I actually tried this. Unfortunately, apparently due to yet another NM bug, these interfaces are shown as read only to NM. Thus it is impossible to change the DNS info.
I also let NM create its own interfaces, which show up as "Auto eth0", "Auto eth1", etc. You are able to feed these DNS information, but they don't activate until you login, and they tend to de-activate upon logout.
If your server is text only, edit /etc/sysconfig/network-scripts/ifcfg-ethX, and add the lines DNS1=xxx.xxx.xxx.xxx and DNS2=xxx.xxx.xxx.xxx (where the x's are the IP addresses of your DNS servers; you could set it to 127.0.0.1 if you're running named locally).
Tried this too. Unfortunately, NM didn't yet recognize something with this (I think it's Peer DNS), so we apparently can't do it this way either.
I actually had tried all of this before posting for the first time. I had already solved the problem well enough to do what was needed. I was just looking for some indication of when this might get fixed. It's clear that NM is the future direction of things. I'm just trying to get myself used to it now...
Cheers,
Chris
-- ============================== "If you are calm while all around you is chaos, then you probably haven't fully understood the magnitude of the situation."
--Unknown
On Sat, 2009-01-17 at 19:20 -0700, Christopher A. Williams wrote:
On Sat, 2009-01-17 at 16:10 -0500, Tom Horsley wrote:
On Sat, 17 Jan 2009 11:10:07 -0700 Christopher A. Williams wrote:
The only solution I have found so far is to:
- properly re-create /etc/resolv.conf to what it should be
- set the immutable flag on it (chattr +i /etc/resolv.conf)
That works in fedora, but even better (as others have said) is disabling NetworkManager service and enabling network instead (i.e. go back to the old and unimproved days :-).
I understand that. The entire point of this exercise was:
- Not to go back to the old ways
---- I think you have a misunderstanding of the role of both 'network' and 'NetworkManager' services.
'network' service is clearly better for server usage as it is a true startup daemon that doesn't require any user interaction.
'NetworkManager' at present provides for userland control which means that it isn't all that useful until a user logs in.
Craig
On Sat, 2009-01-17 at 19:44 -0700, Craig White wrote:
I think you have a misunderstanding of the role of both 'network' and 'NetworkManager' services.
'network' service is clearly better for server usage as it is a true startup daemon that doesn't require any user interaction.
'NetworkManager' at present provides for userland control which means that it isn't all that useful until a user logs in.
That used to be accurate -- but NetworkManager now also handles system-wide network setup. Anaconda and system-config-network both default to setting up NetworkManager connections, which if marked "Connect automatically", will be configured at boot (before login) if connectivity is present.
-Chris
On Sat, 17 Jan 2009 22:17:52 -0500 Matthew Flaschen wrote:
Frank Cox wrote:
NM is great for laptops and stuff that relies on dhcp to obtain an address.
This is a myth. NM is totally unnecessary and harmful for almost any wired connection. It is /not/ useful for wired DHCP.
I disagree. I have NM active on my laptops. I can then use the wireless connection or wired connection without any action required on my part. If I plug in a cable, it's wired. If I don't have a cable plugged in, it's wireless.
NM makes switching back and forth absolutely painless.
On Sat, 2009-01-17 at 19:44 -0700, Craig White wrote:
On Sat, 2009-01-17 at 19:20 -0700, Christopher A. Williams wrote:
On Sat, 2009-01-17 at 16:10 -0500, Tom Horsley wrote:
On Sat, 17 Jan 2009 11:10:07 -0700 Christopher A. Williams wrote:
The only solution I have found so far is to:
- properly re-create /etc/resolv.conf to what it should be
- set the immutable flag on it (chattr +i /etc/resolv.conf)
That works in fedora, but even better (as others have said) is disabling NetworkManager service and enabling network instead (i.e. go back to the old and unimproved days :-).
I understand that. The entire point of this exercise was:
- Not to go back to the old ways
I think you have a misunderstanding of the role of both 'network' and 'NetworkManager' services.
'network' service is clearly better for server usage as it is a true startup daemon that doesn't require any user interaction.
'NetworkManager' at present provides for userland control which means that it isn't all that useful until a user logs in.
No misunderstanding here at all.
Indeed, this was the _original_ intent for NetworkManager. But according to several pieces of information posted here and elsewhere (such as the NetworkManager To Do page at http://live.gnome.org/NetworkManagerToDo), it is morphing into being more. It could very well replace the old network service in due time.
I know I could have done things using system-config-network and the network service. I chose not to for a very specific set of reasons.
-- ==================================== "If you get to thinkin' you're a person of some influence, try orderin' someone else's dog around."
--Cowboy Wisdom
On Sat, 2009-01-17 at 20:50 -0700, Christopher A. Williams wrote:
On Sat, 2009-01-17 at 19:44 -0700, Craig White wrote:
On Sat, 2009-01-17 at 19:20 -0700, Christopher A. Williams wrote:
On Sat, 2009-01-17 at 16:10 -0500, Tom Horsley wrote:
On Sat, 17 Jan 2009 11:10:07 -0700 Christopher A. Williams wrote:
The only solution I have found so far is to:
- properly re-create /etc/resolv.conf to what it should be
- set the immutable flag on it (chattr +i /etc/resolv.conf)
That works in fedora, but even better (as others have said) is disabling NetworkManager service and enabling network instead (i.e. go back to the old and unimproved days :-).
I understand that. The entire point of this exercise was:
- Not to go back to the old ways
I think you have a misunderstanding of the role of both 'network' and 'NetworkManager' services.
'network' service is clearly better for server usage as it is a true startup daemon that doesn't require any user interaction.
'NetworkManager' at present provides for userland control which means that it isn't all that useful until a user logs in.
No misunderstanding here at all.
Indeed, this was the _original_ intent for NetworkManager. But according to several pieces of information posted here and elsewhere (such as the NetworkManager To Do page at http://live.gnome.org/NetworkManagerToDo), it is morphing into being more. It could very well replace the old network service in due time.
I know I could have done things using system-config-network and the network service. I chose not to for a very specific set of reasons.
---- ok - it is still a work in progress and since you understand that - I'll leave you to it.
It seems much more sane to me to use network rather than use NetworkManager and an immutable /etc/resolv.conf but hey, that's just me.
Craig
On Sunday 18 January 2009 03:05:55 Chris Tyler wrote:
On Sat, 2009-01-17 at 19:44 -0700, Craig White wrote:
I think you have a misunderstanding of the role of both 'network' and 'NetworkManager' services.
'network' service is clearly better for server usage as it is a true startup daemon that doesn't require any user interaction.
'NetworkManager' at present provides for userland control which means that it isn't all that useful until a user logs in.
That used to be accurate -- but NetworkManager now also handles system-wide network setup. Anaconda and system-config-network both default to setting up NetworkManager connections, which if marked "Connect automatically", will be configured at boot (before login) if connectivity is present.
Really? It always asks me for a gnome-keyring passphrase after I've logged in and before it connects. If you can tell me how to get this 'Connect automatically' I'd be extremely interested
Anne
On Sun, 18 Jan 2009 08:00:35 +0000 Anne Wilson wrote:
Really? It always asks me for a gnome-keyring passphrase after I've logged in and before it connects. If you can tell me how to get this 'Connect automatically' I'd be extremely interested
Make sure your gnome keyring passphrase matches your login password.
Christopher A. Williams wrote:
The only solution I have found so far is to:
- properly re-create /etc/resolv.conf to what it should be
- set the immutable flag on it (chattr +i /etc/resolv.conf)
3) just add the following options to /etc/sysconfig/networking/devices/ifcfg-X (the name of your connection) PEERDNS=no NM_CONTROLLED=no If you for instance want eth0 not controlled by NetworkManager (because it is a wired connection with a fixed IP) and wlan0 with NetworkManager, change the second option to yes. Please note, that your DNS settings /etc/resolv.conf will never change now unless you manually change it, also when NetworkManger takes control.
Anne Wilson-4 wrote:
That used to be accurate -- but NetworkManager now also handles system-wide network setup. Anaconda and system-config-network both default to setting up NetworkManager connections, which if marked "Connect automatically", will be configured at boot (before login) if connectivity is present.
Really? It always asks me for a gnome-keyring passphrase after I've logged in and before it connects. If you can tell me how to get this 'Connect automatically' I'd be extremely interested
Anne
I would also love to know how to make NM connect system wide for a wireless connection - I tried this on one laptop following some advice on editing the config files to add an additional parameter -
The advice I saw was: "Edit /etc/NetworkManager/nm-system-settings.conf, and add ",keyfile" to the end of the "plugins=" line. Then 'killall -TERM nm-system-settings', and you should be able to make system-wide connections in the connection editor just by checking the "Make available to all users" checkbox."
But it did not work.....
Anyone know how to really make it work in a fully up to date F10 system? Here I am thinking of a wireless connection to an AP using WPA2...
Please man, no chage to flag on it (chattr +i /etc/resolv.conf).
Is not necessary, your only need create a file: vi /etc/dhclient-eth0.conf
Note eth0 is your interface, is could change for: wlan0 or ath0 if is wireless.
check it with: su -c '/sbin/route -n'
and look "Iface".
change eth0 for yours.
Example:
/etc/dhclient-wlan0.conf
And write on the file.
prepend domain-name-servers; DNS1
Or 127.0.0.1 or Your DNS.
And no write neither change file:
/etc/sysconfig/network-scripts/ifcfg-eth0
Please no CHANGE in the file "/etc/sysconfig/network-scripts/ifcfg-eth0" option: Remember change "eth0" for your interface.
NM_CONTROLLED=
Please is would is clean.
And now, restart "NetworkManager". su -c '/sbin/service NetworkManager restart'
And Ready! :-)
Excusme by my english!
-
Anne Wilson -
Chris Tyler -
Christopher A Williams -
Craig White -
Frank Cox -
Jonathan Dieter -
Matthew Flaschen -
mike cloaked -
potat0 -
Tom Horsley -
Tosh