On 8/16/2016 3:53 AM, lejeczek wrote:
$ ping 10.5.6.17 -I p3p3
PING 10.5.6.17 (10.5.6.17) from 172.25.12.202 p3p3: 56(84) bytes of data.
and nothing, ping waits and no reply, Ctrl+C
with such a simple setup rules based routing should not be involved,
kernel should figure it out, right?
you specifically said to send that packet to an interface on the wrong
network, of course, its not going to get through, unless there's an
external route from that network to the destination. I'm presuming
there's a router somewhere else between your 192.168.2.0/24 network and
10.5.6.17, that would enable those ping -I em1/2 commands to work.
note that the recipient of the ping needs to have a route to get back to
the source, too.
--
john r pierce, recycling bits in santa cruz
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
