Inlab Networks : BalanceNG: Example 2 (Dual Legged Routing Mode)
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 LES LoadBalancer
certified OEM Load-Balancers

 

Dual Legged Routing Mode Example

1. The Network Setup


Figure 1: Network configuration for Dual Legged Routing Mode

The default gateway on the two targets needs to point to 10.1.1.254, which is represented by BalanceNG.

2. The Configuration Files

2.1 Node A

//        configuration taken Fri Apr 26 19:03:02 2013
//        BalanceNG 3.446 (created 2013/04/26)
modules   vrrp,arp,ping,hc,master,slb,tnat,nat,rt
set       ipforwarding 1
interface 1 {
          name eth0
          access raw
}         
interface 2 {
          name eth1
          access raw
}         
register  interfaces 1,2
enable    interface 1,2
vrrp      {
          vrid 71
          priority 200
          network 1
}         
network   1 {
          name "DMZ Network"
          addr 172.16.1.0
          mask 255.255.255.0
          real 172.16.1.251
          virt 172.16.1.253
          nat outside
          interface 1
}         
network   2 {
          name "LN Network"
          addr 10.1.1.0
          mask 255.255.255.0
          real 10.1.1.252
          virt 10.1.1.254
          nat inside
          interface 2
}         
register  networks 1,2
enable    networks 1,2
gateway   {
          ipaddr 172.16.1.254
          ping 3,8
}         
server    1 {
          ipaddr 172.16.1.10
          port 80
          protocol tcp
          targets 1,2
}         
register  server 1
enable    server 1
target    1 {
          ipaddr 10.1.1.1
          port 80
          protocol tcp
          tcpopen 80,3,10
}         
target    2 {
          ipaddr 10.1.1.2
          port 80
          protocol tcp
          tcpopen 80,2,10
}         
register  targets 1,2
enable    targets 1,2
//        end of configuration

2.2 Node B

//        configuration taken Fri Apr 26 14:20:07 2013
//        BalanceNG 3.446 (created 2013/04/26)
modules   vrrp,arp,ping,hc,master,slb,tnat,nat,rt
set       ipforwarding 1
interface 1 {
          name eth0
          access raw
}         
interface 2 {
          name eth1
          access raw
}         
register  interface 1,2
enable    interface 1,2
vrrp      {
          vrid 71
          priority 200
          network 1
}
network   1 {
          name "DMZ Network"
          addr 172.16.1.0
          mask 255.255.255.0
          real 172.16.1.252
          virt 172.16.1.253
          nat outside
          interface 1
}         
network   2 {
          name "LN Network"
          addr 10.1.1.0
          mask 255.255.255.0
          real 10.1.1.253
          virt 10.1.1.254
          nat inside
          interface 2
}         
register  networks 1,2
enable    networks 1,2
gateway   {
          ipaddr 172.16.1.254
          ping 3,8
}         
server    1 {
          ipaddr 172.16.1.10
          port 80
          protocol tcp
          targets 1,2
}         
register  server 1
enable    server 1
target    1 {
          ipaddr 10.1.1.1
          port 80
          protocol tcp
          tcpopen 80,3,10
}         
target    2 {
          ipaddr 10.1.1.2
          port 80
          protocol tcp
          tcpopen 80,2,10
}         
register  targets 1,2
enable    targets 1,2
//        end of configuration

3. Things to Test:

  • You should be able to ping the default gateway 10.1.1.254 from the targets.
  • You should be able to ping the virtual web server 172.16.1.10 from the router.
  • Clients from the Internet are able to initiate TCP connection to port 80 on the virtual Web Server 172.16.1.10 (now being represented by BalanceNG).
  • "show servers" and "show targets" in BalanceNG interactive mode should show everything up and operating.

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


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