Network config problem - ssh hangs/connection refused

[code.ferret]

Hello,

I have 2 subnets, A & B and a router connected to both A and B and the WAN.

I have 4 servers dual homed on subnets A and B, 2 of them are Mac OS and 2 of them are Centos 7 (1503). They are all configured to reply on the same interface that requests were received and the gateway on the B subnet is their default gateway.

The 2 Mac OS servers and one of the CentOS servers, bob, work fine in that each can ping and ssh into the others via their subnet A or B addresses.

Additionally, clients on subnet A can also access the Mac OS servers and the CentOS server, bob via their subnet A or B addresses; and the three servers can access any of the clients on subnet A.

The second CentOS server, alice, is the problem.

None of the other dual-homed servers or clients on subnet A can ping or ssh into alice using alice's subnet A address. Pings and ssh simply hang and I see no evidence of traffic at alice via tcpdump. The arp tables on the other servers and clients all show that alice's IP addresses on subnets A and B are mapped to the appropriate MAC addresses.

None of the other dual-homed servers can ping or ssh into alice using alice's subnet B address.

However, clients on subnet A are able to ping and ssh into alice by using alice's address on subnet B.

Further, alice can ping and ssh into all servers and clients via subnet A; and can ping the other three servers on subnet B, but when alice attempts to ssh into any of the servers via their subnet B addresses, alice receives "Connection refused"?!

The servers bob and alice are intended to be configured the same except of course for addresses.

I've compared the various /etc/sysconfig/network-scripts/{ifcfg-, route-, rule-}{eno1, eno2} on bob and alice and they appear to be identical except for the addresses assigned to each interface.

I've compared "ip addr", "ip route", "ip rule" between bob and alice and all look identical save for address assignments.

I have disabled SELinux and disabled the firewall on alice to remove these from consideration.

I'm befuddled regarding where the misconfiguration on alice is.

It seems to me from the evidence that there is not a hardware problem with either of alice's interfaces since I can reach each interface from the router via the subnet A and B addresses for alice and clients on subnet A can reach alice via the subnet B address.

It doesn't seem to be a problem in the router since all other combinations of communication are working.

Further, the connection refused doesn't seem to be a configuration issue with the other three servers via subnet B since they are all able to connect to each other on subnet B. From looking at tcpdump when alice tries to connect to the other three servers on subnet B, I don't see any packets arriving at the B interfaces on the other three servers.

I would really appreciate any ideas about where to probe to try and resolve this issue.

Thank you,
Chris