On Thu, Apr 9, 2009 at 7:00 PM, Dimitri Rodis
wrote:
> Good deal. I'll go to a later snapshot then.
>
> Are upgrades between snapshots on embedded working at the moment, or should
> I just reflash?
>
Yeah you got hit with the xmlparse.inc issue that was in snapshots for
a couple days. I know CARP
Sent: Thursday, April 09, 2009 11:37 AM
To: support@pfsense.com
Subject: Re: [pfSense Support] CARP Bug in 1.2.3
On Thu, Apr 9, 2009 at 1:57 PM, Dimitri Rodis
wrote:
> The snapshot I'm using is dated April 1.. that's a couple of days after
the
> hackathon, I believe. Any idea when the x
On Thu, Apr 9, 2009 at 1:57 PM, Dimitri Rodis
wrote:
> The snapshot I'm using is dated April 1.. that's a couple of days after the
> hackathon, I believe. Any idea when the xmlparse.inc from HEAD was removed?
You where affected then. It was removed for causing various problems
such as these.
S
@gmail.com]
Sent: Thursday, April 09, 2009 10:17 AM
To: support@pfsense.com
Subject: Re: [pfSense Support] CARP Bug in 1.2.3
On Thu, Apr 9, 2009 at 12:37 PM, Dimitri Rodis
wrote:
> I think this is more obscure than you think-- this is on a snapshot build,
> so how many people have 1) run a 1
On Thu, Apr 9, 2009 at 12:37 PM, Dimitri Rodis
wrote:
> I think this is more obscure than you think-- this is on a snapshot build,
> so how many people have 1) run a 1.2.3 snapshot, 2) _had_ a redundant CARP
> config, and then 3) removed the redundant member and 4) added some Outbound
> NAT rules
ewhere, because like I said, I didn't
dupe the section myself.
Dimitri Rodis
Integrita Systems LLC
-Original Message-
From: Scott Ullrich [mailto:sullr...@gmail.com]
Sent: Thursday, April 09, 2009 8:15 AM
To: support@pfsense.com
Subject: Re: [pfSense Support] CARP Bug in 1.2
On Wed, Apr 8, 2009 at 11:31 PM, Dimitri Rodis
wrote:
> Currently running:
>
> 1.2.3-RC1
> built on Wed Apr 1 16:59:10 EDT 2009
>
>
>
> Changed the CARP config-- had a redundant member that I removed, so I shut
> pfsync off. However, I kept getting messages along the top that XMLRPC sync
> was fai
