Traffic going to eth1 is goin

[Ugo Bellavance]

Broekman, Maarten a écrit :
>>  -----Original Message-----
>>  From: redhat-list-bounces at redhat.com 
>>  [mailto:redhat-list-bounces at redhat.com] On Behalf Of Michael Simpson
>>  Sent: Thursday, January 15, 2009 8:49 AM
>>  To: General Red Hat Linux discussion list
>>  Subject: Re: Traffic going to eth1 is goin
>>  
>>  On 1/13/09, Ugo Bellavance <ugob at lubik.ca> wrote:
>>  > Hi,
>>  >
>>  > I'm scratching my head on this one...
>>  >
>>  > I've configured a server with 2 network interfaces, eth0 
>>  and eth1.  eth0 =
>>  > 192.168.2.211 and eth1 = 192.168.2.212.  eth1 seemed to 
>>  work properly, but
>>  > whenever I open a connection to 192.168.2.212, I see the 
>>  traffic on eth0.
>>  
>>  you can't use 2 interfaces on the same subnet without bonding
>>  you used to be able to years ago but it doesn't work now
>>  note your default route
>>  
>>  mike
> 
> That's not strictly true.  You can use as many interfaces on the same
> subnet as you want and traffic to the IP addresses on those interfaces
> will come in initially on that interface, but then the local routing
> rules will force the traffic out the default route, which would appear
> to be eth0.  You can change that behavior by setting up iptables rules
> that force the traffic over different interfaces depending on the source
> / destination of the traffic.

Or use those 2 lines at the bottom of sysctl.conf and run sysctl -p

net.ipv4.conf.all.arp_ignore=2
net.ipv4.conf.all.arp_announce=1

I haven't found exactly what they mean, but I tested it and it works.

Regards,

Ugo