Well, some more tests on this.
It's not a password problem. I've deleted everything, and start from a beta2
full install. Configured the two nodes and the first rules they were
synchronized.
Then, after I created the third VIP, the synchonization failed with Code 104:
XML error: not
Wesley K. Joyce wrote:
expensive
Indeed, but it's a requirement for some environments.
the opportunity to get certified isn't extremely unlikely, actually.
It's not very likely, but not unimaginable. There was an opportunity
for m0n0wall to get certified, completely at the cost of one
Scott Ullrich wrote:
I wouldnt even think of updating such an old version to BETA2.
Reinstall and reconfigure is your best bet.
I assume, a similar hassle is not required for BETA2- RELENG_1?
cheers,
Rainer
-
To
No
On 3/6/06, Rainer Duffner [EMAIL PROTECTED] wrote:
Scott Ullrich wrote:
I wouldnt even think of updating such an old version to BETA2.
Reinstall and reconfigure is your best bet.
I assume, a similar hassle is not required for BETA2- RELENG_1?
cheers,
Rainer
Bill Marquette wrote:
On 3/6/06, Rainer Duffner [EMAIL PROTECTED] wrote:
Scott Ullrich wrote:
I wouldnt even think of updating such an old version to BETA2.
Reinstall and reconfigure is your best bet.
I assume, a similar hassle is not required for BETA2- RELENG_1?
Add another machine as CARP member, then you can seamlessly upgrade ;-)
Holger
-Original Message-
From: Rainer Duffner [mailto:[EMAIL PROTECTED]
Sent: Monday, March 06, 2006 8:42 PM
To: support@pfsense.com
Subject: Re: [pfSense Support] Upgrade 0.84.x - BETA2?
Bill Marquette
Holger Bauer wrote:
Add another machine as CARP member, then you can seamlessly upgrade ;-)
The problem is (I described it before) that I have to protect a several
/24s with bridging and several other /24s via 1:1 NAT.
And I've got VLANs, too.
Last time I checked, nobody seemed to be
