opnsense / tools Goto Github PK

After adding the user 'dhcpd' to the system, the dhcp server is able to start. Beforehand no dhcpd can be enabled

tested on nano img: LibreSSL 15.9. amd64

After managing to burn the image, which is only possible from Linux, the USB stick boots, but there is no installation menu, so it's impossible to use this image as an installer.

Following the process defined earlier in the 16.1 cycle, I now get

# make core-16.1.5
.MAKE.LEVEL.ENV=MAKELEVEL
ARCH=amd64
BLOCKSIZE=K
CCACHE_DIR=/var/db/ccache
CCACHE_LOGFILE=/var/log/ccache.log
CCACHE_PATH=/usr/bin:/usr/local/bin
CLICOLOR=YES
CONFIGDIR=/usr/tools/config/16.1
CONFIG_PKG=/usr/local/etc/pkg/repos/origin.conf
CONFIG_XML=/usr/local/etc/config.xml
COREDIR=/usr/core

...
# Rules section
# uPnPd rule anchor
anchor "miniupnpd"
Installing mpd4-4.4.1_2...
`-- Installing libpdel-0.5.3_6...
`-- Extracting libpdel-0.5.3_6: 100%
Extracting mpd4-4.4.1_2: 100%
Installing mpd5-5.8...
Extracting mpd5-5.8: 100%
Could not find package: ngattach
*** Error code 1

Stop.
make: stopped in /usr/tools

I can install mpd5 just fine from ports, so there seems to be some package issue.

Causes some issues and it is not really needed.

1. The aesni.ko module does not need cryptodev.ko
2. cryptodev should not be used when aesni is loaded as it slows down OpenSSL a lot
3. cryptodev is required by some encryption hardware only

So, by removing cryptodev from the kernel, people on recent X86 hardware will benefit from better encryption speed.

1. The GUI should only add the aesni.ko module to the boot sequence when AES acceleration is selected
2. When alternative hardware is selected, cryptodev could be always loaded or a whitelist/blacklist could be built

Thoughts?

Isn't needed very often, but is useful in the RC phase

WITHOUT_UNBOUND=1

probably freeradius?

via: https://forum.opnsense.org/index.php?topic=2441.0

I've been trying to build opnsense and I'm getting this error : http://pastebin.com/dLgrTVuC
Can you guys help me fix it?

• /usr/local/opnsense/version/kernel and /usr/local/opnsense/version/base
• use the newer markers in the opnsense-update utility
• use the newer markers when building images
• weave this into the rename build script
• add opnsense-update, opnsense-update.base and opnsense-update.kernel to obsoleted files
• remove older markers for builds after 17.1.4

Switch version to 2.4 in the next release.

Without gems, the change breaks nothing and most gems are already patched to be compatible.

Install squid and start

but error could not find package squide

error code 1

• break out repository variables to allow softcoding through a config
• update/checkout scripts for reproducible release builds (tagged versions)

IDK how long i386 will be supported, so this may be an irrelevant issue.

pkg repo for 17.1 does not have following binaries:
www/py-searx -> Anonymous, self-hosted meta search engine
security/obfsclient -> Packet obfuscator for SOCKS
security/tcpcrypt: Alternatively, www/privoxy as plugin upstream to squid could be a better option due to TLS support soon to embedded into privoxy.

Personally, I would place all above in jails, and I'm sure that feature is under consideration...
Regards.

The iso.sh script looks for tha name opnsense where the master tag uses opnsense-devel.

Workaround is very simple, just replace:
-setup_packages ${STAGEDIR} opnsense
+setup_packages ${STAGEDIR} opnsense-devel

But this probably needs to be fixed in the make file somewhere...

pkg(8) seems like the convenient way to also push base system upgrades. Need to refine that into something useable. General idea is to wrap the kernel/base sets into a package including an update script, "install" it via the GUI, then trigger the actual system upgrade and finally clean up the package.

This is straight from the router, not from a VM.

[02.02.2016 14:11:48  /usr/core]
root@base # git pull --rebase
remote: Counting objects: 469, done.
remote: Compressing objects: 100% (284/284), done.
remote: Total 469 (delta 297), reused 126 (delta 126), pack-reused 52
Receiving objects: 100% (469/469), 185.29 KiB | 200.00 KiB/s, done.
Resolving deltas: 100% (304/304), completed with 39 local objects.
From https://github.com/opnsense/core
   35a1118..e6ee842  master     -> origin/master
   a3ea380..5560803  stable/16.1 -> origin/stable/16.1
 * [new tag]         16.1.1     -> 16.1.1
First, rewinding head to replay your work on top of it...
Fast-forwarded master to e6ee8423801c13e636d81ed29ab398ce2db287a1.

[02.02.2016 14:11:55  /usr/core]
root@base # cd ../tools/

[02.02.2016 14:12:04  /usr/tools]
root@base # make core
.MAKE.LEVEL.ENV=MAKELEVEL
ARCH=amd64
BLOCKSIZE=K
CONFIGDIR=/usr/tools/config/16.1
CONFIG_PKG=/usr/local/etc/pkg/repos/origin.conf
CONFIG_XML=/usr/local/etc/config.xml
COREDIR=/usr/core
CPUS=4
EDITOR=vi
GROUP=wheel
HOME=/root
HOSTTYPE=FreeBSD
IMAGESDIR=/tmp/images
LABEL=OPNsense
LOGNAME=root
MACHTYPE=x86_64
MAIL=/var/mail/root
MAKEFLAGS= .MAKE.LEVEL.ENV=MAKELEVEL
MAKELEVEL=1
OLDPWD=/usr/tools
OSTYPE=FreeBSD
PACKAGESDIR=/.pkg
PAGER=less
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin
PLUGINSDIR=/usr/plugins
PORTSDIR=/usr/ports
PORTSREFDIR=/usr/freebsd-ports
PRODUCT_FLAVOUR=OpenSSL
PRODUCT_NAME=OPNsense
PRODUCT_PRIVKEY=/root/repo.key
PRODUCT_PUBKEY=/root/repo.pub
PRODUCT_RELEASE=OPNsense-201602021412-OpenSSL
PRODUCT_SETTINGS=16.1
PRODUCT_TYPE=opnsense-devel
PRODUCT_VERSION=201602021412
PWD=/usr/tools/build
SETSDIR=/tmp/sets
SHELL=/usr/local/etc/rc.initial
SHLVL=1
SRCDIR=/usr/src
SSH_TTY=/dev/pts/0
STAGEDIR=/usr/obj/stage
TARGETARCH=amd64
TARGET_ARCH=amd64
TERM=xterm
TOOLSDIR=/usr/tools
USER=root
VENDOR=amd
>>> Setting up stage in /usr/obj/stage
>>> Setting up world in /usr/obj/stage
tar: Option -f requires an argument
Usage:
  List:    tar -tf <archive-filename>
  Extract: tar -xf <archive-filename>
  Create:  tar -cf <archive-filename> [filenames...]
  Help:    tar --help
*** Error code 1

Stop.
make: stopped in /usr/tools

Hey guys, this isn't really a problem but anyway, I wanted to build opnsense along with Freeswitch, how can I do it? On their website they have a script which can be used to install it, here it is :

pkg install autoconf automake curl git gmake jpeg ldns libedit libtool openssl pcre pkgconf speex sqlite3 wget sudo
mkdir ~/src
cd ~/src
git clone -b v1.4 https://freeswitch.org/stash/scm/fs/freeswitch.git

cd freeswitch
./bootstrap.sh -j
./configure
gmake
sudo gmake install cd-sounds-install cd-moh-install

If you could help me add this script to the build process somehow, it'll be amaazing (:

EDIT : When I try to install some packages listed above, it doesn't allow me, shows the error :

pkg: No packages available to install matching '[PACKAGENAME]' have been found in the repositories

if we are adding AV (see plugins), yara would be nice as well:

https://www.freshports.org/security/yara/

This is trivial at first sight, but we should make sure this does not transport to the final installation.

Workaround:

1. Escape to loader prompt (3)
2. Type: set kern.cam.boot_delay="10000"
3. Type: boot

Reported by: @lattera on APU2

You are packing up and the port is not properly completed.'

error code 1

the ports build didi not finish properly error code 1 STOP

We want to take libressl for a spin. Preliminary tests look good, build fixes for the ports tree have been proposed, but need to be reviewed and tested. In order to make the switch we go the long way of:

1. Use OpenSSL from ports (done).
2. Add openssh-portable to ports (done).
3. Use openssh-portable plus fallback if base version is available (done).
4. Remove OpenSSH from base (done).
5. Disable OpenSSL (WITHOUT_CRYPT) in the base system. (oh joy: Kerberos, fetch, etc.)
6. Use libressl from ports as soon as FreeBSD has coped with the open PRs.

I intend to do a little work on a potential plug in for 'pre processing' incoming connections for E-Mail, specifically port 25 - but that may extend. The initial plan is to take much of this from the Postfix application. There is no plan at this stage to do any content processing, the intention is mainly to prevent unnecessary and inappropriate connections ever reaching a mail server.

It has been suggested that I request the 'ports package' with this in mind and so I am doing so.

It'd be nice to use Poudriere rather than the custom ports build script that's being used. Using poudriere would also let us keep track of which ports built and which didn't.

for soekris amd64

2GB image is too small for updates when there is not enough RAM available.

According to UPDATING 20131108: WITHOUT_ATF is replaced by WITHOUT_TESTS

I have created a virtual machine running FreeBSD 11 and followed all instructions from the readme but I cloned my own core repository and checked out my own branch which is based on master (important).

If I run make cdrom it answered with branches which does not match. I have to checkout stable/17.1 in plugins and src and then I am able to run make cdrom.

But I want to use master, because I am working on a new feature.

One may have to modify the Makefile so you can use your own branch without these workarounds.

from https://github.com/HardenedBSD/opnsense-tools/commits/master

I according to your production step by step step by step to appear a mistake to ask how to deal with

help me please

Hey guys, I wanted to try building the asterisk port whilst building, as you guys said in another post I added asterisk to ports.conf in tools.git and added 'asterisk /' to core/Makefile, but when I try to run asterisk after building, it doesn't seem to contain asterisk..what am I doing wrong here? How do I install ports I need extra during the build?