And because you are using VPN server on 127.0.0.1 / any listening port you want ( TCP ) it is no problem to come on wan on 443 TCP ( on any Virtual IP ) and forward to 127.0.0.1 / listening port. ( set on NAT )

This how I configured my server and depend of country/users IP I also come on other ports (443, 4343, 43434… ) that are forwarded to the same server on 127.0.0.1/43434 TCP

Can you try a 2.3.1 snapshot on one of those HA pairs? There was a fix or two for XMLRPC last week or so, would be worth trying out.

@Derelict:

So for the 1:1 NAT entry Single host is selected for Internal IP?

All of the netmasks on all the CARP VIPs on your L3 circuit should be /28. Not that it's causing this problem.

Enabling that 1:1 NAT should not stop any traffic.

How about a screen shot of the 1:1 NAT edit screen?

Ah, good eye on the /28 CARP IPs. Although, I'm attempting to reach an IP on the WAN_COX circuit (WAN_L3 isn't connected yet).

Initially I was thinking that it was an incorrect outbound NAT rule, however without the 1:1 rule enabled, the device at 192.168.4.225 has no problem reaching the internet.

Screenshot of the 1:1 edit is below.

pfsense-1-1edit.png
pfsense-1-1edit.png_thumb

@awebster:

I guess this is a bug, because ADVBASE, and SKEW should not be overwritten on sync.

No, you need those to match.

Ok, well this was quick. Fixed my own problem. Had /32 masks on my Virtual IP on my master.  Sorry for the fire drill. Thought I would leave this here in case someone else made a bonehead mistake like that.  I did know to use the interface mask, I just overlooked it until now.

Maintenance mode just bumps the skew to 254. That means it's backup status only if it sees advertisements from a lower skew/higher priority. Absent that, it's still master.

I'm guessing in that case the ones that don't go to backup status are on one particular interface. Likely CARP advertisements don't make it from secondary to primary on that interface for some reason. Most always network-related, either no connectivity between them, or multicast not making it in that direction.

Hi everybody,
I've just upgraded to pfSense 2.3, but I still have the same issue.
Any idea?
Thank you again.

you know that pointing to a wiki is not going to help….

Anyway to the question

Maybe your looking at multi WAN? meaning that the WAN has a diferent gateway from each other ex: 181.xx.xx.114/29 with gateway of 181.xx.xx.113 and lets say you have another lSP 201.xx.xx.21/29 with gateway of 201.xx.xx.222 meaning its called multi WAN with fail over

But if you have one lSP 181.xx.xx.114/29 with gateway of 181.xx.xx.113 but thy give you another ip of 181.xx.xx.117 you need to add a Virtual IP (VIP) then create NAT rules

Hello,
Thank you for your reply.

Therefore, the following configuration is normally possible ?

CARP VIP IP interface : 192.168.1.249/24
STACK CARP IP ALIAS VIP interface :  192.168.2.249/24

Thank you again for your help.
Soulearth

Hello all,

I'd also like to know if this issue is still present in pfSense 2.2.6. Anyone using such configuration ?

Regards,

Régis

The sync address is just the IP of a pfSense Box, which gets the configuration settings. This can be slave or master or any box else.
If you intend to obvert sync direction, first delete the sync IP from the master than add the new one to the slave.

@ewuewu:

What I want to obtain is:

LAN addresses should not be translated AND sould leave the pfsense via the WAN CARP address

Packet can't leave pfSense "via the WAN CARP address". That is just a virtual IP address, nothing physical. Packets may leave pfSense via an interface or can be routed to a gateway. They just have a source and a destination address, and these can be translated or not.