On Aug 21, 2009, at 5:02 PM, Scott Ullrich wrote:
On Fri, Aug 21, 2009 at 3:45 PM, Ian
Levesquei...@crystal.harvard.edu wrote:
php: /xmlrpc.php: Disallowing CARP sync loop.
You have a CARP sync loop. You do not want to do that.
Thanks, Scott - that much I figured out :)
It turns out
On Aug 18, 2009, at 10:30 AM, Ian Levesque wrote:
I just noticed that my two pfSense boxen aren't syncing anymore. In
the logs, I see:
An error code was received while attempting XMLRPC sync with
username admin https://192.168.8.1:443 - Code 2: Invalid return
payload: enable debugging
Hello,
I just noticed that my two pfSense boxen aren't syncing anymore. In
the logs, I see:
An error code was received while attempting XMLRPC sync with username
admin https://192.168.8.1:443 - Code 2: Invalid return payload: enable
debugging to examine incoming payload
How can I
Hello,
I've got a WAN rule that allows traffic from a specific subnet in our
university's private network direct access to our LAN. We're basically
bridging two LANs across a WAN interface. The generated rule looks
like this, where 1.2.3.4 is our default gateway:
pass in log quick on
On Aug 18, 2009, at 6:51 PM, Chris Buechler wrote:
On Tue, Aug 18, 2009 at 6:44 PM, Ian
Levesquei...@crystal.harvard.edu wrote:
snip
From the rule editing page, it appears that a gateway can be
defined, but
I'm only given the option of using default or my default route
(1.2.3.4).
The
On Jun 26, 2009, at 2:00 PM, Ian Levesque wrote:
We're running DHCP and DNS on a pair of CARPed pfSense 1.2.1 boxen.
Other than the fact that they don't sync DCHP entries, it's been
working OK for us. However, we've currently got them configured to
assign static IPs to specific MACs
Hi all,
We're running DHCP and DNS on a pair of CARPed pfSense 1.2.1 boxen.
Other than the fact that they don't sync DCHP entries, it's been
working OK for us. However, we've currently got them configured to
assign static IPs to specific MACs, and that's becoming difficult to
manage.
Upgrade from -RC1 went smoothly here. Running CARP on two routers,
upgraded primary then secondary router. No problems to report.
Cheers,
Ian
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
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
Hello,
I'm running 1.2.1-RC1 (built on Sat Sep 13 03:53:42 EDT 2008). After
about 10 days of uptime, I noticed that logs were becoming stale. It
turns out that all logging functionality stopped yesterday evening. In
dmesg, the last messages are:
pid 20276 (clog), uid 0: exited on
On Oct 28, 2008, at 12:03 PM, Scott Ullrich wrote:
This is fixed in 1.2.1.
Good to hear. Is this fix included in the latest daily snapshot? Until
1.2.1 is released, is there something else I could do (maybe just a
nightly `kill -HUP ${syslogdpid}` cron job) to ensure that it doesn't
On Oct 27, 2008, at 7:01 AM, Steve Harman wrote:
Do we have the ability in pfSense to specify the domain suffix(es)
that get distributed to clients via DHCP? I couldn’t find anywhere.
my DHCP clients receive the domain i use in the General Setup Domain
field. is there a reason you'd have
13 matches
Mail list logo
