Messages

1

18.1 Legacy Series / Re: How to test the development version

« on: January 15, 2017, 06:28:52 am »

Thanks!
I have a new issue when building:

Code: [Select]

>>> Setting up /usr/core copy in /usr/obj/usr/tools/config/17.1/OpenSSL:amd64
fatal: ambiguous argument 'stable/17.1': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
*** Error code 128

Stop.
make: stopped in /usr/tools
There is core folder mentioned, i have forked its master branch to my own repo and made some minor changes in code. Could that be a cause of tools build failure?

2

18.1 Legacy Series / Re: How to test the development version

« on: January 14, 2017, 09:01:34 am »

Hi! I want to try develop some additions to opnsense Web Proxy module and append sssd package/plugin. How should I build current 17.1 images from sources for testing? There are instructions for building 16.7 on github.com/opnsense/tools page, when I follow them, make cdrom says:

Code: [Select]

>>> Running build step: ports
>>> /usr/src does not match expected branch: stable/16.7
>>> To contunue anyway set SRCBRANCH=master
*** Error code 1And if I set SRCBRANCH to master, build fails on ngattach, which afaik shouldn't be there for 17.1 (link).

Btw, 2 more questions:
- Should building vm have exactly 6 GB of RAM as said on tools page, or I can assign, for example, 5,5? My pc has only 8 and goes slow.
- For building 17.1 should I use FreeBSD 10.3 or 11.0?

3

16.7 Legacy Series / Re: Upgrading to 16.7, known issues and workarounds

« on: January 11, 2017, 11:56:47 am »

from the web interface ( System ---Administration ) have you already tried to set Primary Console to VGA console?

Worked, thanks! It was set to serial. But, upgrade procedure shouldn't change primary console, isn't it?

4

16.7 Legacy Series / Re: Upgrading to 16.7, known issues and workarounds

« on: January 10, 2017, 11:41:27 am »

Hello. Just made a clean install and then upgraded to 16.7.13 through SSH. After reboot a console freezes right after displaying interface binding, but all services and ssh are ok. You can see in attached pictures. How I can fix a console?

5

17.1 Legacy Series / Re: Windows AD and SSO

« on: January 09, 2017, 01:02:38 pm »

Join to voljek's question. Absolutely same issue, can't join domain neither through web-gui, nor through kinit/msktutil. Please, help