Re: [pfSense-discussion] long upgrade of 1.2.3RC3full on ALIX

2009-10-15 Thread Jim Pingle
Eugen Leitl wrote: > On Thu, Oct 15, 2009 at 11:40:50AM +0200, Eugen Leitl wrote: > >> Aargh -- you might have found the real culprit there. >> Unfortunately, meanwhile I figured out that the error >> message was due to a corrupt /etc/rc.upgrade (read error, >> I presume the flash is fried). I've

Re: [pfSense-discussion] pfsense IPSEC support

2009-12-05 Thread Jim Pingle
Harald Jenny wrote: > first I wanted to say thank you for this nice piece of software, I think it > can keep up with most commercial appliances, the only thing that makes me a > little bit sad is the IPSEC support. Not really being a great BSD-crack it > seems to me that the FreeBSD port of isak

Re: [pfSense-discussion] oink, oink

2010-02-26 Thread Jim Pingle
On 2/26/2010 10:26 AM, Eugen Leitl wrote: > There's no way to get snort to run on an ALIX, am I correct? It should work but you must be _very_ frugal in choosing the (few) rule sets you want to load. Also setting it to lowmem is a must. Jim ---

Re: [pfSense-discussion] modified nanoBSD 1.2.3 image for WRAP?

2010-03-08 Thread Jim Pingle
On 3/8/2010 3:25 PM, Christoph Hanle wrote: > On 07.03.2010 18:23 Eugen Leitl wrote: >> >> Does anyone have the 1 GByte 1.2.3 image modified for WRAP >> around? Thanks. >> > Hi Eugen, > please be carefull with production usage of pfSense 1.2.3 on WRAP, > I have more troubles with this combiniation

Re: [pfSense-discussion] modified nanoBSD 1.2.3 image for WRAP?

2010-03-08 Thread Jim Pingle
On 3/8/2010 5:51 PM, David Rees wrote: > I've seen same or similar behavior on an ALIX box with a fairly large > ruleset and decent number of VPNs. > > We could never get all the VPNs to come up properly and we eventually > ended up with a corrupted configuration file while we were trying to > dis

Re: [pfSense-discussion] API?

2010-11-12 Thread Jim Pingle
On 11/12/2010 2:01 PM, Nathan Eisenberg wrote: > I have a customer who wants to be able to automate IP blackholing on their > PFSense firewall from their custom IDS. In essence, the application wants to > go something like > > 'I'm being abused by this IP 198.51.100.20' > 'POST HTTPS://GATEWAY

Re: [pfSense-discussion] 2.0-BETA5 (i386) built on Sat Jan 1 17:53:01 EST 2011

2011-01-02 Thread Jim Pingle
On 1/2/2011 5:00 AM, Eugen Leitl wrote: > > I'm screwed up after yesterday's update. The firewall > stopped routing after yesterday's upgrade > to 2.0-BETA5 built on Sat Jan 1 17:53:01 EST 2011 > > The firewall seems to see everthing > (with the exception of package updates: > "Unable to communi

Re: [pfSense-discussion] 2.0-BETA5 (i386) built on Sat Jan 1 17:53:01 EST 2011

2011-01-02 Thread Jim Pingle
On 1/2/2011 10:09 AM, Eugen Leitl wrote: > On Sun, Jan 02, 2011 at 10:06:54AM -0500, Jim Pingle wrote: > >> Actually it looks like the packages aren't loading on pfSense.com, which >> would cause that error. It probably isn't related to the snapshots >> except

Re: [pfSense-discussion] 2.0-BETA5 (i386) built on Sat Jan 1 17:53:01 EST 2011

2011-01-02 Thread Jim Pingle
On 1/2/2011 10:45 AM, Eugen Leitl wrote: > On Sun, Jan 02, 2011 at 10:36:42AM -0500, Jim Pingle wrote: > >> If there is, it's probably related to the packages you had installed... > > I agree it's probably the packages. I've noticed it before, so > usually

Re: [pfSense-discussion] 2.0-BETA5 (i386) built on Sat Jan 1 17:53:01 EST 2011

2011-01-02 Thread Jim Pingle
On 1/2/2011 12:35 PM, Eugen Leitl wrote: > On Sun, Jan 02, 2011 at 11:44:07AM -0500, Jim Pingle wrote: > >> The packages should be OK again now. > > See the packages, upgrade of the other systems (from a > snapshot of 15 days ago) was uneventful (I purged whatever > few

Re: [pfSense-discussion] PFSense on compact flash, and packages

2011-02-14 Thread Jim Pingle
On 2/14/2011 4:35 PM, Cédric Jeanneret wrote: > Hello, > > I think I've read that we cannot install packages on pfsense when using > it on a compact flash (like for alix systems). > Will it be still true for 2.0? For now, I've found a opened bug about it > [1]... > If it's impossible, may I have a

Re: [pfSense-discussion] 1:1 and Outbound Nat

2011-02-25 Thread Jim Pingle
On 2/25/2011 2:37 PM, Tony Zakula wrote: > Hi, > > I am taking the plunge and switching to pfsense. First time loading > it, so please bear with me. > > I have two external interfaces in different ip ranges and subnet > masks. 3 Nics in the machine altogether. So I will be using 1:1 Nat > for

Re: [pfSense-discussion] squid.inc gotchas

2011-06-05 Thread Jim Pingle
On 6/5/2011 7:10 AM, Odhiambo Washington wrote: > So here is my patch, which also contains a few changes required in squid-3. There's your problem, squid 3 is largely untested and should not be trusted. :-) If you want it to work, use the squid 2.x package. Every so often someone else comes alon

Re: [pfSense-discussion] squid.inc gotchas

2011-06-06 Thread Jim Pingle
On 6/6/2011 5:43 AM, Odhiambo Washington wrote: > On Sun, Jun 5, 2011 at 18:04, Jim Pingle http://forum.pfsense.org/index.php/topic,32923.msg191044.html [snip] > So in essence, we need: > > (12:25:03 <~>) 0 $ diff squid.inc squid.inc.local > 527c527 > < } > --

Re: [pfSense-discussion] Disk-based Backup

2011-06-08 Thread Jim Pingle
On 6/8/2011 1:50 PM, Odhiambo Washington wrote: > I have decided that my pfSense PC will have two disks - ad4 and ad6 as > they are now. > I'd like to backup ad4 to ad6 every weekend - automated using dump. > > Is this the stupid way of doing it? > > I have a feeling that someone would tell me th

Re: [pfSense-discussion] Disk-based Backup

2011-06-08 Thread Jim Pingle
On 6/8/2011 2:04 PM, Bao Ha wrote: > How is ataraid ("fake" raid) compared to gmirror? > > I think the main disadvantage of ataraid is that it is tied to a > specific chipset. It is difficult to recover the disk if moved to a > different systemboard. But, for redundant purposes of a firewall, you

Re: [pfSense-discussion] Disk-based Backup

2011-06-08 Thread Jim Pingle
On 6/8/2011 2:32 PM, Adam Thompson wrote: > The main issue with using RAID instead of backups is that it doesn’t > protect against corruption, software bugs, or human error. While there > are some cases were restoring to last weekend’s known-good state isnt’ > adequate or appropriate, those are fe