[lug] forcing certain services to use eth1 instead of eth0

[Hugh Brown]

> I am all for making things simpler.  The eth1 is a seperate IP but on the same 
> network.  However, it is a new connection.  Perhaps I just need to clear the 
> routing table?
> 
> -Michael

I think you'll need to use the iproute2, assuming that the applications
can't be told which ip to respond from.  For example, in working with
DNS (ala BIND), I had told the server to listen on a specific IP, and
told the slaves to only allow zone-updates from that same IP.  The
master kept on sending the notify's on the wrong interface until I added
"notify-source <dns ip>;"

So DNS can be told which port to listen on/respond from.  I would be
surprised if you couldn't get sendmail to do the same.  If imap is being
run out of xinetd, you can tell it which interface to listen on.

Another thought is whether or not the LISTEN line from netstat shows
that NFS/mail are listening on 0.0.0.0 or on the specific IPs.  If they
are listening on all interfaces, I'd adjust the config to only listen on
the appropriate ones.

Hugh