Now suddenly spiegel.de works again.
strange.  ???

Easy!

RRD data is in /var/db/rrd

Just rm the data you no longer need.

e.g.
[2.0.2-RELEASE][admin@pfsense.domain]/root(1): cd /var/db/rrd
[2.0.2-RELEASE][admin@pfsense.domain]/var/db/rrd(2): ls
GW-quality.rrd      ovpns1-traffic.rrd  system-states.rrd
WAN-quality.rrd      ovpns1-vpnusers.rrd  updaterrd.sh
ipsec-packets.rrd    ppp-cellular.rrd    wan-packets.rrd
ipsec-traffic.rrd    system-memory.rrd    wan-traffic.rrd
ovpns1-packets.rrd  system-processor.rrd
[2.0.2-RELEASE][admin@pfsense.domain]/var/db/rrd(3):rm ovpns1*.rrd
[2.0.2-RELEASE][admin@pfsense.domain]/var/db/rrd(4):

to drop the OpenVPN interface stats

If you only give it one interface in the initial CLI setup it will be labelled WAN and it will be open for connections to the webgui.
However that is a special case, as soon as you add another interface it will default back to blocking all incoming connections on WAN.

Steve

I was able to fix it.  First i tried removing the prompt altogether via http://doc.pfsense.org/index.php/Remove_F1_Boot_Prompt .  I didn't really expect it to work since it wasn't defaulting incorrectly (it didn't work).

I got my install disk and just reinstalled the bootloader from it.  All is well now.

might be solved now. doing testing atm.

i had at one time lvl 1 at 256 and when i change to 128 / 64 and so on the cache disk still had the old dirs
dont know if that was the problem. but i deleted all folder in cache and did squid -z when i have the default 16 on the lvl 1

hope that was the problem.

Thank you guys, I'll report to them.

Thanks for replying, I also had this feeling but hoped that someone might have tackled it somehow.

It doesn't work Mutual PSK + Xauth for vpnc:

http://forum.pfsense.org/index.php/topic,59385.msg319238.html#msg319238

Use ike-qtgui (Shrew Soft VPN Access Manager) package.

update: last couple of days it seems to be going ok.
Did not update yet to 2.0.3 prerelease, also reverted back from all previous modifications.

What seems to be working: in "System\Routing\GW_WAN" under 'Advanced' I increased the value 'Down' to 60 (default was 10). This action seem to have helped for the dyndns update, I haven't had the nasty 'curl' error anymore since modification. So either it actually helped, OR I have been lucky until' now. I still sometimes see the GW as Offline, so maybe I should double it. (maybe I need some better understanding of the apinger mechanism  :-[ )

As 2nd backup mod, I installed the cron package & modified the nightly scheduled DynDns check to run every 30 minutes. It does pollute the system log a bit, but good side effect is I can check how it is working, and so far it seems I haven't needed the cron mod yet.

before I forget: Tnx Tim & Phil for the given suggestions! Really appreciated…

Nope. I also haven't got an iPhone :)

Hi,

And did you added firewall allow rules for your dvr ports? And what is/are your dvr port(s) And if you want to connect default port (80) it might be conflict witrh your pfsense box port. You should change web access port on your dvr device.

Regards,
SGTR

Very good point!

Hmm I will give it a try and see what happens. Sounds a lot more simple anyway.

@jimp:

The backtrace seems to indicate a problem in memory or the hdd, hard to say for sure since it just mentioned that it crashed while operating in the swap space code.

That's deeper down in FreeBSD than we touch, so it isn't likely to be an OS or pfSense issue, most likely hardware in some way.

Thanks for the tip! Will do a hardware diag during off hours.

Appreciate the super quick response!

-M

I have the same issue but it seems people who are testing it don't happen to experience it.

PERFECT!

In the System -> User Manager section, I clicked on edit admin account.

In the "Authorized keys" section, clicked "Click to paste an authorized key."

I had to re-type in my password, because I kept getting an error that the passwords didn't match.  Once I did that, it worked like a charm.

Thanks again!

ok, got it working.  not sure what the deal was, i didnt change anything today.

i plugged the cisco router into opt1, just as i did last week, and it worked w/o any issues.  i used the same straight through cable that i had left on site.

anyway, just wanted to update the thread.

thanks.

Well, it looks like "Have you tried turning it off and on again?" Has succeeded after a 2nd reboot.