Should be fixed on latest snapshots.

Should be red as far as I know. They show red for me in firefox, chrome, and opera.

Pushed a commit to fix alias display just now.

Yeah, sorry for the trouble and thank you for the reports.
The fix is intended for some ipsec configs but i will check how to make it less problematic.

Perhaps it's posible to remember last state of interface/gateway and send only email if state differs.
2nd perhaps: make it possible to mark an interface/gateway to send email on change.

Thanks Jim, everything works great with the new recompiled qstats!

And… you will see the next version of the status-queue page, that's the result I wanted to achive! ;)

Michele

Just upgrade to the release and it's fine.

The whole run was bad, and was deleted. The new ones should be OK.

Thankyou very much, that worked great!

Should be fixed by this:
https://github.com/bsdperimeter/pfsense/commit/f54712b6c8cc69721ccfd5b26a23e62bca722b72

The timestamp is not so important, check the size/hash value before and after the test.

I don't see it at the moment but we used to pass -m to tar so it would not change the modification times when extracting.

Read the answer Jim has given in the other thread.

anyone?

Rules on any interface called optn (usually people have renamed them WiFi etc, but they are called opt1, opt2 etc underneath) were working fine. It is only the case for the "builtin" interfaces called wan and lan that was broken.
I have made a pull request to fix it: https://github.com/bsdperimeter/pfsense/pull/373
Yes, it turns out it has been broken in the 2.1/mainline branch since April 2011! (see comments on pull request for links to that)

I added that to the builds yesterday, should be in the current snapshots.

I believe so, yes. You'll only see the C for hosts on the other end of a route/iroute network and not the client IP itself.

Initially 2.1 was going to be built on FreeBSD 9.0. In fact there were a number of builds that were tested. However there were problems that proved too difficult to overcome in a reasonable time frame and hence 8.3 is now the base OS.

Steve

May have possibly found it, was looking at https://github.com/bsdperimeter/pfsense, and found hw.usb.no_pf="1" was added two days ago to the loader.conf.  (http://redmine.pfsense.org/issues/2306)  Even though this refers to disabling the USB buss from showing as a network interface.  I did think this could possibly be having an effect, I added a system tunable and set hw.usb.no_pf with a value of 0.  After a reboot, below is the output from iperf, internet performance running a test on www.speedtest.net appears to be back up to normal.

8] local 192.168.5.3 port 60103 connected with 192.168.5.1 port 5001
[ ID] Interval      Transfer    Bandwidth
[  8]  0.0- 1.0 sec  9.00 MBytes  75.5 Mbits/sec
[  8]  1.0- 2.0 sec  7.00 MBytes  58.7 Mbits/sec
[  8]  2.0- 3.0 sec  5.75 MBytes  48.2 Mbits/sec
[  8]  3.0- 4.0 sec  8.75 MBytes  73.4 Mbits/sec
[  8]  4.0- 5.0 sec  6.88 MBytes  57.7 Mbits/sec
[  8]  5.0- 6.0 sec  8.88 MBytes  74.4 Mbits/sec
[  8]  6.0- 7.0 sec  7.00 MBytes  58.7 Mbits/sec
[  8]  7.0- 8.0 sec  7.75 MBytes  65.0 Mbits/sec
[  8]  8.0- 9.0 sec  9.50 MBytes  79.7 Mbits/sec
[  8]  9.0-10.0 sec  3.88 MBytes  32.5 Mbits/sec
[  8]  0.0-10.0 sec  74.6 MBytes  62.5 Mbits/sec

It's possible though that the problem doesn't show up for a little while, so I will redo tests later today and see if the problems back or if this did indeed resolve the problem.