Inlab Networks : Software : BalanceNG : Examples : Example 16
BalanceNG
About/Features
Datasheet
References
Download
Documentation
Examples
   - Example 1
   - Example 2
   - Example 3
   - Example 4
   - Example 5
   - Example 6
   - Example 7
   - Example 8
   - Example 9
   - Example 10
   - Example 11
   - Example 12
   - Example 13
   - Example 14
   - Example 15
   - Example 16
   - Example 17
   - Example 18
   - Example 4-1
FAQ
Tips+Tricks
Configs
Pricing+Order
License Shop
Key Factory
Support
Change History
Benchmarks
PartnerNetwork
OEM Systems
BNG V4 FRs
RBridge
Balance
Inlab-Scheme
 
BalanceNG - The Software Load Balancer
BalanceNG®

The Software Load Balancer and Embeddable ADC

10 Years BalanceNG

BalanceNG certified system
Thomas-Krenn LoadBalancer
certified OEM Load-Balancers

 

IPv4 Server Load-Balancing in SNAT Proxy mode

SNAT (Source-NAT) has been implemented in the SLB module of BalanceNG V3 for IPv4 and IPv6, introducing the new configuration command "server N proxy enable".

Proxy SNAT state replication from the VRRP master to the VRRP backup is handled automatically.

The following configuration file example shows the application of the new "server N proxy enable" directive (requires no target server configuration and network changes):

The Configuration File (only Master shown)

//        configuration taken Tue Nov 16 15:23:55 2010
//        BalanceNG 3.190 (created 2010/11/17)
modules   vrrp,arp,ping,hc,master,slb
interface 1 {
          name eth0
}
register  interface 1
enable    interface 1
vrrp      {
          vrid 33
          priority 200
          network 1
}
network   1 {
          addr 172.17.2.0
          mask 255.255.255.0
          real 172.17.2.55
          virt 172.17.2.56
          interface 1
}
register  network 1
enable    network 1
server    1 {
          ipaddr 172.17.2.58
          port 80
          protocol tcp
          proxy enable
          targets 1,2
}
register  server 1
enable    server 1
target    1 {
          ipaddr 172.17.2.30
          port 80
          protocol tcp
          tcpopen 80,3,10
}
target    2 {
          ipaddr 172.17.2.31
          port 80
          protocol tcp
          tcpopen 80,3,10
}
register  targets 1,2
enable    targets 1,2
//        end of configuration

Please contact us in case of any questions, errors or suggestions at info@inlab.de.


Copyright © 1991-2016,2017 by Inlab Networks GmbH, All Rights Reserved - Impressum - Widerrufsrecht - Sitemap - Internal