Cannot bring eth1 up
Rick Stevens
ricks at nerd.com
Tue May 10 19:43:20 UTC 2011
On 05/10/2011 10:13 AM, Aaron Gray wrote:
> I cannot seem to bring eth1 up.
>
> # ifup eth1
> Error: Connection activation failed: Device not managed by
> NetworkManager or unavailable
>
> # cat ifcfg-eth1
> GATEWAY0=192.168.0.1
> IPV6INIT=yes
> BROADCAST="192.168.1.255"
> DNS1=8.8.8.8
> UUID=9c92fad9-6ecb-3e6c-eb4d-8a47c6f50c04
> BOOTPROTO=none
> NAME="System eth1"
> PREFIX0=24
> MACADDR="00:26:18:E4:99:77"
> NM_CONTROLLED=yes
> IPV6_FAILURE_FATAL=no
> TYPE=Ethernet
> DEVICE=eth1
> IPADDR0=192.168.1.1
> IPV6_AUTOCONF=yes
> MTU=""
> NETMASK="255.255.255.0"
> IPV6_DEFROUTE=yes
> DEFROUTE=yes
> IPADDR="192.168.1.1"
> NETWORK=""
> IPV4_FAILURE_FATAL=yes
> ONBOOT=no
> HWADDR=00:26:18:E4:99:77
> IPV6_PEERDNS=yes
> IPV6_PEERROUTES=yes
I dunno about the "IPADDR0", "PREFIX0" stuff (in fact, anything with a
"blah0". An interface has but one IP, one netmask, etc. If you want
multiple IPs on a NIC you set up an alias such as eth1:1. Try a minimum
config and see if that works:
DEVICE=eth1
BOOTPROTO=static
BROADCAST=192.168.1.255
HWADDR=00:26:18:E4:99:77
IPADDR=192.168.1.1
IPV6INIT=yes
IPV6_AUTOCONF=yes
NETMASK=255.255.255.0
NETWORK=192.168.1.0
DNS1=8.8.8.8
NM_CONTROLLED=yes
ONBOOT=no
(in truth, you don't need the "NETWORK=" or "BROADCAST=" bits
either...they're inferred by the desired IP and netmask).
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, C2 Hosting ricks at nerd.com -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
- -
- Diplomacy: The art of saying "Nice doggy!" until you can find a -
- big enough rock. -
----------------------------------------------------------------------
More information about the users
mailing list