marcin.giedz at arise
Nov 17, 2009, 11:41 PM
Post #11 of 13
(1612 views)
Permalink
|
Alexis Rosen pisze:
Hi Alex,
I really appreciate your help and yes now I know this is wrong list.
Anyway to close this subject I'd like to ask you why do you see
obstacles for not using 'lo' to stick IPs from advertised network? This
is quite common in cisco or bgp generally, isn't it? If 'lo' is not good
enough should I use physical interface for my PA network?
Many thanks,
Marcin
> On Nov 15, 2009, at 9:17 AM, Marcin Giedz wrote:
>> but postfix stays in my case on the server which is in LAN
>> 192.168.30.0/24 ?
>>
>> so once again:
>>
>> on router:
>> 1) ISP1: 1.1.1.1 on eth0
>> 2) IPS2: 2.2.2.2 on eth1
>> 3) on IPS1 and IPS2 BGP is created
>> 4) IP of my advertised network : 3.3.3.1 on lo
>> 5) my LAN: 192.168.30.0/24 on eth3, in this LAN SMTP server exist
>> 192.168.30.5
>>
>> 6) from outside (Internet) 'dig mydomain.com MX' gives 3.3.3.1
>> 7) during sending emails from my SMTP server connection on port 25 is
>> established using source IP address of ISP1 or ISP2 depends on which one
>> is default GW for particular network. This ends up with message from
>> external SMTP server saying: "your IP ISP1(1.1.1.1)/ISP2(2.2.2.2)
>> doesn't correspond to IP from your mydomain.com (3.3.3.1)"
>
> A few thoughts on this:
>
> 1) This is a NAT issue. You haven't configured it correctly. So a
> previous poster's suggestion to read the docs on your NAT software
> (natd or whatever) is the right first step. Your problem is that you
> are telling your NAT software on your router to rewrite all your
> outbound traffic as coming from your router. It's doing that, and it's
> choosing as a source IP address whatever interface it's sending the
> traffic from. This is what you would expect, by default. You should be
> able to have it use your loopback address instead, with the
> appropriate rules.
>
> 2) What you're doing may be the wrong idea. Consider not using your
> loopback address as the MX. (Similarly, don't use it for other servers
> either.) Instead select another address inside your netblock (perhaps
> 3.3.3.2, using your example netblock) for your SMTP server, and set up
> your NAT rules to rewrite traffic from your SMTP server as coming from
> there (and do the opposite for inbound traffic). That sort of static
> 1-to-1 NAT is a lot simpler conceptually and may help you get things
> going. (Note that your current design isn't inherently wrong or
> broken, and I have many networks set up that way myself, but if you've
> got a whole /24 and you're having trouble, it's probably more complex
> that you need it to be.)
>
> 3) This is the wrong list. Please take this to a networking list for
> the OS you're using - you're likely to get more, better, more specific
> help there.
>
> /a
_______________________________________________
Quagga-users mailing list
Quagga-users [at] lists
http://lists.quagga.net/mailman/listinfo/quagga-users
|
