>>> Ports with failures:        0 >>> Building athstats...Done! >>> Building tools/crytpo...Done! ==> End of pfPorts... >>> Operation ./build_pfPorts.sh has ended at Mon Feb 21 21:19:43 EST 2011

All good now. Make sure you do a "portsnap fetch extract" after updating the git repos, or update your ports with csup. Also make sure you have a good and current version of autoconf and autoconf-wrapper installed.

The Developer ISO was discontinued, as none of the developers used it any longer. We all build things in a VM or jail based on the same OS as the pfSense install being worked on, and then move binaries over to the firewall.

Setup a VM for FreeBSD 7.2 and you can probably compile the driver fine there, and move over the resulting .ko file to the firewall.

If you have a driver issue, you're better off trying out 2.0 at this point to see if it behaves any better.

Ok, i managed to add it correctly i think…
It now shows up in the dyndns provider list, and checks return codes correctly. And noip is not fake anymore.

The only problem i had is that here at work we use 200.0.0.0/16 for lan (used as WAN in pfsense), and this ip is not correctly detected as private by is_private_ip(). are we incorrectly using this ip class or is the is_private_ip function wrong?

Sorry if i don't provide a diff against sources, but i'm not a developer i just have basic "change existing code" skills.
I copied back and forth the files using ssh and edited them.

The version the original files come from is 2.0-BETA5 (i386) built on Sun Jan 16 21:23:13 EST 2011:

/etc/inc/dyndns.class
/usr/local/www/services_dyndns.php
/usr/local/www/services_dyndns_edit.php

dyndns.class.txt
services_dyndns.php.txt
services_dyndns_edit.php.txt

You already asked a similar question in the captive portal forum. Please don't cross-post the same question to multiple boards.

Adding this pointer to the FAQ since this thread comes up high in Google results.
http://doc.pfsense.org/index.php/Can_I_sell_pfSense

Thank you. Now it is clear why it fails.

Found port location /usr/ports/www/pecl-APC.
Copying pfPorts/usr/ports/www/pecl-APC and building…
Building pecl-APC
Building port pecl-APC
*** Error code 1
Found port location /usr/ports/math/php52-bcmath.
Copying pfPorts/usr/ports/math/php52-bcmath and building...
Building php52-bcmath
Building port php52-bcmath
*** Error code 1
Found port location /usr/ports/archivers/php52-bz2.
Copying pfPorts/usr/ports/archivers/php52-bz2 and building...
Building php52-bz2
Building port php52-bz2
*** Error code 1
Found port location /usr/ports/textproc/php52-ctype.
Copying pfPorts/usr/ports/textproc/php52-ctype and building...
Building php52-ctype
Building port php52-ctype
*** Error code 1
Found port location /usr/ports/ftp/php52-curl.
Copying pfPorts/usr/ports/ftp/php52-curl and building...
Build dependency curl of php52-curl
Building curl
Building port php52-curl
Building php52-curl
Building port php52-curl
*** Error code 1
Found port location /usr/ports/devel/php52-gettext.
Copying pfPorts/usr/ports/devel/php52-gettext and building...
Building php52-gettext
Building port php52-gettext
*** Error code 1
Found port location /usr/ports/net/php52-ldap.
Copying pfPorts/usr/ports/net/php52-ldap and building...
Building php52-ldap
Building port php52-ldap
*** Error code 1
Found port location /usr/ports/converters/php52-mbstring.
Copying pfPorts/usr/ports/converters/php52-mbstring and building...
Building php52-mbstring
Building port php52-mbstring
*** Error code 1
Found port location /usr/ports/security/php52-mhash.
Copying pfPorts/usr/ports/security/php52-mhash and building...
Build dependency mhash of php52-mhash
Building mhash
Building port php52-mhash
Building php52-mhash
Building port php52-mhash
*** Error code 1

i search in google and nothing related.

You ahve to configure through ipfw and just load dummynet module.
Than pipe/queue numbers can be used in pf rules.

You can do this from the port itself no need to do that in the C sources.
Just hack up the Makefile of the port.

Most of what you want to know has already been covered in our documentation:

http://doc.pfsense.org/index.php/Can_I_sell_pfSense

http://doc.pfsense.org/index.php/What_license_does_pfSense_use%3F

http://www.pfsense.org/index.php?option=com_content&task=view&id=42&Itemid=62

https://rcs.pfsense.org/projects/pfsense

https://rcs.pfsense.org/projects/pfsense-tools

Look in /etc/inc/auth.inc for starters.

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.