Ah - also good to know.  Thanks again.

Referring to the end of that other post:

from pfsense to AP - There is Ping

That would go out from 192.168.2.1 on pfSense directly to the AP. So pfSense OPT1 and the AP have compatible (hopefully the same) subnets.

from AP to pfsense - no ping

I guess that was from AP, ping 192.168.1.1 - the pfSense LAN IP. In that case the AP probably does not know how to route to that. If you tried to ping 192.168.2.1 then that is good, but you will need to have added a pass rule on OPT1 after booting the LiveCD version.

I can't understand what has happened here - the symptoms look a lot like an AP subnet/mask/default gateway problem. But it is pfSense that has been upgraded - so what is the real cause of the problem???

Can you post the actual AP:

IP address network mask default gateway for LAN (or tell us that there is no setting for that)

and confirm that OPT1 is 192.168.2.1/24 and has a pass rule with source any (or OPT1 net).

I wouldn't worry about offending johnpoz, I'm sure he can take it!  ;D

It can be frustrating when people don't appear to be following instruction. However in this thread there were many instructions from many people. I stopped posting because it was just confusing matters. Glad you got it sorted.  :)

Steve

Ah - You are in luck.  I would just wipe it, reinstall 2.1 clean (not upgrade) and restore the configuration you saved before you updated.

Which firebox? How much RAM?
Key to this seems to be the backing up of RRD files in combination with the update/reinstalling packages. If you have either a lot of interfaces or a lot of data you may run out of space. How far back does your RRD data go?

http://forum.pfsense.org/index.php/topic,66571.msg364374.html#msg364374

Steve

@Jon:

Hello All,

I recently upgraded my firewalls from 2.0.3 to 2.1 and noticed that after the upgrade the rrd graphs for traffic aren't accurate. The widget on the dashboard displays accurate traffic data, but the rrd graphs display 1/3rd the actual amount. For instance I just reset my rrd graph data thinking it was a glitch from the upgrade and the traffic going through one of my wan interfaces is 30mbit. the switch graphs show 30mbit, the front widget shows 30mbit, but the RRD graph says current bandwidth is 13mbit. This wasn't the case on 2.0.3. Is anyone else seeing mismatches between rrd traffic graphs and the dashboard traffic widget/actual network data?

Regards,

Jon

EDIT: full 64 bit install running on DELL PowerEdge R610 Servers.

I have actually now noticed that the issue seems to be the SVG viewed graphs on the front page. they seem to display a data rate much higher than the actual rate. I tested this by upgrading the secondary firewall in a carp pair to 2.1 and left the primary on 2.0.3. When switching between the 2 the 2.1 firewall consistently showed higher inaccurate values in the svg graph on the front page than the 2.0.3 box. I flipped the carp between the 2 multiple times and noticed a consistent difference. The 2.0.3 box showed a much more accurate traffic rate that was consistent with rrd graphs from the switch port. I think there may be a bug in the graphing system perhaps due to the ipv6 additions? At low rates (sub 10mbit) it seems to be fairly accurate but as the rate increases it can often spiral out of hand and display double the actual rate. I tested this by switching from 2.1 to 2.0.3 during multiple loads and seeing drastic differences on 2.1 at high rates. I think there is a calculation issue somewhere in the graphing system that is multiplicative.

Regards,

Jon

@kejianshi:

My pfsense in my basement for my home use is Athlon X2.  You hurt my feelings  :'(

Pfffft, that's too new.

Thanks for the help

Partiton size not big enough is an odd error though. The slices in the 2G nano image are fixed size. The only way I could imagine that happening would be trying to upgrade with the wrong upgrade file, 2GB upgrade to a 1GB image for example. Shouldn't be possible to do that with the auto update though.  :-
Do you have the exact error wording?

Steve

This announcement: http://forum.pfsense.org/index.php/topic,66567.0.html
and read this for how to update your update URL: http://forum.pfsense.org/index.php/topic,66457.0.html

Thanks.  A sleep at the switch I was…

Got it, thanks…

@individual-it:

booting is now ok. But every change to the config by WebGui causes into a "crash or freeze", nothing is working.

Hmm, could it be that you are trying to install an ALIX BIOS on your Lanner? Where did you get that BIOS?
Anyway, I never had to update the BIOS on my Lanner to get pfSense installed.
I just used a USB card reader and wrote the pfSense i386 Nano 4GB image on my (4GB) CF using Windows. After that I just put the card in and it booted right away. You might need to switch the BAUD rate to 9600 8N1 to see pfSense boot if it does not match the rate of your Lanner BIOS settings.

Strange, rebooting the box seems to have fixed the issue.

I know the options of Traffic Graphs
And I tried it and it did not keep

The strange thing is
Just did the same actions
And it worked

About packages
The best way to know is to check the forums I guess

tnx

I have the same issue with my Atom base board, trying to auto detect the dev yield nothing, I read somewhere that it works sometimes, then you just typ ufs:dev/xxxxx and it will continue to boot, once booted you need to edit fstab

i went back to 2.03

There must be something wonky with my 2.0.3 settings that are causing 2.1 to crap out on me.

I had to do a complete reinstall from CD to wipe the drive and am now in the process of manually parsing through the backup.xml file to rebuild my settings.