On Thu, 2012-10-04 at 12:35 -0700, jackson byers wrote:
FWIW, the following is my ifcfg-eth0 in my f16box
Note static IP, NM_Controlled=yes
$ less ifcfg-eth0
# Broadcom Corporation NetXtreme BCM5702X Gigabit Ethernet
DEVICE=eth0
HWADDR=00:e0:18:d2:d1:95
BROADCAST=255.255.255.255
ONBOOT=yes
BOOTPROTO=static
IPADDR=192.168.2.8
NETMASK=255.255.255.0
NETWORK=192.168.2.0
GATEWAY=192.168.2.1
TYPE=Ethernet
NM_CONTROLLED=yes
USERCTL=no
PEERDNS=yes
DNS1=206.13.31.12
DNS2=68.94.156.1
DOMAIN=pacbell.net
ifcfg-eth0 (END
does anyone see anything wrong, questionable?
I have been using this at least through
f12, f14, f16
I can't recall where I got all of this, especially
USERCTL=no
PEERDNS=yes
I don't know the meaning of, or the impact of either of these.
Jack
Above is consistent in that
my /etc/resolv.conf says Added by NetworkManager
For many years, I have been using static IP and
NETWORK=192.168.2.0
in contrast the imac is using DHCP
and network 192.168.1.0
You have hit the nail on the head. Your iMac is configured for DHCP and
was working, but your F16 box is configured for static addressing that
does not match what the "new router" is willing to accept.
So, since you have the ifcfg-eth0 file available, edit the file and
change the following line:
BOOTPROTO=static
to
BOOTPROTO=dhcp
You can also safely remove the lines:
IPADDR=192.168.2.8
NETMASK=255.255.255.0
NETWORK=192.168.2.0
GATEWAY=192.168.2.1
DNS1=206.13.31.12
DNS2=68.94.156.1
DOMAIN=pacbell.net
which contain the incorrect static settings.
--Rob