rsasper,

I'd be willing to help you merge your improvements into the 2.0 baseline.  I've been wanting to implement an update accelerator functionality myself so I'd like to help just integrate yours into 2.0 instead if you'd like the help.  I believe something such as an update accelerator would be best suited as an add-on package though.

If you'd like the assistance let me know.

Regards,
Ron

I don't have anything setup to test l7 so I can't reproduce the errors - if you can, that's the kind of feedback the ticket needs.

Our pf is different, check patches in tools repo at rcs.pfsense.org.

The one in 2.0 is not possible to be in FreeBSD because we patch heavily ipfw and some parts of the kernel to implement some features.

Nobody really uses the dev iso anymore, just use a stock FreeBSD 7.2 VM/system for building items for pfSense 1.2.3.

At one point they broke, and nobody cared enough to fix them, so they were discontinued.

There is a rule setup by default in pfSense that blocks IPv6, but there is also an option to disable that rule, which you can use if you want to try testing IPv6 on it.  It is in System: Advanced.  The underlying system supports IPv6, but the pfSense web gui does not (yet), so you can't use it for configuring IPv6 addresses or rules.

Last I heard, you still need patches to build in a jail, but the patches haven't been maintained. I don't know if any of the devs are still using jails. Most of us use Virtual Machines for building now. VMware and VirtualBox both work. VirtualBox even works well directly on FreeBSD (I use it on my BSD workstation)

cd /home/pfsense/tools/pfPorts/php5/ && make all install clean
cd /home/pfsense/tools/pfPorts/php5-pfSense-module/ && make all install clean

Then run the build again.

You could start by making your own local copy of the repository by cloning it with Git and committing your changes to your local repository as you work on it.  When you have some changes to share, you could make a publicly available clone on https://rcs.pfsense.org/ (which is where the main pfSense repositories also reside) and push your changes.  For testing your changes, a system (either physical or virtual) with a full install would be useful so you could use gitsync to apply your changes to your test system (playback gitsync from the developer shell on the console menu).

Some useful documents for a new pfSense developer:
http://devwiki.pfsense.org/DeveloperRules
http://devwiki.pfsense.org/GitWorkflow

If you do any development, it should be done on recent 2.0 snapshot builds (except if you are trying to make a package for 1.2.3).

Apologize.  It was blocked by my filter (dansguardian).  I will fix this and try again.

It looks like you already created a ticket for this a couple weeks ago:
http://redmine.pfsense.org/issues/556

You might look at the haproxy package. I think I saw someone mention that you can pick a CARP IP from a drop-down in that package.

Right, I stop building right now, but I will try later. Thanks

I fix the problem
edit the file pfPorts/php4/Makefile.ext
change line 47
LIB_DEPENDS+=  curl.5:${PORTSDIR}/ftp/curl
TO
LIB_DEPENDS+=  curl.6:${PORTSDIR}/ftp/curl

Everything's ok!

The load balancing is done in pf, and it has to happen so fast that there is not enough time to take any of that into consideration. It may work on slow connections but it likely wouldn't scale well.

Ideas like that are easy to dream up, but much harder to actually implement. :-)

It's not dead, it's firewalled. That is a private cvsup server.

Just pick any of the public FreeBSD cvsup mirrors and use one :)

Support for the developer ISO has been broken for quite some time and I don't believe anyone is working on a fix.

Yep, /etc/version does the main version and /etc/platform will also get you pfSense (full install) or nanobsd (embedded) or cdrom, too.

That may help if you need to have specific code checks for nanobsd/embedded.

They are in the tools repo on the pfSense gitorious site:

http://rcs.pfsense.org/

Once you have downloaded a clone of the tools repo with git, they are under builder_scripts/conf/

There are different files for different versions (embedded, full, 64 bit, etc)