@jimp:

We've seen that now and then but haven't found a 100% fix for it. It seems to happen when rc.newwanip resets NTPD after an IP address change or interface up or down event.

maybe this will help:

      -U number, --updateinterval=number               interval in seconds between scans for new or dropped interfaces.               This option takes an integer number as its argument.               Give the time in seconds between two scans for  new  or  dropped               interfaces.  For  systems with routing socket support the scans               will be performed shortly after the interface  change  has  been               detected  by  the system.  Use 0 to disable scanning. 60 seconds               is the minimum time between scans.

Thanks. My problem was that I was mistakenly only searching within the sub forum folder. Thank goodness for that Newbie "Driver In Training" star. I feel like it is half an excuse anyway.

This might make a nice addition to pfSense, too:

http://www.openlisp.org/

http://en.wikipedia.org/wiki/Locator/Identifier_Separation_Protocol

Put a corresponding post into the packages wishlist thread…

You're not alone: http://forum.pfsense.org/index.php/topic,62237.0.html

I tried everything I could think of but couldn't get traffic to flow through ipsec vpn.
My OpenVPN is hosed in 2.1 as well, I can't run a server and a client at the same time and these errors are thrown every minute:
MANAGEMENT: Client connected from /var/etc/openvpn/server1.sock
MANAGEMENT: CMD 'status 2'
MANAGEMENT: CMD 'quit'
write to TUN/TAP : Invalid argument (code=22)

I'd really like to see 2.1 ready for production but it seems quite rough at this point from a vpn perspective.  How can I help to resolve all of these vpn issues?

If something is completely and totally broken, it should be disabled. I'm not aware of any packages currently that are completely broken. General stability of packages is noted by their status: alpha, beta, stable.

60 can be too low at larger scale (hundreds of tunnels).

It might be possible for that to be a tunable somewhere in the future though.

I also added a new Zabbix agent item which counts the interfaces without ipv4
It's not as elegant or sturdy as I want it to be, but let's see if this will give me false positives….

ifconfig | grep -A2 'ether ' | grep -c options 0

In Zabbix Agent, they look like this:

UserParameter=net.ipv4.ifs,ifconfig | egrep -c 'inet .*[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+ ' UserParameter=net.ipv4.noip, ifconfig | grep -A2 'ether ' | grep -c options

I noticed that check.reload.status really spikes my processor and I have more than a minute no connection after I add an interface or vlan…
Sometimes not all the interfaces come back with an IP

It would be nice if this didn't happen in the final version....

Resetting the web configurator (option 11 on the console) let me get to the dashboard.

option 1  8)

http://lists.pfsense.org/pipermail/list/2012-September/002934.html

Take a look at this link it might help explain it a bit better.  You can even disable gateway monitoring if your are not using failover.

wallabybob, thanks for helping me

I just ticked the box to disable hardware calculation, reboot pfsense and ….. IT WORKS

Yesterday, I also did tick the box but I did not reboot the pfsense virtual machine as the web interface's message was "The changes have been applied successfully." + Close button

Maybe pfsense developers should modify the message to "Your appliance must be rebooted" + Reboot button

Thank you my problem is solved

I believe it only shows up when you first access the DHCP section (e.g. go to services_dhcp.php) once you pick an interface tab, if the interface has a static IP, it goes away.

The code could maybe be a bit smarter about when to display the message, but ultimately it's there because people question why some interfaces are not in the list and it's because those interfaces have dynamic IPs.