1. The main goal of BSDRP is not firewalling but routing. If you are looking for a firewall, or for sharing your Internet access, don't use BSDRP but use pfSense, OPNsense, SmallWall or t1n1wall, instead.
2. BSDRP doesn't have a Web GUI: It's to be configured from a CLI only (like Cisco/Juniper), or by an API (like netconf) [planned feature]
3. BSDRP is not intended for home use but for company use (small ISP as example).

It depends on your hardware:

• 4 cores Atom with with multi-queue aware NIC is the minimum for a line-rate gigabit router (1.48Mpps of smallest packet size).
• 8 core Xeon is the minimum for a 10Gigabit Full-Duplex (10Gbps receiving + 10Gbps transmitting = 20Gbps) with IMIX packet size distribution
• 12 core Xeon is needed for a 10Gb line-rate router (14.8Mpps)

A server designed to support 40Gb/s of bidirectional traffic could almost support IPFW in stateless mode but not pf neither ipf:

It depends of your hardware and crypto algorithms used:

It depends of your hardware and crypto algorithms used, but a userland software it will be almost half lower than IPSec:

BSDRP targets x86 architectures only.

ZRouter.org targets ARM and MIPS architectures.

The technical issues regarding the support of ARM/MIPS architectures with BSDRP are:

1. Be able to modify the bootloader (for changing the boot-partition) from the FreeBSD user space: Permit to switch the active partition after an upgrade
2. Having a bootloader that support a minimum boot-partition selection screen: Permit to revert-back to the previous version if the new installed version has major problem.

All features not related to routing will not be added into the base of BSDRP (but installing or removing FreeBSD packages is still possible).

No forum planned..