The client time issue in the NTP dashboard widget has been fixed:
https://redmine.pfsense.org/issues/7245

You need to create an own topic in "traffic shaper".
Wizard created shaper needs manual tune. You need to create or use exciting firewall rules to assign your desired queues to traffic. Fo example you have utorrent running on 192.168.1.10 port 1111 (port forwarded), you need to find wizard created p2p floating firewall rule and manually assign IP and port.

Changing it system-wide wouldn't accomplish this particular goal of protecting just this one VPN. It would also kill the ability to reach the Internet at all.

It would have to be set on a policy basis, so pf or ipfw.

I agree though it's not worth the effort.

My issue specifically was with the regular dynamic DNS page, though it looks like it needed fixing on both of them :)

jump - thanks. This helps me know which direction to go.

Looks like fixed.

Great thanks! I can set it to 0 now without any errors. The errors on reboot have also gone.

Shit, you're right. Was reading the post above which said  …using 2.3.3 beta...
2.4 is still a way to go.

I made the changes are its working again.  Thank you  8)

Yes, you can update to daily snapshots and later to RC etc…

jimp:

Your floating rule workaround gets the problem temporarily fixed and all requested traffic flows flawlessly!

https://forum.pfsense.org/index.php?topic=117827

It seems related!

@doktornotor:

Multiple of those packages have XMLRPC features. Turn them off.

I've checket all the XMLRPC/Sync options in the packages (I've found them in squid, squidGuard) and all are configured as "Do not sync this package configuration" and I've clicked Save just to be sure!

UPDATE: I've found a Sync config in pfBlockerNG to another pfSense of mine, but version 2.3.2-RELEASE-p1, so I turned it off!

So the notifications stopped! Thank you!

Just a heads up, this patch fixed the display for non-WAN interfaces but when trying to change a rule on my LAN this morning nuked the WAN interface rules so make sure you have backups.

Thanks.

I followed the instructions in that section, to unload the selected module I selected Non/ACPI and then rebooted.
Same errors. But as long as there aren't issues with this error, all is good.

Thanks Phil, I checked the html and I have a feeling the changes I'd recommend would need HTML changes rather than CSS as they ought to be field-side not label-side.  That could be a lot of work looking at the logs so I'll leave it for now and consider doing it for my first code submission… Don't hold your breath though!

The main thing I wanted to check was if I should test all the pages you've changed or just some.  I'll go with all of them, that could take a while but I think it'll be worth it.

fyi with the newest update 2.4.0.b.20170208.0843 (your fixes included)…  i noticed the Blank/empty id=o returned on the services_dhcp.php page and the status_dhcp_leases page was back to the original issue.

After deleting the blank/empty entry on the new firmware.... everything returned to the correct state, rebooted and the issue did not return.

So, I think the issue has been corrected.... Like you Im not sure what I did to cause the problem.

@papadeeh:

Original problem solved with latest update

2.4.0.b.20170208.0843

:)

All screens cleaned up!

Please, don't multipost. https://forum.pfsense.org/index.php?topic=125239.0

In general, I'd avoid the badly broken netmap thing altogether.

It's because 2.4 is based on RELENG_2_4 branch of FreeBSD-src, that is based on FreeBSD branch releng/11.0.

I'll ask Luiz about cherry-picking it