F19 - networking problem & questions

[Cristian Sava]

I have a server with two NICs (on-board and attached).
HW: ASRock H67M-GE + I3-2120 + 8GB + 1TB (hdd, sata)

[root at physics network-scripts]# cat ifcfg-enp4s0
IPV6_PEERDNS="yes"
IPV6INIT="yes"
UUID="b43c0128-ec02-4793-98c9-f396fb9438d2"
IPADDR1="192.168.1.1"
IPADDR0="172.16.0.1"
PREFIX1="24"
PREFIX0="16"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="yes"
HWADDR="64:70:02:14:43:EF"
BOOTPROTO="none"
IPV6_DEFROUTE="yes"
IPV6_AUTOCONF="yes"
IPV6_FAILURE_FATAL="no"
IPV6_PEERROUTES="yes"
TYPE="Ethernet"
ONBOOT="yes"
NAME="enp4s0"
[root at physics network-scripts]# cat ifcfg-enp5s0
TYPE=Ethernet
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=enp5s0
UUID=fc903246-75fa-4680-86f8-b5132fc891c5
ONBOOT=yes
IPADDR0=193.x.y.130
PREFIX0=26
GATEWAY0=193.x.y.129
DNS1=193.x.y.254
DOMAIN=central.ucv.ro
IPADDR1=193.x.y.162
PREFIX1=26
IPADDR2=193.x.y.163
PREFIX2=26
HWADDR=00:25:22:F9:71:3D
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes

[root at physics ~]# route
Kernel IP routing table
Destination  Gateway         Genmask      Flags Metric Ref Use Iface
default      g129.central.uc 0.0.0.0         UG  0      0   0 p5p1
link-local     *             255.255.0.0     U   1002   0   0 p4p1
link-local     *             255.255.0.0     U   1003   0   0 p5p1
172.16.0.0     *             255.255.0.0     U   1      0   0 p4p1
192.168.1.0    *             255.255.255.0   U   0      0   0 p4p1
193.x.y.128    *             255.255.255.192 U   1      0   0 p5p1

[root at s194 sysconfig]# cat iptables
# Custom file edited on 02-Jul-2013
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m conntrack --ctstate NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j ACCEPT
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
# Completed on 2013-07-02 11:48
*nat
:PREROUTING ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A PREROUTING --dst 193.x.y.162 -p tcp -j DNAT --to 192.168.1.73
-A OUTPUT --dst 193.x.y.162 -p tcp -j DNAT --to 192.168.1.73
-A PREROUTING --dst 193.x.y.163 -p tcp -j DNAT --to 192.168.1.200
-A OUTPUT --dst 193.x.y.163 -p tcp -j DNAT --to 192.168.1.200
-A POSTROUTING -s 192.168.1.0/24 -p tcp --dst 192.168.1.73 --dport 22 -j
SNAT --to 192.168.1.1
-A POSTROUTING -s 192.168.1.0/24 -o p5p1 -j SNAT --to-source 193.x.y.130
-A POSTROUTING -s 172.16.0.0/16 -o p5p1 -j SNAT --to-source 193.x.y.130
COMMIT

With F19 install (no updates) it is the same with NM or with network
service.

The problems:
1) Why "route" shows iface=p4p1, p5p1 instead enp4s0, enp5s0 ?
2) Why "ifconfig" does show only the IPADDR0 without aliases?
3) All is working as expected when 192.168.1.73 is on-line. If ...73 not
on-line, the address 193.x.y.162 is assigned to the the server, it
responds to "ping 193.x.y.162" but it should be unreachable (or
something equivalent) because 192.168.1.73 is off.
Similar for 193.x.y.163 .

After updating aujour:

The external network is not reachable anymore but the internal network
is ok if NM is enabled and working.
This setup does not work with network service anymore.
Any advice how to fix (not downgrade-ing?)?

https://bugzilla.redhat.com/show_bug.cgi?id=980785

C. Sava