Comments on: Development update http://blog.pfsense.org/?p=459 News, reviews and more related to the pfSense firewall project Sun, 19 May 2013 21:07:07 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: roy slinkman http://blog.pfsense.org/?p=459&cpage=1#comment-4704 roy slinkman Mon, 31 Aug 2009 16:06:13 +0000 http://blog.pfsense.org/?p=459#comment-4704 I have been running 1.2.3-RC1 at five different sites all connected by IPSEC vpns with squid, squidguard and lightsqid packages installed.

absolutely NO issues!!!

great product and the five sites were ipcop sites (replaced them).
using old dell’s and intel nic’s.

Keep up the great work.

]]> By: Chris Buechler http://blog.pfsense.org/?p=459&cpage=1#comment-4240 Chris Buechler Tue, 14 Jul 2009 23:29:58 +0000 http://blog.pfsense.org/?p=459#comment-4240 Shaun: no, that discussion is happening in IRC and emails for right now.

]]> By: Shaun http://blog.pfsense.org/?p=459&cpage=1#comment-4238 Shaun Tue, 14 Jul 2009 21:43:32 +0000 http://blog.pfsense.org/?p=459#comment-4238 Chris,
Is there a spot on the web other than http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/127528 that we can follow the progress on the ping issue? I am by no means a developer but I did find the thread very interesting, at least what’s online.

Thanks!

]]> By: Chris Buechler http://blog.pfsense.org/?p=459&cpage=1#comment-4181 Chris Buechler Thu, 09 Jul 2009 16:00:28 +0000 http://blog.pfsense.org/?p=459#comment-4181 No update to the PR doesn’t mean we’re not working on it. Yes, the release is on hold until that is resolved, and we are actively working on it.

]]> By: tohil http://blog.pfsense.org/?p=459&cpage=1#comment-4178 tohil Thu, 09 Jul 2009 11:17:27 +0000 http://blog.pfsense.org/?p=459#comment-4178 hi Chris,
i saw in the issue 127528 since may no comment update. are you near on a solution or is the problem not so easy to fix? is release of 1.2.3 hold till this is fixed?

regards

]]> By: Chris Buechler http://blog.pfsense.org/?p=459&cpage=1#comment-4103 Chris Buechler Mon, 29 Jun 2009 21:59:42 +0000 http://blog.pfsense.org/?p=459#comment-4103 Steven: Yes it has finally been acknowledged, we’re working with one of the FreeBSD core developers to find a solution.

]]> By: Steven http://blog.pfsense.org/?p=459&cpage=1#comment-4102 Steven Mon, 29 Jun 2009 21:54:03 +0000 http://blog.pfsense.org/?p=459#comment-4102 Chris, just out of curiosity – have the FreeBSD devs been able to reproduce or acknowledge the bug within “ping”? I read over the report that started back in Sept 2008, and it seems that it isn’t being readily acknowledged. I wonder how long it will take to resolve this issue, without that acceptance.

BTW, great job on PFSense, I’m part of the silent majority, but I must say that PFSense is totally sexy, and the best firewall platform I’ve ever had the pleasure to work on. I am looking forward the 1.2.3 release!

]]> By: Chris Buechler http://blog.pfsense.org/?p=459&cpage=1#comment-4074 Chris Buechler Thu, 25 Jun 2009 14:21:26 +0000 http://blog.pfsense.org/?p=459#comment-4074 xeonixc: that is one of the suspected FreeBSD issues that I’m looking at but I don’t see any problems other than the one we got fixed upstream about 3-4 weeks ago.

]]> By: xeonixc http://blog.pfsense.org/?p=459&cpage=1#comment-4073 xeonixc Thu, 25 Jun 2009 10:32:41 +0000 http://blog.pfsense.org/?p=459#comment-4073 cant wait any more for RC2, checking your website six times a day, throw it out quick or i jump out of the window :P . Well any bug fixes in wireless and LAN bridge code in RC2?

]]> By: Chris Buechler http://blog.pfsense.org/?p=459&cpage=1#comment-4072 Chris Buechler Thu, 25 Jun 2009 05:36:47 +0000 http://blog.pfsense.org/?p=459#comment-4072 Aaron: Welcome. :)

Johnny: Yeah SSD should be supported just fine. Though given the experience of one of our developers who has been working with them, the reliability factor just isn’t there yet it seems. Very high failure rates.

The next generation of embedded is coming soon, at which point it will be a much better choice than the current embedded. You’ll still be limited to some extent due to the nature of CF, but the upgrade problems will be gone, and package support (for those suitable on such a platform) will be available. ETA a month or so.

]]>