Major Netbalancer Issue

Home Page Forums Network Management ZeroShell Major Netbalancer Issue

This topic contains 0 replies, has 0 voices, and was last updated by  Smokeshow 10 years, 1 month ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #41518

    Smokeshow
    Member

    I have a Zeroshell box running for a client with 2 WAN interfaces setup on the same /24 subnet running off of 2 seperate DSL lines running throught netbalancer in Balancing & Failover Mode.

    I assigned the IP’s using a startup script:

    # Startup Script
    ifcfg ETH00 add 12.34.16.31/24
    ifcfg ETH01 add 12.34.16.32/24

    My ISP just called me saying that there are some major issues regarding our connections. What is happening is either interface will respond to an ARP request on either of the assigned IP’s. Here is a very short log exert that I was sent: (I’ve edited the macs & IP’s for privacy)

    Mar  6 10:04:00 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:00 hydra arpwatch: flip flop 12.34.16.31 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:01 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:04 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:05 hydra arpwatch: flip flop 12.34.16.31 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:06 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:07 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:07 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:10 hydra arpwatch: flip flop 12.34.16.31 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:11 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:15 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:15 hydra arpwatch: flip flop 12.34.16.31 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:18 hydra arpwatch: flip flop 12.34.16.31 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:19 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:20 hydra arpwatch: flip flop 12.34.16.31 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:22 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:22 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:24 hydra arpwatch: flip flop 12.34.16.31 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:27 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:28 hydra arpwatch: flip flop 12.34.16.31 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:28 hydra arpwatch: flip flop 12.34.16.31 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:30 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:31 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:32 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:34 hydra arpwatch: flip flop 12.34.16.31 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:34 hydra arpwatch: flip flop 12.34.16.31 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:37 hydra arpwatch: flip flop 12.34.16.31 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:37 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:38 hydra arpwatch: flip flop 12.34.16.31 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:38 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:40 hydra arpwatch: flip flop 12.34.16.31 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:40 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:40 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:41 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:41 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:41 hydra arpwatch: flip flop 12.34.16.31 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:41 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:41 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:41 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:43 hydra arpwatch: flip flop 12.34.16.31 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:43 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:43 hydra arpwatch: flip flop 12.34.16.31 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:45 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:47 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:49 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:50 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)
    Mar 6 10:04:55 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:65:8f (0:0:0:e4:6d:3f)
    Mar 6 10:04:55 hydra arpwatch: flip flop 12.34.16.32 0:0:0:e4:6d:3f (0:0:0:e4:65:8f)

    My temporary fix was to order 2 /30 subnets to give the two interfaces some more separation.
    Hopefully there is a solution to this issue without having to switch IP’s.

    Any help would be very much appreciated.

    #47707

    olivier1010
    Member

    I had a similar problem, when using a failover bonding, sending packets to a bridge at the other side through two different tunnels, each one using a different provider wan link.

    the bridge at the other side was sending back arp traffic sent by the bonding dead link arp detection, causing unuseful traffic on the spare link.

    A solution is to use IP target failover detection instead of ARP, this is implemented in the bonding driver, but the switching response time is in the second range instead of millisecond.

    Using the bonding driver in arp detection mode is a must for VoIP tunnels, it does allow to switch a dead wan link in about 40 ms, almost not noticeable on a phone call.

    There is a setting in the bonding driver that give the possibility to setup the arp time between each request.

    It would be nice to have access to those bonding driver settings in the GUI, as well as giving access to other bonding modes (there are about 5 modes if i remember correctly).

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.