Am 26.03.2011 12:05, schrieb Jon Masters:
Hello,
So, back in the good old days, one could just type this:
ifconfig eth0 some_temp_ip up
Then it became necessary to:
/etc/init.d/NetworkManager stop
Then it became necessary to:
systemctl disable NetworkManager.service
Just to try to get the interface left alone.
But when the link it's attached to drops, the settings are immediately
being dropped and the interface unconfigured. So, what have I missed?
What's the other thing that's trying to be all "helpful" but actually
preventing me from running TFTP usefully? Sure, I could plug it into a
switch and go all Windows 95 on this, but...I'd rather not.
Nobody stops you to disable Network-Manager, DHCP, AVAHI and the other noob-crap
and write your /etc/sysconfig/network-scripts/ifcfg-eth0 manually as i do
everytime directly after the first boot and i guess the next 20 years
this will be the same on a unix-like system
the whole network-config can be like this
replace 127.0.0.1 by your namservers, disable
all things you do not need and type
* chkconfig network on
* service network start
after the basic configuration
[root@srv-rhsoft:~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
IPADDR=192.168.1.2
NETWORK=192.168.1.0
GATEWAY=192.168.1.1
BROADCAST=192.168.1.255
NETMASK=255.255.255.0
TYPE=Ethernet
BOOTPROTO=static
ONBOOT=yes
NM_CONTROLLED=no
USERCTL=no
IPV6INIT=no
[root@srv-rhsoft:~]$ cat /etc/resolv.conf
nameserver 127.0.0.1