It seems to be up. At least I'm getting 'beacon stuck' messages from it:

Dec 11 21:29:27 kernel: ath0: stuck beacon; resetting (bmiss count 4)

We use ath0 for our "guest wireless". As we have no guests right now, there's no traffic on it, so no big deal if it's down.

Same Problem here, IDir 'Domain.name' does not match to 'IP address'.

But I can Access the remote Firewall over Domain Name or IP address (using zoneedit).

The Domain Name does have another reverse IP Name as it is from the Internet Provider.

It's a ipseq pfsense <-> m0n0wall.

Thank you for your reply,

Everything is working fine now. There was no real problem with DNS Forwarder as I found a couple of hours later that there was a massive DDOS attack using the DNS servers of my ISP TeliaSonera against Electronic Arts at the time of my installation which fooled me into believing that there was a problem with pfsense. It seems like it subsided after I switched to DNS Resolver which made me draw an incorrect conclusion. I switched back to DNS forwarder today after your mail and all is ok.

I will clear my browser cache in the future in any case of GUI abnormalities. Thank you for your other advice and I will post a Suricata feature request in the packages subsection. The line speed is still discretely faster, fluke or not :)

Thank you

Ah, found it.
After adding another symlink perl works again:

/usr/local/lib/perl5 -> /usr/pbi/nrpe-amd64/local/lib/perl5

Thanks for the heads up, I'll get it updated today and report back!

Thanks for all the great work!

Regards

Dave

I too have a multi-wan setup and outgoing FTP does not always work. I mostly notice it on websites that have download links to FTP sites. I click on the link and nothing happens. I usually resort to launching filezilla, entering FTP link and click retry over and over until it works. Unfortunately I do not know how to debug this issue. Let me know what info I could provide. Here is my setup:
I am running version 2.2 RC, in ESXi environment with dual wan/single LAN. Older posts mention 'debug.pfftpproxy' mine is set to 0. TFTP Proxy is set to LAN (No sure if this even applied to this issue).

Just did an installation with the 2.2 RC releaes. Now its working fine out of the box :D

https://blog.pfsense.org/?p=1506

@phil.davis:

No, that has been discussed in the forum somewhere in the past but not implemented. And yes, in some scenarios it would be handy, allowing the user to define the order in which the default gateway switched over as WANs go down/up.
At the moment you can enable default gateway switching in System, Advanced, Miscellaneous. But if you have more than 2 WANs there is no way to tell pfSense which alternate WAN/s to select in which order as the failover default gateways.

thx for your quick response

upgraded to 2.2 RC and then tried and started working

That #90EE90 is the color to display.
usr/local/www/javascript/index/ajax.js changed to implement better handling of that gateways widget color display.
I guess browsers will have cached the old ajax.js - try a full page reload and/or clear some caches.

This should really be a separate topic!
Look in your config for $config['installedpackages']['pfblockerlists']['config'] (Diagnostics->Edit File, /cf/conf/config.xml - look for pfblockerlists and config under that and row and url under that. config.xml is in XML format.) Those should point to some files. In the file/s there will be loads of URLs…
I guess one of those files has a huge number of entries and it is exploding PHP memory.

I did find a temp fix while on outage.  I changed the WAN configuration from auto detect (which was auto detecting 1000BT/full) to 1000BT/full static and the problem vanished.

I updated the 2.2 release notes page today and added a note about that in the captive portal section.

https://doc.pfsense.org/index.php/2.2_New_Features_and_Changes#Captive_Portal

Heh, I knew it.  With no snapshots for a few days, I could smell the RC coming a mile away.

Turns out I had a second simultaneous connection running from another Host in the pfSense LAN network. This caused the connection to have this mysterious freezes.