Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    Failover Syntax Error

    Routing and Multi WAN
    3
    4
    1481
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      foof last edited by

      I've setup (what I think is) a simple failover config.  All IP's are static.  3-15-07 Snap.

      Name  Type      Servers/Gateways  Port  Monitor
      balancer  gateway      wan                            64.56.140.1
                  (failover)    opt1                            205.200.66.7

      Proto  Source  Port  Destination  Port  Gateway
      *  LAN net  *    *                *      balancer

      When the balancer is set to load balancing traffic alternates between wan and opt1 like it's supposed to.  Failover mode traffic goes out wan, so far so good. OPT1 goes offline, still Ok.  WAN goes offline and nothing is going anywhere and an alert pops up.

      php: : There were error(s) loading the rules: /tmp/rules.debug:158: syntax error pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [158]: pass in quick on $lan route-to { ( balancer ) } round-robin proto tcp from 192.168.1.0/24 to any keep state label "USER_RULE"

      All I'm trying to accomplish is everything goes over WAN unless it's offline then switch to OPT1.  Any docs I've seen combine balancing, failover and port based routing.  Nothing simple.

      1 Reply Last reply Reply Quote 0
      • S
        sullrich last edited by

        I believe this bug is known and Seth is working on a fix.

        1 Reply Last reply Reply Quote 0
        • D
          databeestje last edited by

          I believe it is fixed in all snapshots dating 21-03-2007 and later.

          1 Reply Last reply Reply Quote 0
          • F
            foof last edited by

            That would be my typical luck.  I downloaded the 03/20/2007 version.  :'(  Oh well, at least I can confirm it's fixed and working good in the 03/22/2007 version.  ;)

            1 Reply Last reply Reply Quote 0
            • First post
              Last post