Robert Locke wrote:
On Mon, 2006-12-11 at 12:35 -0600, Marc Schwartz wrote:
On Mon, 2006-12-11 at 12:12 -0500, Matthew Saltzman wrote:
On Mon, 11 Dec 2006, Marc Schwartz wrote:
Aaron Konstam wrote:
On Mon, 2006-12-11 at 09:42 -0500, Gene Poole wrote:
Beware - It seems that the first time you use NetworkManager it destroys
the contents of you resolv.conf (built at install time). It also seems
that it doesn't make a backup copy first.
Thanks,
Gene Poole
I have never noticed that this is true. I will have to look into your
statement.
If you have a network profile that is based upon a fixed IP address and DNS
servers (which I do have at home behind a router with DHCP disabled), then NM
will overwrite the configurations for that profile, including
/etc/resolv.conf.
Have you tried using "system-config-network-cmd --profile profilename
--activate"?
If you have two profiles, one that is activated when you boot your
system wanting NM (only lo adapter is activated, all others are
"ONBOOT=no"), the other has your Ethernet adapter turned on and
"different DNS settings".... Then if you activate the profile with the
above command (rather than "ifup eth0"), it should copy in the new
settings.
Also, take a look at the "netprofile=profilename" kernel argument, that
can reset your system back to the NM profile by default every time you
boot.....
Rob,
The above command in your first paragraph is what I have as part of my
scripts, but I need to disable NM first prior to use.
This script activates the required profile, ups the interface, brings up
the firestarter GUI and starts the firewall (which I use for iptables
config) and then runs fetchmail to get my e-mail.
I have a few similar scripts for differing profiles, all stuck in my
nautilus scripts folder, so that I can just right click on the desktop
and run them.
I could in practice just use these for all occasions, but using NM for
DHCP based situations, such as in my office or when travelling and using
wireless, is easier.
None of my interfaces are activated on boot, as there are of course
times when my laptop is not connected. This saves time during boot,
rather than waiting for a timeout to occur.
I had looked at one time using the kernel boot arguments, but using the
scripts are easier.
When NM supports profiles, as Matthew suggested earlier, this will
become a non-issue.
Thanks for your post.
Marc
