you can, but don't do it. pc's are horrible switches

My apologies: I should have read more carefully. I just jumped down to the "Disable Write Caching" section. I think I have documentation fatigue today.

Yes, hint.ata.0.mode=PIO4 works in place of hw.ata.ata_dma=0 and, it boots fine.

Thank you.

Andrew

I'll just point out that your WAN side rules are similarly flawed.
Your NAT rules to allow IPSec traffic to a server at 192.168.0.9 will not pass the required UDP traffic.

Steve

Not sure what you were doing with tinycore in the original post, but you didn't end up with nano on it as it wouldn't be mounting adaX. Just write the SD card from another machine and move it over to the APU.
https://doc.pfsense.org/index.php/Writing_Disk_Images

https://doc.pfsense.org/index.php/Writing_Disk_Images

Ah, thanks!
I did not have a entry like that in the backup. But after som try-and-errors (thank god for snapshots!!!) i figured out to go to "System->Advanced->Serial Communications->Change to VGA" on the 2.1.5 system, save the configuration and take a backup again adds the following to the XML:

<system><serialspeed>9600</serialspeed> <primaryconsole>video</primaryconsole></system>

Now it boots fine after restoring config :)

@heper:

start by removing the mouse (it isnt of any use when dealing with pfsense)
try a different keyboard to see if that makes any difference (as basic as possible)

I unplugged both the keyboard and mouse and did a reboot. Seemed to work. CPU usage is at 0% idle. Ill try connecting the keyboard and doing a reboot and see what happens.

EDIT:
Plugged keyboard back in without the mouse.

CPU usage at 0%.

$ vmstat -i interrupt                          total      rate irq16: ehci0                        345          1 irq23: ehci1                        458          2 cpu0:timer                        236204      1124 irq264: xhci0                        50          0 irq265: em0                          391          1 irq266: em1:rx 0                    2824        13 irq267: em1:tx 0                    664          3 irq268: em1:link                      1          0 irq269: ahci0                      2189        10 cpu1:timer                          2310        11 Total                            245436      1168

Thank you guys! Hopefully the issue doesn't return. Now ill spend my time tinkering around.

If all else fails, try a 2.2.3 snapshot. We added more cleanup code to remove old mirror info from disks before creating a new mirror.

@michael2015:

hallo,

Am trying to install pfsense on an acer desktop to help me monitor my network. anyone to guide me through the steps of installation and configuration. I appreciate that

pfSense isn't a network monitoring tool, it's a router/firewall.

Captive portal issues solved ?
Meanwhile I'm using 2.2.2 some time now. This is a graphical result (real time) : http://www.test-domaine.fr/munin/brit-hotel-fumel.net/pfsense.brit-hotel-fumel.net/portalusers.html
These stats are from an hotel, so I do NOT control the device of our users (clients), neither what and how the clients are working with the portal.
All I know is that pfSense + captive portal works.
2.2.2 is rock solid.

Btw : I consider 2.1.5 completely different to 2.2.2  - it's a major kernel upgrade, PHP upgrade ad much more.
Something as a "in place" upgrade when it concerns BIG changes are not logic neither usable. Servers aren't upgraded like that, neither desktop PC's, neither firewall and routers.
Going from 2.1.4 to 2.1.5, ok, but 2.1.5 to 2.2.2 is another ball game.
Put the config file on a clean install - and it rocks.
And yes, sometimes its needed to look into the config XML file (its just a clear, readable file) to do some final trimming.
Stay away from packages if you can't stand the hard-core code parching.

Steve:

Thanks for the kind updates. I have just had success by turning on UPNP in Pfsense for port range 1024-65535 which is the range that Skype indicates it may use. I showed udp status as good now. Let's see how this operates for a while. I have been trying to short this out for a week. Skype is great but they could use a update of the client software.

Best Regards,

Howard

Thanks Heper.  It was affecting my FTP server (not client), but I already had all of that stuff done.  What fixed it for me was totally bizarre.

When I had first set this up a year or so ago I was pretty green.  I had defined the passive port range different from the NAT'd port range for some reason that I don't remember.  Originally I had 30000-30100 reserved for passive FTP (we don't have many FTP users at all so a small range was fine) and mapped it to 20-120.  Duh, so stupid, but I didn't know what I was doing with pfSense at the time.  I saw that, nuked the port remapping and let it sit natively at 30000-30100 and it's been working fine ever since.

Just a like to DD-WRT howto in case someone else hits this thread in future: http://www.dd-wrt.com/wiki/index.php/Wireless_Access_Point

youripadress/system_advanced_misc.php

I was configured the "Proxy URL" and "Proxy Port".
When erase this configuration, update work again.

I solved using squid in a debian server  :P

@georgeman:

Alright, it is confirmed to be the same issue then, thanks

thanks it works ! :)

Were you able to get your problem resolved?