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

Syncing settings to backup server

pfBlockerNG
2
4
1.1k
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.
  • B
    blueduckdock
    last edited by Nov 16, 2016, 4:33 PM

    Might pertain to just BBCan but maybe someone else has had experience.

    I searched but didn't find a clear cut answer. The situation is:

    • I have two firewalls in CARP and am looking to sync settings from 1 to 2.
    • I set it to backup to designated backup server.
    • It does not sync properly.

    Now I did see something about the admin creds having special characters which may for some reason screw up syncing. I also tried doing it via replicated targets and that doesn't seem to work either.
    I am enabling pfblocker on both and it just does not work- get errors on 1 about not being able to sync then #2 complains about missing the aliases, etc.

    Any help is appreciated.

    1 Reply Last reply Reply Quote 0
    • B
      BBcan177 Moderator
      last edited by Nov 23, 2016, 4:49 AM

      In the pfBlockerNG XMLRPC Sync Tab, did you try "Sync to hosts defined below" option?  I think you can only use the root or admin username …

      "Experience is something you don't get until just after you need it."

      Website: http://pfBlockerNG.com
      Twitter: @BBcan177  #pfBlockerNG
      Reddit: https://www.reddit.com/r/pfBlockerNG/new/

      1 Reply Last reply Reply Quote 0
      • B
        blueduckdock
        last edited by Nov 28, 2016, 8:07 PM

        @BBcan177:

        In the pfBlockerNG XMLRPC Sync Tab, did you try "Sync to hosts defined below" option?  I think you can only use the root or admin username …

        I think I was too quick on calling for help or something just seemed up.
        I noticed errors on force updates (ie. change, then force update on 1) and I think it's because I didn't force update on 2 right away (so 1 syncs before 2 can be force updated since that still runs on cron.)

        In any case, I tested with a simple password (no special characters) and just let cron do its thing. That worked a few times and I went and changed the password to something complex and it continued to work. Failover seems fine though I didn't test it for longer than an hour (to see how cron would do) but I assume that'll be good (why wouldn't it?)

        I am going to try this on my production boxes soon enough and I'll let you know if I see any errors there.
        Thanks BBcan again. Very much appreciate the work you do on this package.

        1 Reply Last reply Reply Quote 0
        • B
          blueduckdock
          last edited by Dec 1, 2016, 3:08 PM

          Good on the prod boxes. Whatever it is- it's just on initial sync. After that I can seem to make changes, etc. without issue and just let CRON do its job.

          SOLVED. Thanks

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