Frank Cox wrote:
On Mon, 10 Mar 2008 18:33:21 -0400
"Kevin J. Cummings" <cummings@xxxxxxxxxxxxxxxxxx> wrote:
*OR* you tell your laptop to *NOT* use DHCP for the ethernet interface,
and configure your static address using system-config-network.
I think you would then lose the benefit of using Network Manager. It's easiest
(in my opinion) to let Network Manager handle all network connections on a
laptop that moves around from place to place.
This may
ultimately involve using some sort of network profiles if your static
address at home differs from your static address at work.
Again, Network Manager will do all of the dirty work for you, if you just set
up your dhcp server to provide a static address to your machine if it's
required.
Frank, unless I totally misread the the original post, there is no "your
dhcp server" to configure to anything, he has been told to use a static
IP address. That means his computer doesn't ask for an IP, it uses the
same IP all the time.
I found that it is possible to remove the NM software and own your
computer again. Then you use one script to start using DHCP and one for
each static IP you use (I never had more than two).
I also have a script to start the WiFi NIC, which so far is always DHCP.
NM is one of those things which works really well as long as you
structure your computer use to do things the way it wants (sounds like
Windows, doesn't it). When you do something out of the ordinary it's
often easier to do it manually.
Using a laptop as an AP to a wired network connection comes to mind as
another one of the things which is easier to do by hand, using familiar
tools. I'm unconvinced that you can get NM to do it at all, but I make
no pretense of being an expert in NM guru-level configuration.
--
Bill Davidsen <davidsen@xxxxxxx>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
