We are focusing on a number of last minute release issues. We’ll have updates posted again soon. Sorry for the delay!
Archive for 2005
Now that the feature freeze has been lifted, I will be making a push over the next few days to merge the new package code I’ve been working on into HEAD. The following features are among those currently planned for initial inclusion:
- Multiple package repositories
- Although the pfSense team will continue to run an ‘official’ repository, the package system will be moving to a more decentralized model. Any user may create their own repository XML file using the repomaker tool (check tools/repomaker in HEAD).
Important! We need users that previously had problems installing with the Installer to try this version!
New features include:
- Polling support per interface. Supported interfaces: em, fxp, ixgb, nge, re, vge, dc, rl, sf, sis, ste, vr, xl. This should speed up networking quite a bit.
- Port aliases are fixed
- HTTPS Captive portal fix
- Incoming FTP should be fixed (NAT Port forwads)
- Fixed auth issues
- USB Keyboard fixed
- Installer allows overriding the disk geometry
- Captive portal login count on status page
- Package services stopped correctly upon deinstall
There seems to be a lot of confusion over just what the RELENG_1 tag in CVS means.
We’re taking a similar approach as the FreeBSD project in our CVS tagging. Commits now are all made to HEAD, which is developer-use-only now. After a certain period, these changes are MFC’ed into the tag RELENG_1. MFC is Merged From -CURRENT. HEAD in CVS is basically like FreeBSD’s -CURRENT, though generally we don’t refer to it as such. We use the same term, MFC, because that’s what we’re used to.
All public releases from this point on will be made from RELENG_1. This will eventually help us stabilize releases without slowing development, as known-unstable code and features will remain in HEAD.
This doesn’t mean much of anything at this point other than we’re getting closer to the first beta! FreeBSD 6.0 RC1 is out and is likely to be the only RC. 6.0 release is expected within a couple weeks or so. We should hit beta shortly after that, but no promises.
I just sent out this message to our developers list. This is great news!
Alright guys, a major milestone was just reached. RELENG_1. I have
branched the trunk of pfSense so the feature freeze is now lifted for
I will be handling MFC’s to the RELENG_1 tree so if you have a commit
that needs MFC’d back to RELENG_1 (only bug fixes) then please label
in the commit something similar to freebsd. Something like:
MFC: In 1 day
I will merge stuff back to RELENG_1 on a daily basis as needed.
So without further due, go ahead and commit and lets get some new
features in HEAD!
We changed DNS servers last night. Other than stale caches affecting the resolving of our new FAQ FQDN, it was a transparent transition.
If you can’t resolve faq.pfsense.org/com/net, flush your DNS server’s cache. If you don’t control your DNS server, you’ll just have to wait until the cached entries expire.
The new NS records are park17.secureserver.net and park18.secureserver.net.
We currently have deployed all the mirrors we are going to use at this point. The load spread across the mirrors is relatively minimal for the connectivity available. Please hold off on any mirror offers for now.
After we reach 1.0 release, we may need to add some to deal with increased loads, but we’re in good shape for now.
Thanks to all those who have offered!
0.86 is now making it’s way to a mirror near you. Changes since 0.85ish include:
- A new console option to aide in transferring config.xml to a removable media device for livecd users
- Multiple WAN fixes for port-forwards
- Ajaxification of the main status page meters and stats
- Many new games and resources added to the traffic shaper ez shaper wizard
- DNS fixes for DHCP
- New wireless from lsf with many options such as wpa_supplicant
- Cleaned up CARP/PFSync startup process quite a bit and closed a bug when traffic shaping is enabled
- Captive portal pass through mac entries should always exist and allow the traffic. The reason for this is because we do not have native mac address filtering mechanisms. this allows us to filter by mac address easily and get around this limitation. I consider this a bug in m0n0wall and pfSense as m0n0wall does not have native mac filtering mechanisms as well.
- NAT encapsulated IPV6 may work now? Needs more testing.
- Fixed handling of aliases in many cases
- and much more…
We recently switched to LightTPD and are having a number of issues now with firmware upload. We’re working on fixing it. Until then, please download from our old location.
Please help us welcome Seth Mos to the team! Seth has corrected countless bugs so far.