|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: [2] how to bind smtp client to specific address?
From: Michael Ju. Tokarev (mjt
tls.msk.ru)Date: Thu Mar 30 2000 - 09:13:13 CST
- Next message: Vivek Khera: "Re: How to stop this spam"
- Previous message: Louis-David Mitterrand: "Re: temporary relaying of a domain"
- In reply to: Mailing List Account: "Re: [2] how to bind smtp client to specific address?"
- Next in thread: Mailing List Account: "Re: [2] how to bind smtp client to specific address?"
- Reply: Michael Ju. Tokarev: "Re: [2] how to bind smtp client to specific address?"
- Reply: Mailing List Account: "Re: [2] how to bind smtp client to specific address?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mailing List Account wrote:
>
[]
> Can someone point me to a HOW-TO or FAQ, or some kind of documentation on
> getting this done correctly? I am using Linux IP aliasing and want to get
> the outgoing connections coming from the right interface, instead of all on
> the non-aliased interface as they are now....
>
Not a faq/howto, but see iproute2 package's "ip" command.
(it is avalable at redhat as iproute-xxx-yyy.rpm, and also
see ftp://ftp.inr.ac.ru/ip-routing/ (main site, slow), or
mirrors (see Liviu Daia's message on thread about list of
mirrors).
Here is output of "ip route" on one of my machines (very multihomed :) .
Note the "src xxx.yyy.zzz.nnn" lines. When connection is made from
this machine, routing mechanism chooses route entry to use, and
uses "src ip.add.re.ss" for source address, if set up.
Read the docs about ip command (in LaTeX), esp. for "ip route".
Note also that this command (ip) can be used instead of ifconfig,
route and some other, and gives you more control.
$ ip route
212.158.168.7 dev eth0 scope link src 212.158.168.7
212.158.168.6 dev eth0 scope link
192.168.1.5 dev eth0 scope link
192.168.5.6 dev eth1 scope link
212.158.168.250 dev eth1 scope link src 212.158.168.253
212.24.52.233 dev eth2 scope link
212.158.168.253 dev eth3 scope link
212.158.168.252/30 dev eth3 proto kernel scope link src 212.158.168.253
212.24.52.232/29 dev eth2 proto kernel scope link src 212.24.52.233
212.158.168.0/28 dev eth0 proto kernel scope link src 212.158.168.7
192.168.3.0/24 dev eth1 proto kernel scope link src 192.168.3.1
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.5
127.0.0.0/8 dev lo scope link
default via 212.158.168.254 dev eth3
(on eth3, there is only one address (212.158.168.253), so it is used)
$_
- Next message: Vivek Khera: "Re: How to stop this spam"
- Previous message: Louis-David Mitterrand: "Re: temporary relaying of a domain"
- In reply to: Mailing List Account: "Re: [2] how to bind smtp client to specific address?"
- Next in thread: Mailing List Account: "Re: [2] how to bind smtp client to specific address?"
- Reply: Michael Ju. Tokarev: "Re: [2] how to bind smtp client to specific address?"
- Reply: Mailing List Account: "Re: [2] how to bind smtp client to specific address?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]