@AndrewZ: Same here, with the latest snapshot. EDIT: the issue seems to be gone rm /var/db/rrd/*.rrd disable/enable RRD graphing backend This did the trick for me too.

I'm not too familiar with the sk(4) devices from Marvell, but some others on the forums have had issues with them. Do you have another network card you could try in place of that NIC?

The exact same error? This error: Fatal error: Call to undefined function upgrade_000_to_001() in /etc/inc/config.lib.inc on line 405 Means that the config version tag is missing from the config.xml file, which would only happen if it were empty. If you want to send me the config I can have a look at it, jimp [at] pfsense {dot} org.

The  <preferoldsa>is what is used now, there used to be an older tag (<preferredoldsa>) but it was moved quite some time ago. It works for me though, the first two lines are with the checkbox off, second two are with the checkbox on: [2.0-RC1][root@pfsense.localdomain]/root(3): grep prefer /conf/config.xml [2.0-RC1][root@pfsense.localdomain]/root(4): sysctl net.key.preferred_oldsa net.key.preferred_oldsa: 0 [2.0-RC1][root@pfsense.localdomain]/root(5): grep prefer /conf/config.xml                 <preferoldsa> [2.0-RC1][root@pfsense.localdomain]/root(6): sysctl net.key.preferred_oldsa net.key.preferred_oldsa: -30</preferoldsa> ```</preferredoldsa></preferoldsa>

Ahh ok, it makes sense. :)

To get that working, you have to enable the dns-forwarder and have both options "Register DHCP…" enabled. The dns-forwarder acts as a small dns-server, which will fullfile all requests inside your homenet. Now you get your webserver via http://webserver01.local at your net. If you now enter at the DHCP-settings-page under "Search domain list" "local" (without the ""), then you will find your webserver via http://webserver01. Hope that will answer your questions. No host-file-hacking necessary. Good luck!

hello i just try with last build (10 march), it works fine Thanks

Thank You jimp

@scheidell: related to the whole thing.   if you try to upgrade, same problem.   bet you have an ata drive? /dev/ad4s1a? ? Hi Scheidell, From dmesg: ad2: 3825MB <sandisk sdcfx3-008g="" hdx="" 5.00="">at ata1-master PIO4  From Diagnostic: nanobsd: Bootup slice is currently: ad2s1</sandisk>

We CDATA escape the descrs now so that old protection could probably be safely removed on 2.0.

Not sure your setup will work. The usual way to do this is to add the IP address you have assigned to rl2 as a virtual IP address to the public interface rl0, then setup an rfc1918 DMZ  subnet off of rl2 hosting your mail, web etc. You then can either setup port forwarding (25 for smtp, 110 for pop3) through to the mail server in the DMZ. If all you intend to have is the one server then a 1:1 nat will do the job. Just add the rules to allow access on the required ports for both the WAN and LAN interfaces or allow pfsense to create them at the same time as the nat/port forwarding is created. I should also have said that allowing any traffic on any port through to your mail server is a very bad idea.

I have the exact same error too. Changing the MAC address will cause the interface to go up -> down -> up -> down. When I remove the interface mac address, it is all normal again and I notice the interface MAC has changed to what I want it to be. See if that is the case for you!

I'm not sure about your specific chipset, but aren't the common channels 1-12? Have you tried setting to one of those channels and rebooting?

Oke doke, I missed it last time, but somehow my opt1 interface had the same MAC address as my PC… checking under the interfaces tab I noticed that sure enough my PC's MAC address was entered. I've never had the need to do this, nor did I do it, very confusing. The only thing I've done is use the feature to create a WOL entry button found on the DHCP lease page. I will delete the WOL entry and see if I can recreate the issue.

The system has started behaving itself since posting this. Not sure if it was tied up dealing with package install or it ties in with the em0 ticket I raised.

NVM - resolved!

Ok I will give it a try. Very strange thing though as it is only with em0 not em1 and em2 that I have in the box fully working. It is a dual core dual proc system so not sure if it would be the way the PCI-E bus is designed that maybe making a difference. The error always happens on going onto the dashboard or making a config change to EM0.