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

    BUG? Sloppy State not working on actual snapshot with WAN Failover Group

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    1 Posts 1 Posters 1.1k Views
    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.
    • R
      Reiner030
      last edited by

      Hi,

      we have 2 fw / gw pairs with iBGP full mesh routing on the gateway with WLAN bridge between them.
      (1st building: GW 1/2/3;
      2nd building: GW 254/253/252 of an /24 network).

      Yesterday I've tested our first building; fw1/2 have routing group .1/.254 to gateways:
          2x internal pfSense => 2.0.1,
          2x external pfSense => 2.1-BETA1 from last week
      and we have here with Sloppy State problems with our limiters on stable 2.0.1.
      => http://forum.pfsense.org/index.php/topic,59415.0.html

      Today I've tested our second building; fw1/2 have routing group .254/.1 to gateways:
          2x internal pfSense /  2x external pfSense
          => 2.1-BETA1 (amd64) built on Wed Feb 27 04:47:52 EST 201
      and the activated sloppy state did not work as on our 2.0.1 firewalls (even with no limiter actually defined).

      I always lost connection when gateway failover is done; after fallback I got my connect back if session didn't run into timeout.
      If failover is active I can make a new connection without problems/right IPs (which is lost when fallback is made).

      I think that' also a bug because the definition on both fw pairs (2.0.1 / 2.1-BETA1) are equal.

      Bests

      Reiner

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.