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

Cluster / Failover - doesn't work correctly

Scheduled Pinned Locked Moved 1.2.1-RC Snapshot Feedback and Problems-RETIRED
8 Posts 6 Posters 3.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.
  • K
    KoalaTNR
    last edited by Jul 31, 2008, 1:00 PM Jul 31, 2008, 12:34 PM

    Hello,

    Problem 1

    If I delete an alias on master firewall then the alias will not deleted on backup firewall. The sync doesn't work correctly.

    Tested with

    PFSense 1.2.1 Beta Snapshot 20080729-0437
    PFSense 1.2 Release

    Problem 2

    If I add an CARP IP on master firewall the IP will synced to backup firewall. On backup firewall is an manually "stop" and "start" of CARP needed.
    If I don't manually restart CARP on backup firewall then the backup firewall doesn't set the new CARP IP in backup mode and doesn't work for this
    IP.
    … see attached image

    Tested with
    PFSense 1.2.1 Beta Snapshot 20080729-0437
    PFSense 1.2 Release

    Greetings
    Thomas
    carp_ip.jpg
    carp_ip.jpg_thumb

    1 Reply Last reply Reply Quote 0
    • S
      sullrich
      last edited by Jul 31, 2008, 11:19 PM

      It ABSOLUTELY works on 1.2.  I am leaning toward PEBKC problems.

      1 Reply Last reply Reply Quote 0
      • K
        KoalaTNR
        last edited by Aug 18, 2008, 7:48 AM

        It doesn't work !!! I've tested today with latest snapshot.

        1 Reply Last reply Reply Quote 0
        • G
          GruensFroeschli
          last edited by Aug 18, 2008, 8:13 AM

          1.2  =/=  1.2.1

          It definitly works on 1.2
          I just set that up yesterday and had no issues.

          We do what we must, because we can.

          Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

          1 Reply Last reply Reply Quote 0
          • N
            NickC
            last edited by Aug 18, 2008, 12:20 PM

            1.2_RELEASE:

            if you can't get it going on 1.2 you've probably got a config problem.
            
            1.2.1 RC1:
            ~~~~~~~
            About a week ago I tried to get the sync going here and gave up. The master of the pair would show that the message that it had failed to login as admin on the slave device. As far as I could tell I had set everything as I would on a 1.2 pair. The rule to allow all on the sync interface was in place.
            This maybe a HTTPS login issue that was preventing the connection for sync. At that stage I could not create certificates (can we do that now?) so I copied the certificate/key from a working 1.2 onto both of the 1.2.1 firewalls. No go, I gave up.
            So has anybody got the 1.2.1 rc1 synching happily? If so I'll have another go.
            1 Reply Last reply Reply Quote 0
            • U
              UnderCover
              last edited by Aug 18, 2008, 1:10 PM

              heres my build

              1.2.1-RC1
              built on Sun Aug 17 23:30:22 EDT 2008

              here is the error i get:

              php: : New alert found: A communications error occured while attempting XMLRPC sync with username admin http://10.1.0.2:80.

              i am sure i typed in the right password for carp and the username was left default (admin)

              1 Reply Last reply Reply Quote 0
              • N
                NickC
                last edited by Aug 18, 2008, 2:03 PM

                @UnderCover:

                1.2.1-RC1
                built on Sun Aug 17 23:30:22 EDT 2008
                …
                php: : New alert found: A communications error occured while attempting XMLRPC sync with username admin http://10.1.0.2:80.

                That's what I was getting. My message was "https://…:443" but I guess if you've not configured a certificate it will try port 80.
                Multiple password tries etc... No joy.

                1 Reply Last reply Reply Quote 0
                • H
                  heiko
                  last edited by Aug 18, 2008, 3:18 PM

                  I have opened a ticket on 2008/08/07…..

                  http://cvstrac.pfsense.com/tktview?tn=1797,33

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                    This community forum collects and processes your personal information.
                    consent.not_received