How do I use interface binding in firmware version 1.17 ?

Interface binding on 1.17 will be done using the manual network routes with “Type” set to “Connection”.

Manual routes are used in scenarios where you have multiple subnets on the LAN segment, or you want to specify certain subnet traffic to use a specific Remote LAN, or WAN link. This feature can be configured by going to the “ADVANCED” tab on the BBNA Management Interface and clicking on the “Add” button next to the Manual Network Routes section:

The “Type” field specifies “Simple Route”, “Connection Route”, or “Advanced Route”.  “Device Type” will identify the interface/tunnel type for the traffic we are setting the route for. As an example, WAN or LAN subnets or “VLL” if the traffic is destined for a VLL tunnel. The “Destination” field specifies the destination IP address subnet to which the packets will be routed to. This can be accomplished either through a device route or through a VLL route, based on the option chosen previously.                                                   

To set interface binding, set the “Type” field to “Connection” which will expose additional configuration options, as shown below, to identify the traffic. Options include “Source IP/Subnet”, “DSCP”, “Protocol”, “Source Ports” and “Destination Ports”. You can also modify the Priority and/or the Maximum Transmission Unit (MTU) size of the traffic.

The Failover Mode is used to configure the failover action in case of primary interface failure. It has 2 modes: “sticky mode” and “available mode”. In case of a primary interface failure, the sticky mode will transfer the traffic onto the secondary interface, and when the primary line comes back up, will transfer the traffic back to the primary interface. With the “available mode”, after the primary interface recovers, the traffic that failed-over earlier will continue to use the failover interface. The newer sessions will be routed over the primary interface as usual.