Hi all. First post, so be gentle :-)

I have a webserver setup, where i need the server to have multiple eht:0 aliases in order to do some SSL-vhosting and other stuff.

The servers eh0 is set up in /etc/network/interfaces (its an Ubuntu)
And i have added the eth aliases with : ifconfig eth0:1 123.231.213.123 up command.

This works great, i can use the additional IP´s for the SSL-vhosts, and all is good.

My problem now is that while the server itself has 1 IP, (and approx 20 IP on alias interfaces) it uses random (i think) IP´s when it is to connect to other servers. E.g the main problem is that if a Vhost on the server sends out an email, the server uses a wrong IP in the headers. Thus making it seem like the email is coming from another IP than then on the Vhost it´s currently residing.

Currently, when the server connects to its smarthost in order to deliver emails, It connects from the IP that is bound to the eth0:0 interface, and not the IP bound to eth0 which is desired.

The question now is how do I sort out the IP´s so that all connections the server makes as a client, will use the first (Eth0) IP ?

And all the extra IP-adresses will only be used as "server addresses" not to make client requests.

Does it even make sense ?

Any help is greatly appreciated.

cheer
/Husaren

I think I understand what you want.

You want all emailS sent from the server to appear to come from the ip bound to eth0. That would be a configuration of your mail server software on the server. Probably sendmail, postfix, or exim.

As for other client connections I'm not sure.


Btw I assume your outgoing emails are sent from the server not some smtp client In a vhosts code (like a php script connecting to another server). I don't have a clue for other outbound connections.

That is exactly what I want.

Well. All the Vhosts use PHP´s mail() which redirect the mail to localhost. Here Courer-mta accepts the mails and send them to a dedicated outbound SMTP-server. It is in the tranfer that the server connects to the dedi outbound SMTP as a client, and from another IP than the one bound to eth0.

Im not sure it helps to have Courier-mta listen on only a specific interface as im pretty confident this problem is regarding the inner workings of linux-networking.

In short, it would be nice to be able give som sort of prio to each of the eth interfaces.

Or be able to define that only eth0 should be used for outbound connections.