I guess the biggest confusion is that fact it doesn't specify you will
need to add a static route to your other gateways so it knows to pass
traffic destined for the isolated network to the LB.
In a L4xNAT config, does the LB NAT only traffic requested externally
or will it NAT all traffic from the real servers?



On Sun, Jul 28, 2013 at 5:15 PM, Laura Garcia <[email protected]> wrote:
> Hi, I reply you below
>
>
> On Fri, Jul 26, 2013 at 3:38 PM, Jack Scagnetti <[email protected]> wrote:
>>
>> Then I find the quick start guide very confusing. It says it needs an
>> isolated network for it to work which would imply some sort of
>> masquerading.
>
>
> No, it does not imply to do any masquerading and the guide is not referring
> to NAT in any way for the load balancer.
> The NAT should be done by the backends in the uplink farms case, which are
> the routers or firewalls with direct internet access with public IP.
> Also, the guide is not saying anything about the public IP address in the
> load balancer and is absolutely a bad idea.
>
>
>>
>> The only way it would ever be able to work the way you describe with
>> the datalink setting is if you had your own IP space and a ASN to
>> allow routing across 2 different providers.
>>
>
> The guide is just describing the way to do load balancing between uplink
> lines for which we've to create 3 different subnets through 3 different
> network interfaces in the load balancer and creating a balancer routing
> gateway in it. Also, maybe some rules in the backends or firewalls should be
> included to detect the client subnet as a local network.
>
> Please, let me know which part of the guide is confusing for you.
>
> Regards.
>
>>
>>
>>
>>
>>
>> On Fri, Jul 26, 2013 at 2:40 AM, Laura Garcia <[email protected]> wrote:
>> > Hi Jack,
>> >
>> > The uplink farm do not use NAT, it just transform the load balancer in a
>> > GW
>> > with load balanced routes, so the source IP is not modified. If you need
>> > to
>> > do NAT then you've to try the L4xNAT farms.
>> >
>> > Regards.
>> >
>> >
>> > On Thu, Jul 25, 2013 at 10:35 PM, Jack Scagnetti <[email protected]>
>> > wrote:
>> >>
>> >> I’ve been following the uplink quick start guide (
>> >>
>> >>
>> >> http://www.zenloadbalancer.org/web/index.php?page=quick-start-guide-for-uplinks-load-balancing-with-zen-load-balancer
>> >> ) and I seem to be having an issue with how NAT is working.
>> >>
>> >>
>> >> Simple layout:
>> >>
>> >> 10.4.10.1 (GW)
>> >> |
>> >> |
>> >> 10.4.10.91 (eth0)
>> >> [ZLB]
>> >> 192.168.100.91 (eth2)
>> >> |
>> >> |
>> >> 192.168.100.105
>> >>
>> >>
>> >> The NAT'ed VM  can ping both sides of the LB but cannot ping the GW or
>> >> beyond.
>> >> I tried a SSH attempt to something else on the eth0 network and it's
>> >> seeing the attempt coming from the .105 IP as if not's being
>> >> masqueraded at all.
>> >>
>> >> Is there something missing from the guide?
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> See everything from the browser to the database with AppDynamics
>> >> Get end-to-end visibility with application monitoring from AppDynamics
>> >> Isolate bottlenecks and diagnose root cause in seconds.
>> >> Start your free trial of AppDynamics Pro today!
>> >>
>> >>
>> >> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> >> _______________________________________________
>> >> Zenloadbalancer-support mailing list
>> >> [email protected]
>> >> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>> >
>> >
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > See everything from the browser to the database with AppDynamics
>> > Get end-to-end visibility with application monitoring from AppDynamics
>> > Isolate bottlenecks and diagnose root cause in seconds.
>> > Start your free trial of AppDynamics Pro today!
>> >
>> > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> > _______________________________________________
>> > Zenloadbalancer-support mailing list
>> > [email protected]
>> > https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Zenloadbalancer-support mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Zenloadbalancer-support mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Zenloadbalancer-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support

Reply via email to