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

CARP Setup working - Automatic NAT = OK; Manual NAT = Failing…

Scheduled Pinned Locked Moved HA/CARP/VIPs
2 Posts 2 Posters 2.3k 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.
  • D
    djsmiley2k
    last edited by Oct 6, 2011, 8:09 AM

    I've got a normal CARP setup which works "normally" - if i power down / kill the master router then it falls back with minimal/no loss of service however once I turn on Manual NAT so I can have the outbound source address set to the Virtual floating IP of the CARP interface and then fail over a box it goes haywire with massive (upto 50%) loss.

    When I turn on the manual outbound NAT there is 6 rules generated. These are:

    • localhost to wan

    • localhost to wan port 500 (Static)

    • pfsync to wan

    • pfsync to wan port 500 (Static)

    • lan to wan

    • lan to wan port 500 (Static)

    I've tried with removing various combinations of rules in case any were interfering, and have also tried using static ports but I still experience the loss, and am now at a total "loss" of what to do (pun not intended :/ ).
    This is running 2.0-release.

    1 Reply Last reply Reply Quote 0
    • M
      marcelloc
      last edited by Oct 14, 2011, 4:46 AM

      Wait some seconds until your switch flush mac address table.

      Also connect to your switch and see if there is any problem with mac table(full) or cpu usage.

      Treinamentos de Elite: http://sys-squad.com

      Help a community developer! ;D

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
        [[user:consent.lead]]
        [[user:consent.not_received]]