Before I go through the process of trying to hack into the sync
backend on pfsense, I just wanted to put this out there one last time...
Anybody with inside info willing to shed some light on the future
plans for this issue?
Cheers,
Ian
On Oct 31, 2008, at 3:11 PM, Ian Levesque wrote:
Just found the bug report: http://cvstrac.pfsense.org/tktview?tn=1747,33
Still curious about potential workarounds and the projected release
for a fix.
Cheers,
Ian
On Oct 31, 2008, at 2:56 PM, Ian Levesque wrote:
Hi all -
I have two pfSense installations, successfully using carp + XMLRPC
sync to provide failover routing, firewall, DNS and DHCP services
to my network of a few hundred workstations. Everything has been
working beautifully, except for one thing: the dhcp configuration
isn't synced between the boxen. This poses two problems: 1) because
we're running redundant dhcp, unless both dhcp servers are using
the same config we have the possibility of inconsistent dhcp
results on our LAN and 2) if the primary dhcp server does go down,
there's a risk that some clients whose lease time expired may
forfeit their IP address.
Before I spend the time trying to figure out a reliable way to sync
the config, has anybody already successfully found a workaround to
this deficiency? Also, does anybody know if this will be fixed in
1.2.1?
Cheers,
Ian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Commercial support available - https://portal.pfsense.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Commercial support available - https://portal.pfsense.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Commercial support available - https://portal.pfsense.org
