hhm ok after some testing around i will come to the result that i need to change some sed command's inside the builder_common.sh

after changing all sed ""  (all sed's with double quotes) to sed (without double quotes) it works and the errors are gone :)

sed ""
change to
sed

example:
sed "" -e /ttyd0/s/off/on/ ${PFSENSEBASEDIR}/etc/ttys
change to
sed -e /ttyd0/s/off/on/ ${PFSENSEBASEDIR}/etc/ttys

now the pfSense 2.0.1-RELEASE-nanobsd (i386) with vga is booting yoohooo :)

hope someone else can need this info

best regards
ren22

portsnap fetch && portsnap extract
cd /home/pfsense/tools/builder_scripts
./clean_build.sh
./set_version.sh RELENG_8_1 cvsup.de.freebsd.org
./update_git_repos.sh
./apply_kernel_patches.sh
./build_iso.sh
./build_nano.sh

Using /usr/home/pfsense/tools/builder_scripts/remove.list.iso.8 …
Operation ./build_nano.sh has started at Sat Nov 19 21:10:51 CET 2011

Remove list: /usr/home/pfsense/tools/builder_scripts/remove.list.iso.8
                  Copy list: /usr/home/pfsense/tools/builder_scripts/../builder_scripts/copy.list.RELENG_8_0
            MAKEOBJDIRPREFIX: /usr/obj.pfSense
          pfSense build dir: /usr/pfSensesrc/src
            pfSense version: 2.0-RELEASE
                    CVS User: sullrich
                  Verbosity:
                    BASE_DIR: /usr/home/pfsense/tools/builder_scripts/../..
                    BASEDIR: /usr/local/pfsense-fs
                Checkout dir: /usr/home/pfsense/tools/builder_scripts/../../pfSense
                Custom root: /usr/home/pfsense/tools/builder_scripts/../../pfSense
              CVS IP address: cvs.pfsense.org
                Updates dir: /tmp/builder//updates
                pfS Base dir: /usr/local/pfsense-fs
              FreeSBIE path: /usr/home/pfsense/tools/builder_scripts/../../freesbie2
              FreeSBIE conf: /dev/null
                  Source DIR: /usr/pfSensesrc/src
                  Clone DIR: /usr/local/pfsense-clone
              Custom overlay:
            pfSense version: 8
              FreeBSD branch: RELENG_8_1
                pfSense Tag: RELENG_2_0
                EXTRAPLUGINS: customroot
                EXTRAPLUGINS: customscripts
                EXTRAPLUGINS: pkginstall
                EXTRAPLUGINS: buildmodules
            MODULES_OVERRIDE: i2c
            MODULES_OVERRIDE: ipmi
            MODULES_OVERRIDE: acpi
            MODULES_OVERRIDE: ndis
            MODULES_OVERRIDE: ipfw
            MODULES_OVERRIDE: ipdivert
            MODULES_OVERRIDE: dummynet
            MODULES_OVERRIDE: fdescfs
            MODULES_OVERRIDE: cpufreq
            MODULES_OVERRIDE: opensolaris
            MODULES_OVERRIDE: zfs
            MODULES_OVERRIDE: glxsb
            MODULES_OVERRIDE: runfw
            MODULES_OVERRIDE: if_stf
              Git Repository: https://github.com/bsdperimeter/pfsense.git
                  Git Branch:
              Custom Config:
                    ISOPATH: /tmp/builder//pfSense.iso
                    IMGPATH: /tmp/builder//pfSense.img
                MEMSTICKPATH: /tmp/builder//pfSense-memstick.img
                  KERNELCONF:
        TARGET_ARCH_CONF_DIR: /usr/pfSensesrc/src/sys/i386/conf/
    FREESBIE_COMPLETED_MAIL:
        FREESBIE_ERROR_MAIL:
                    OVFPATH: /tmp/builder/
                    OVFFILE: pfSense.ovf
                    OVAFILE: pfSense.ova
                    OVFVMDK: pfSense.vmdk
                  OVFSTRINGS:
                      OVFMF:
                    OVFCERT:
                    SRC_CONF: /usr/home/pfsense/tools/builder_scripts/conf/src.conf.embedded.8
CROSS_COMPILE_PORTS_BINARIES:
            SPLIT_ARCH_BUILD:
    UPDATES_TARBALL_FILENAME: /tmp/builder//updates/pfSense-Full-Update-2.0-RELEASE-i386-20111119-2110.tgz
        PKG_INSTALL_PORTSPFS:
  CUSTOM_CALL_SHELL_FUNCTION:

Cleaning build directories: pfsense-fs pfsense-clone Done!
Using GIT to checkout RELENG_2_0
Checking out tag RELENG_2_0...Done!
Making sure we are in the right branch... [OK] (RELENG_2_0)
Creating tarball of checked out contents…Done!
Building world and kernels for Embedded... 8  RELENG_8_1 ...
+++ NO_BUILDWORLD set, skipping build
Ensuring that the btxld problem does not happen on subsequent runs...
Installing world for i386 architecture...
Making hierarchy
Installing everything
Building embedded VGA kernel...
Not adding D-Trace to Kernel...
KERNCONFDIR: /usr/pfSensesrc/src/sys/i386/conf
ARCH:        i386
SRC_CONF:    src.conf.embedded.8
Kernel build for pfSense_wrap_vga.8.i386 started on Sat Nov 19 21:11:25 CET 2011
stage 1: configuring the kernel
stage 2.2: rebuilding the object tree
stage 2.3: build tools
stage 3.1: making dependencies
stage 3.2: building everything
Kernel build for pfSense_wrap_vga.8.i386 completed on Sat Nov 19 21:11:55 CET 2011
Installing embedded VGA kernel...
Installing kernel
Installing kernels to LiveCD area....done.
Phase populate_extra...
Making devd... Done.
Mounting devfs /usr/local/pfsense-fs/dev ...
Merging extra items...
Running plugins: customroot customscripts pkginstall buildmodules Done!
Using /usr/home/pfsense/tools/builder_scripts/../builder_scripts/copy.list.RELENG_8_0...
Populating newer binaries found on host jail/os (usr/local)...
Installing collected library information (usr/local), please wait...
Fixing up NanoBSD Specific items...
Creating md5 summary of files present...Done.
Copying config.xml from conf.default/ to cf/conf/
Testing PHP installation in /usr/local/pfsense-fs: FCGI-PASSED PASSED  [OK]
Installing packages listed in /tmp/pfspackages
Finding origins… 2 found
Finding dependencies... 2 found
Sorting 4 packages by dependencies... done.
Copying 4 packages
[0….]
Cloning /usr/local/pfsense-fs to /usr/local/pfsense-clone…Done!
Using TAR to clone...
Deleting files listed in /usr/home/pfsense/tools/builder_scripts/remove.list.iso.8
[nanoo] sandisk 1g
[nanoo] NANO_MEDIASIZE: 1947518
[nanoo] NANO_HEADS: 16
[nanoo] NANO_SECTS: 63
[nanoo] NANO_BOOT0CFG: -o packet -s 1 -m 3
Configuring NanoBSD /etc
Configuring NanoBSD setup
Using TAR to clone setup_nanobsd()…
Pruning NanoBSD usr directory...
building NanoBSD disk image (i386)...
30912+0 records in
30912+0 records out
997097472 bytes transferred in 15.441514 secs (64572520 bytes/sec)
******* Working on device /dev/md0 *******
fdisk: invalid fdisk partition table found
fdisk: Class not found
******* Working on device /dev/md0 *******
parameters extracted from in-core disklabel are:
cylinders=1932 heads=16 sectors/track=63 (1008 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=1932 heads=16 sectors/track=63 (1008 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
    start 63, size 922257 (450 Meg), flag 80 (active)
        beg: cyl 0/ head 1/ sector 1;
        end: cyl 914/ head 15/ sector 63
The data for partition 2 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
    start 922383, size 922257 (450 Meg), flag 0
        beg: cyl 915/ head 1/ sector 1;
        end: cyl 805/ head 15/ sector 63
The data for partition 3 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
    start 1844640, size 102816 (50 Meg), flag 0
        beg: cyl 806/ head 0/ sector 1;
        end: cyl 907/ head 15/ sector 63
The data for partition 4 is:
<unused># /dev/md0s1:
8 partitions:
#        size  offset    fstype  [fsize bsize bps/cpg]
  a:  922241      16    unused        0    0
  c:  922257        0    unused        0    0        # "raw" part, don't edit
/dev/md0s1a: 450.3MB (922241 sectors) block size 4096, fragment size 512
        using 36 cylinder groups of 12.66MB, 3240 blks, 1632 inodes.
super-block backups (for fsck -b #) at:
32, 25952, 51872, 77792, 103712, 129632, 155552, 181472, 207392, 233312, 259232, 285152, 311072, 336992, 362912, 388832, 414752, 440672, 466592, 492512,
518432, 544352, 570272, 596192, 622112, 648032, 673952, 699872, 725792, 751712, 777632, 803552, 829472, 855392, 881312, 907232
Filesystem  1K-blocks Used  Avail Capacity  Mounted on
/dev/md0s1a    453327    1 417060    0%    /tmp/builder/.mnt
283395 blocks
Filesystem  1K-blocks  Used  Avail Capacity  Mounted on
/dev/md0s1a    453327 145586 271475    35%    /tmp/builder/.mnt

Mounting and duplicating NanoBSD pfsense1 /dev/md0s2a /tmp/builder//.mnt
7205+1 records in
7205+1 records out
472195584 bytes transferred in 33.322620 secs (14170422 bytes/sec)
Filesystem  1K-blocks  Used  Avail Capacity  Mounted on
/dev/md0s2a    453327 145586 271475    35%    /tmp/builder/.mnt
/dev/ufs/pfsense1 / ufs ro,sync,noatime 1 1
/dev/ufs/cf /cf ufs ro,sync,noatime 1 1
/dev/ufs/pfsense1 / ufs ro,sync,noatime 1 1
/dev/ufs/cf /cf ufs ro,sync,noatime 1 1
Creating /cf area to hold config.xml
/dev/md0s3: 50.2MB (102816 sectors) block size 4096, fragment size 512
        using 4 cylinder groups of 12.55MB, 3214 blks, 1632 inodes.
super-block backups (for fsck -b #) at:
32, 25744, 51456, 77168
34 blocks
[nanoo] Creating NanoBSD upgrade file from first slice…
7205+1 records in
7205+1 records out
472195584 bytes transferred in 31.662914 secs (14913207 bytes/sec)
Image completed.
/tmp/builder//
-rw-r--r--  1 root  wheel  951M Nov 19 21:13 /tmp/builder//nanobsd_vga.full.img
-rw-r--r--  1 root  wheel  450M Nov 19 21:14 /tmp/builder//nanobsd_vga.upgrade.img
Operation ./build_nano.sh has ended at Sat Nov 19 21:14:10 CET 2011</unused>

I figured it out by looking at one of the pre-recorded macros.

This isn't in the help or documentation anywhere.. I guess I'm the only person who ever got tripped up on it though!

@ermal:

There is rate limit on the login attempts a host can make.
So its not based on user but host sending login attempts. Its hardcoded in php code to 5 attempts in 15minutes but do not quote me on that.

That's the sort of thing I'm looking for. If it were configurable for # attempts and # minutes for future, it would be nice. Also worth adding to the documentation if correct. While it allows multiple clients (which causes the limit to scale) it's not nearly enough for heavy duty brute force to be viable. Thanks. As to the others…? :)

Thanks jimp!

I see you updated http://doc.pfsense.org/index.php/Creating_Your_Own_Package_Repository already too, fantastic.

Still not recommended. There is no way to get all of the required compilers, headers, tools, etc, on there and still have a system one would consider secure and usable.

If you must share hardware, I'd suggest using a VM setup like ESX and make a pfSense VM and a separate VM for your other services.

May not take much to do really, it could be as simple as adding some sortable tags to the table there, as we have on many other pages.

Open a feature request ticket on redmine (set target version to 'future') and if someone gets a moment to look at it, it may be easy.

Thanks.
In the next months i plain made the subscription (very low money, everything starting from begin now) and i will request that.
Thank you for the anwser.

Best Regards.

https://github.com/bsdperimeter

All packages work that way. <config>is an array inside of a package like that. It's interpreted by the XML parser as an array, so it gets an array index.

Some packages have multiple configs (multiple tabs, etc) and rely on that.</config>

You can get the green_saver.ko from here:
http://files.pfsense.org/jimp/ko-8.1/

Place that in /boot/modules/ and then add it to /boot/loader.conf.local like so:
green_saver_load="YES"

That may be enough. If you need to tweak the time, install the shellcmd package and then setup a vidcontrol -t nnn command to change the timeout.

Hi,

I'm done with debugging of the voucher system.
Next week maybe i can provide more details about the key generation an the databases.
I had written a first "test-php-script" and it looks like it works.

Can somebody provide me the development documentation/scripts/sources (e.g. github ..)?
I have only found this: https://github.com/bsdperimeter/pfsense .

Work in Progress ….

:)

Is there anyone to answer my first question?

I do not think that will solve what you are after.
Mostly will break other things.

Check out the replies here.

I had the same question and just successfully requested the change to be made officially!

Thank you to both of you!

stephenw10: I have followed the steps you outlined and forked to source. I committed the changes and requested a merge, plus dropped an email to the core team.

richinspirit: Thank you, too! I have sent you the new files (3 all together) via email!

AFAIK FreeBSD supports only hardware virtualized (HVM) kernels on amd64; however, PV drivers are supported in this configuration.

The PHP one doesn't matter - we aren't moving to 5.3 yet and there is no fix for that on 5.2.x.

The syslog one isn't really relevant to how it's used on pfSense so again, doesn't really matter.

If there is a problem, we usually address it with custom patches or updating as needed.