We have 2 gateway on the same subnet. One is 192.168.0.3(default) and .2 The gateway .2 has access to some device that .3 doesn't. We have created the following route to have traffic of 10.10.x.x to be routed directly to 192.168.0.2.
Destination Gateway Flags Refs Use Netif Expire
default 192.168.0.3 UGS 0 3808954 re0
10.10.0.0 192.168.0.2 UGS 0 24 re0
Now the issue is everything wants to route through the .3 gateway.
traceroute to 10.10.18.118 (10.10.18.118), 64 hops max, 52 byte packets
1 192.168.0.3 (192.168.0.3) 0.536 ms 1.323 ms 0.355 ms
2 * * *
As a work around, we have created a route on the .3 gateway to forward 10.10 traffic through 192.168.0.2 gateway.
traceroute to 10.10.18.118 (10.10.18.118), 64 hops max, 52 byte packets
1 192.168.0.3 (192.168.0.3) 0.536 ms 1.323 ms 0.355 ms
2 192.168.0.2 (192.168.0.2) 0.601 ms 0.642 ms 0.636 ms
3 one.one.one.one (1.0.0.1) 20.558 ms 18.371 ms 18.127 ms
4 10.10.18.118 (10.10.18.118) 19.632 ms 21.249 ms 17.772 ms
Now this work for ping but we are having other issue that is being caused by routing the traffic through 192.168.0.3. All we are trying to do is route 10.10.0.0 directly to 192.168.0.2 without going through 192.168.0.3.
Destination Gateway Flags Refs Use Netif Expire
default 192.168.0.3 UGS 0 3808954 re0
10.10.0.0 192.168.0.2 UGS 0 24 re0
Now the issue is everything wants to route through the .3 gateway.
traceroute to 10.10.18.118 (10.10.18.118), 64 hops max, 52 byte packets
1 192.168.0.3 (192.168.0.3) 0.536 ms 1.323 ms 0.355 ms
2 * * *
As a work around, we have created a route on the .3 gateway to forward 10.10 traffic through 192.168.0.2 gateway.
traceroute to 10.10.18.118 (10.10.18.118), 64 hops max, 52 byte packets
1 192.168.0.3 (192.168.0.3) 0.536 ms 1.323 ms 0.355 ms
2 192.168.0.2 (192.168.0.2) 0.601 ms 0.642 ms 0.636 ms
3 one.one.one.one (1.0.0.1) 20.558 ms 18.371 ms 18.127 ms
4 10.10.18.118 (10.10.18.118) 19.632 ms 21.249 ms 17.772 ms
Now this work for ping but we are having other issue that is being caused by routing the traffic through 192.168.0.3. All we are trying to do is route 10.10.0.0 directly to 192.168.0.2 without going through 192.168.0.3.