Gordon Messmer wrote: 
On 05/07/2010 07:26 AM, Jussi Hirvi wrote:
  
[root@farm1 log]# ip route show
62.236.221.64/28 dev eth0  proto kernel  scope link  src 62.236.221.67
62.220.237.96/27 dev eth1  proto kernel  scope link  src 62.220.237.104
192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
169.254.0.0/16 dev eth1  scope link
default via 62.220.237.126 dev eth1
    

Yeah, so you have two interfaces on different IP networks.  When someone 
connects to 62.236.221.67, the reply packets will still head out through 
62.220.237.126 on eth1.  That router probably filters the reply packets 
since they're from a non-local IP network.

I'm not sure if there's a simpler way to do this:  When I have 
multi-homed servers I usually just use Shorewall to create two routing 
tables: one with a default route through each outbound router.  Packets 
are marked based on their source address and routed based on those marks.


that can be done with `ip route` and `ip rule` and a few iptables commands, you dont need shorewall to do it for you.  you got it exactly right, you mark sockets that are 'to' the 2nd interface to use the alternate routing table, whihc specifies the alternate default gateway.