Thats most likely my fault as I added the Sync code. :)

Could we simply HUP slbd on filter reload?

Thanks for all your support guys. I'll stick to my proposed solution which i'm happy to use. I am very impressed by pfSense, and it's my absolute prefered firewall, and i have tested a few. Thank you very much.

//Eskild

@sullrich:

Yes, go ahead and email me the information.

You got mail… :)

/jan

Finally… after testing on three motherboard, I can do ping and port forwarding from external to internal machine.
The main problem is in the default gateway of the internal machine. I forgot to add additional gw in the server routing table.  ;D ;D ;D

I will switch to pfSense immediately... thanks guys... ;) ;) ;)

You can do what you want with it.  The point is to not ask for help when doing things beyond the scope of what we offer support for.

The Bad Gateway messages are cosmetic and they should be there no matter which IP you are using. They appear always when a CARP IP is brought up.

Wouldn't this be the same problem you run into when you try to impose CARP on a set of bridged interfaces?  Basically the deal is that CARP and proxyarp (or bridging) don't play nicely together.

@kikawala:

I did not try 0.94.10, but I did not have any problems with 0.94.12

Known problem, colin is working on configuration sync.