FC17 network issues

[lightman47]

Rather than replacing my server FC14 64 with FC17 64, I (now realized WISELY) plugged in a different drive and installed FC17 64 on it. Install went great! All is stable and most runs great - except networking with 2 NICs which went 'south' in a big hurry! This machine is my gateway. I currently have plugged in the FC14 drive, or I wouldn't be 'connected' and able to write this.

FC 14-64:

Plug this drive in - all works perfectly!


FC 17-64:

After 2 days of alternating between NetworkManager and network, I am running network. Some things have improved; others have gotten worse. {Done a ton of research/print-outs - learned a little but realized how much I don't yet 'get'}. I got connected to the Internet during this process for a while and was able to do the YUM updates/install yesterday morning as long as I disabled the the NIC for my internal network.

My internal network (192.168.0.nn) works great now that I was able to get 'dhcpd' running (recalling the ".conf" file I'd saved on a mounted data drive). We're good "inside" the house.

Currently:

My 'outside' NIC (static for port forwarding reasons 192.168.1.253) to the DSL modem (192.168.1.254) - PINGS great. Indeed, Web Browser will bring-up my DSL modem page, and I can login and adjust the modem settings. EVERYTHING beyond that modem (PING, etc.) is "network unreachable".

My 'inside' NIC (eth1 this session, but will change) - pings 'anywhere' inside the house; all return 100% received / 0% loss. This is regardless of eth(?) assignment.

Worse: Now, even disabling the "inside card" (ifdown eth1 - or whatever it's name is today) no longer produces an Internet connection - the same unreachable message (EXCEPTING it will talk to my DSL modem - ???). Disabling the 'inside' card used to INSTANTLY produce a responsive Internet, but no longer.

I renamed my cards back to eth0 & eth1 - using info from another post here to remove the biosdevname (rpm -e biosdevname)

DISCOVERY: udev keeps changing my eth? assignments with every {n}th reboot!!!! W.T.Heck!!!) I later learned it didn't matter a lot because most network stuff seems to be done by addresses. Firewall, however is another matter (at least as regards the GUI Firewall implementation).

---

I would LOVE to provide you a history of what I have done, but my memory isn't good enough to remember it all (yeh, I did LOTS, especially trying to combat the almost constant udev eth{n} re-assignments). That said, I'll try to provide any info/results you require. Having disabled NetworkManager, I am now able to auto-map the shared drives - so I can run FC17, produce the requested outputs, then plug-in the FC14 system drive to return here to report the results.

[stevea]

EVERYTHING beyond that modem (PING, etc.) is "network unreachable".

Show the routes and interface assignments please
ip route
ip addr

Did you manually edit the /etc/syconfig/net*/../foo.ifcgf files ?

[lightman47]

Show the routes and interface assignments please
ip route

Subnet 0 is my internal network (using DHCPD and working fine)
Subnet 1 is my connection to my DSL modem (outside world)

169.254.0.0/16 dev eth0 scope link metric 1002
169.254.0.0/16 dev eth1 scope link metric 1003
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.253
192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.253

ip addr

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:1b:fc:10:a3:1e brd ff:ff:ff:ff:ff:ff
inet 192.168.0.253/24 brd 192.168.0.255 scope global eth0
inet6 fe80::21b:fcff:fe10:a31e/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether 00:30:f1:1c:b3:7f brd ff:ff:ff:ff:ff:ff
inet 192.168.1.253/24 brd 192.168.1.255 scope global eth1
inet6 fe80::230:f1ff:fe1c:b37f/64 scope link
valid_lft forever preferred_lft forever

Did you manually edit the /etc/syconfig/net*/../foo.ifcgf files ?

I edited /etc/sysconfig/network-scripts/ifcfg-eth(n) a number of times -

ifcfg-eth0:

TYPE=Ethernet
BOOTPROTO=none
IPADDR0=192.168.1.253
PREFIX0=24
GATEWAY0=192.168.1.254
DNS1=166.102.165.13
DNS2=207.91.5.20
DNS3=8.8.8.8
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="eth0"
UUID=e15d9926-ddec-43c1-9abc-93b28b4a0f1c
ONBOOT=yes
NM_CONTROLLED=no
HWADDR=00:30:F1:1C:B3:7F

ifcfg-eth1:

TYPE=Ethernet
BOOTPROTO=none
IPADDR0=192.168.0.253
PREFIX0=24
GATEWAY0=192.168.1.253
DNS1=192.168.1.254
DNS2=166.102.165.13
DNS3=207.91.5.20
DOMAIN=egan
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="eth1"
UUID=e90f80c4-df7e-4564-9f10-599d8ed045c7
ONBOOT=yes
NM_CONTROLLED=no
HWADDR=00:1B:FC:10:A3:1E

Thank you.
---- edit ---

I might mention that I ran Wireshark and can see pings arriving from the inside interface (destined ultimately for the Internet), but they never make it to the other NIC - like the machine is a black hole, kinda.