Re: Keepalived and NAT loopback,.

Pat Suwalski <[email protected]>
Newsgroups gmane.linux.keepalived.devel
Message-ID <[email protected]>
This seems to be an amazingly difficult problem to solve, and I can't 
for the life of me figure out why it would be so.

--Pat

On 13-08-14 10:38 AM, Pat Suwalski wrote:
> On 13-08-13 06:51 PM, Paul Robert Marino wrote:
>> I'm assuming you have 3 public ips with a 1 to 1 two way (Source and
>> destination) static nat on two of them to two internal hosts with
>> private IPs
>
> This part is correct. It's SNAT/DNAT rules. There are 3 public IPs.
>
>> The third public IP is a VIP controlled as a VRRP instance in
>> keepalived and used by the load ballancer instance ballancing against
>> the other two public IPs
>> is this correct?
>
> I think it's correct, but I'm not exactly clear on your description.
> Firewall A has 1 IP, Firewall B has 1 IP, and the failover VIP is 1 IP
> shared between them.
>
> --Pat
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Keepalived-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/keepalived-devel
>


------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.