On 2013-09-29, at 2:19 PM, Ernst den Broeder wrote:
> a week went by, I thought it was fixed but alas, today it had a kernel crash
> after almost reaching day 14. What can I do to help a developer find the
> problem? I would really like to see this fixed as I think pfSense an
> absolutely a
You misunderstood completely. I added those items AFTER I started having
problems as a diagnostic to eliminate things people would recommend I
try. The BASE HARDWARE was causing this issue. The replacement UNIT you
sent me IS FINE and i'm thankful for reaching a resolution and the old
unit is b
Nevermind.
I solved it by accidentally recreate my LAN interface. It works now.
Regards
GodriL
On Mon, Sep 30, 2013 at 2:53 PM, godril wrote:
> Hi,
>
> I dont know if this been already discussed, since I just joined this
> mailing list, but I'll push my luck.
>
> Previously I ran happily with
In a recent thread there was mention of a RRD bug when upgrading to 2.1 on
nanobsd systems where the /tmp filesystem would fill up, resulting in a
sytem with no valid interfaces.
I have two production systems to be upgraded, one running 2.0.1 and the
other running 2.1RC0, both nanobsd, so this pro
Yudhvir,
I’m just grumpy, because of messages like the below (OP, not you), and threads
like this:
http://forum.pfsense.org/index.php/topic,66684.15.html
Note again that it’s someone who decided to put their own SSD in the box,
loaded their own version of pfSense, then blew their foot off wh
Jim,
Netgate has a solid reputation for quality stuff and I happen to be a happy
customer. On occasion when I've called with technical questions, your
support has been very good. Enough for me to recommend your company and
products... and support.
Therefore, I find your "starting" tone a bit defe
Hi,
Some of you may remember me posting about this before, but since 2.1 became
available, I thought I would try again. The problem I have is that when a
scheduled LAN rule is configured, my pfSense will randomly crash, usually in
the VR driver. I'm very confident it is not a hardware problem
Netgate sold you a FW-7535 with a CF card and either 1MB or 2MB of ram,
originally.
You changed the ram and installed an SSD, reloaded pfSense, and now you want to
complain that Netgate couldn’t… what, exactly?
There are thousands of FW-75xx systems in the world, happily running pfSense.
T
Hi,
Some of you may remember me posting about this before, but since 2.1 became
available, I thought I would try again. The problem I have is that when a
scheduled LAN rule is configured, my pfSense will randomly crash, usually in
the VR driver. I'm very confident it is not a hardware problem
Le 2013-09-23 08:15, Ugo Bellavance a écrit :
Le 2013-09-20 00:28, Chris Buechler a écrit :
On Thu, Sep 19, 2013 at 8:22 AM, Ugo Bellavance
wrote:
Hi,
My old PC Engines WRAP is still surviving, and I'd like to install
2.1 on
it. Are these instructions still valid for 2.1?
https://doc.pfsense
On Monday, September 30, 2013 10:58:42 AM Seth Mos wrote:
> On that note: This is a last call to people in the US to
> get one before they are stuck in a hard place.
>
> We got ours just in time before the last /8 policy in
> RIPE land.
>
> Like the whole IPv6 migration, better plan ahead then g
On 30-9-2013 10:53, Chris Bagnall wrote:
> On 30/9/13 7:56 am, Seth Mos wrote:
>> I finally bit the bullet and signed up for PI space with a ASN and
>> hopefully that's that.
>
> Worth mentioning here that no more IPv4 PI ranges will be allocated - at
> least not within RIPE jurisdiction (conserva
On 30/9/13 7:56 am, Seth Mos wrote:
I finally bit the bullet and signed up for PI space with a ASN and
hopefully that's that.
Worth mentioning here that no more IPv4 PI ranges will be allocated - at
least not within RIPE jurisdiction (conservation rules kicked in when we
started on the last /
Hi,
I dont know if this been already discussed, since I just joined this
mailing list, but I'll push my luck.
Previously I ran happily with pfSense 2.0 with another router behind it to
handle the LAN traffic.
The schema looks like this:
internet <--> pfSense <--> subnet 192.168.1.0/24 <---> rou
14 matches
Mail list logo
