Re: Forcing poudriere to rebuild a package and all dependencies

[Bryan Drewery]

On 8/26/2016 3:21 PM, Russell L. Carter wrote:
> Hi,
> 
> So I'm in the middle of jumping a herd of 6 boxen from 10.3 to 11, and

Upgrading/Replacing a poudriere jail from 10.3 to 11 normally would
rebuild all packages since there would either be no packages in the new
jail (if using a name such as 10-amd64 and 11-amd64), or it would
rebuild all packages for the major version updating (if you used a
simple jail name like 'foo').

So I'm not sure how you don't have all packages rebuilding in that case.

How did you upgrade your jail from 10.3 to 11?

> I can't find how to update necessary ports modules such as, but not
> limited to, the several nvidia kernel modules.  This information does
> not appear to be googleable, so let's correct that.
> 
> Here's my /usr/local/etc/poudriere.d/make.conf, which is indeed
> appended at the beginning of a poudriere bulk run:
> 
> WITH_OPENSSL_PORT=  yes
> OPENSSL_PORT=   security/openssl
> DEFAULT_VERSIONS=pgsql=9.5 php=7.0
> #  Set this to the list of ports you wish to rebuild every time the
> #  kernel is built.
> PORTS_MODULES=nvidia-driver-340  nvidia-driver virtualbox-ose-kmod
> sysutils/vm-bhyve sysutils/pefs-kmod
> DISABLE_LICENSES=yes
> 
> Simply rm'ing the package file does not work.  Ideas?  Otherwise, the
> upgrade is going fairly smoothly, kudos to the team.  I've had worse
> experiences with apt-get.
> 
> Thanks,
> Russell
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

Forcing poudriere to rebuild a package and all dependencies

[Russell L. Carter]

Hi,

So I'm in the middle of jumping a herd of 6 boxen from 10.3 to 11, and
I can't find how to update necessary ports modules such as, but not
limited to, the several nvidia kernel modules.  This information does
not appear to be googleable, so let's correct that.

Here's my /usr/local/etc/poudriere.d/make.conf, which is indeed
appended at the beginning of a poudriere bulk run:

WITH_OPENSSL_PORT=  yes
OPENSSL_PORT=   security/openssl
DEFAULT_VERSIONS=pgsql=9.5 php=7.0
#  Set this to the list of ports you wish to rebuild every time the
#  kernel is built.
PORTS_MODULES=nvidia-driver-340  nvidia-driver virtualbox-ose-kmod 
sysutils/vm-bhyve sysutils/pefs-kmod

DISABLE_LICENSES=yes

Simply rm'ing the package file does not work.  Ideas?  Otherwise, the
upgrade is going fairly smoothly, kudos to the team.  I've had worse
experiences with apt-get.

Thanks,
Russell
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Maintainership Status for PHP 5.6

[Kurt Jaeger]

Hi!

> I'm testbuilding 5.6.25 right now.

A patch is at

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212183

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Maintainership Status for PHP 5.6

[Kurt Jaeger]

Hi!

> > About resetting the maintainer, I'll ask around.

> The rules are pretty clear:
> https://www.freebsd.org/doc/en/books/porters-handbook/makefile-maintainer.html

It's more about: Who's willing to do it ?

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Maintainership Status for PHP 5.6

[Baptiste Daroussin]

On Fri, Aug 26, 2016 at 09:08:44PM +0200, Kurt Jaeger wrote:
> Hi!
> 
> > It's been a week since PHP 5.6.25 was released and it still has not hit the
> > ports system. This has been an ongoing problem for quite sometime now.
> 
> tz@ has ambitions with php, as he's maintaining php70. Maybe
> he finds the time...
> 
> feld@ also worked on some updates.
> 
> I'm testbuilding 5.6.25 right now.
> 
> > According to freshports commit log, the maintainer for PHP 5.6 hasn't made
> > a commit since November 2015.
> > 
> > What exactly is the status of maintainership for this port? Is it time for
> > the maintainership to be reset or changed?
> 
> We all try to move to php70 as fast as possible 8-}
> 
> About resetting the maintainer, I'll ask around.
> 
The rules are pretty clear:
https://www.freebsd.org/doc/en/books/porters-handbook/makefile-maintainer.html

Beside that the maintainer being active the best would be to talk to him :)

(I have CCed him)

Best regards,
Bapt


signature.asc
Description: PGP signature

Re: Maintainership Status for PHP 5.6

[Franco Fichtner]

Hi Kurt,

> On 26 Aug 2016, at 9:08 PM, Kurt Jaeger  wrote:
> 
> I'm testbuilding 5.6.25 right now.

Please please make sure to reset all the php56-* module's
port revisions to zero if you do commit.  This was missed
in the php70 bump.


Cheers,
Franco
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Maintainership Status for PHP 5.6

[Kurt Jaeger]

Hi!

> It's been a week since PHP 5.6.25 was released and it still has not hit the
> ports system. This has been an ongoing problem for quite sometime now.

tz@ has ambitions with php, as he's maintaining php70. Maybe
he finds the time...

feld@ also worked on some updates.

I'm testbuilding 5.6.25 right now.

> According to freshports commit log, the maintainer for PHP 5.6 hasn't made
> a commit since November 2015.
> 
> What exactly is the status of maintainership for this port? Is it time for
> the maintainership to be reset or changed?

We all try to move to php70 as fast as possible 8-}

About resetting the maintainer, I'll ask around.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Maintainership Status for PHP 5.6

[Ken]

Hey guys,

It's been a week since PHP 5.6.25 was released and it still has not hit the
ports system. This has been an ongoing problem for quite sometime now.

According to freshports commit log, the maintainer for PHP 5.6 hasn't made
a commit since November 2015.

What exactly is the status of maintainership for this port? Is it time for
the maintainership to be reset or changed?

Ken
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Gimp 2.8.18,2 plugins not working under 10.3

[scratch65535]

[Default] On Mon, 22 Aug 2016 04:07:25 -0700 (PDT), Don Lewis
 wrote:

>
>sysctl kern.ipc.shm_allow_removed=1

That seems to have done the trick.  Thanks!

I hope the maintainer fixes the problem more generally, though.  
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: problem installing ports

[Robert Huff]

On 8/26/2016 7:42 AM, Robert Huff wrote:


Let me guess, you have (NFSv4) ACLs enabled somewhere.  The HEAD was
supposedly fixed in r304075, but the change still was not merged to
stable/11.


 Yes, on the filesystem that holds WRKDIRPREFIX.
 Is it as simple as that?   (And is there a PR number?)


Apparently, it is.
Thanks for the helo.


Madly compiling away,


Robert Huff



___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Committers needed

[Kurt Jaeger]

Hi!

> > https://bugs.freebsd.org/211663
> > https://bugs.freebsd.org/211664
> > https://bugs.freebsd.org/211573
> > https://bugs.freebsd.org/211624

Done, with 211624 pending MFH.

Tobias, does the change from 211624 mean that we can close the
two PRs 154502 191296 as fixed with a reference to 211624 ?

That's my take, but I'd like to have some confirmation before I closed
them as fixed.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: security/strongswan start=route issue

[Franco Fichtner]

> On 26 Aug 2016, at 3:54 PM, abi  wrote:
> 
> Strange indeed. Yes, I ping correctly and auto=start works flawless.
> 
> Is OPNsense tracking 10 branch? I'm on 11-RC1

Yes, it's on 10.3.  Can't say anything about the state of
11 in the next few weeks in that regard.  Sorry.


Cheers,
Franco
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: security/strongswan start=route issue

[abi]

Strange indeed. Yes, I ping correctly and auto=start works flawless.

Is OPNsense tracking 10 branch? I'm on 11-RC1


On 26.08.16 10:05, Franco Fichtner wrote:

Hi,


On 26 Aug 2016, at 9:00 AM, abi  wrote:

I'd like to open PR on upstream, but I want be sure that the problem exists not 
only for me, as the problem looks strange.
The issue is that tunnel behaves different if it autostarts (auto=start) and 
when it starts when traffic registered between left and right side. 
(auto=route).

This works fine in our OPNsense setups.

Make sure you use ping with the option "-S $LEFT_IP", it will
only auto-route local traffic that originates from within your
leftsubnet.


Cheers,
Franco


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: problem installing ports

[Robert Huff]

On 8/26/2016 7:33 AM, Konstantin Belousov wrote:


===>   Registering installation for dialog4ports-0.1.6
Installing dialog4ports-0.1.6...
Child process pid=6648 terminated abnormally: Bus error
*** Error code 138

Stop.

... and pkg-static drops a core file.
I get this (with different pids) for _every_ port on "make install".
Never seen this before.  Google offered no possible causes.
"Bus error" means a memory violation - and I have no idea how to
proceed.  The core file has no debugging symbols, making a backtrace
useless.



Let me guess, you have (NFSv4) ACLs enabled somewhere.  The HEAD was
supposedly fixed in r304075, but the change still was not merged to
stable/11.


Yes, on the filesystem that holds WRKDIRPREFIX.
Is it as simple as that?   (And is there a PR number?)


Boggled at the simplicity,


Robert Huff



___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: problem installing ports

[Konstantin Belousov]

On Fri, Aug 26, 2016 at 07:14:38AM -0400, Robert Huff wrote:
>   So ...
>   I replaced my 10.3/i386 system with:
> 
> FreeBSD 11.0-RC2 #0 r304729: Wed Aug 24 06:59:03 UTC 2016 
> r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
> 
>   and kernel+world are working.
>   Installing ports is a different matter.
>   1) I created /usr/ports and /usr/doc.
>   2) I "self-installed" pkg; this brought with it
> 
> apr-1.5.2.1.5.4_1
> db5-5.3.28_4
> expat-2.1.1_2
> gdbm-1.12
> gettext-runtime-0.19.8.1
> indexinfo-0.2.4
> readline-6.3.8
> serf-1.3.8_1
> sqlite3-3.13.0
> 
>   3) Next:
> 
> root@>> pkg install subversion
> 
>   which I used to populate the ports tree.
>   4) Now, to install portmaster.  That requires dialog4ports:
> 
> root@>>   make clean
> ===>  Cleaning for dialog4ports-0.1.6
> root@>>   make
> ===>  License BSD2CLAUSE accepted by the user
> ===>   dialog4ports-0.1.6 depends on file: /usr/local/sbin/pkg - found
> ===> Fetching all distfiles required by dialog4ports-0.1.6 for building
> ===>  Extracting for dialog4ports-0.1.6
> => SHA256 Checksum OK for dialog4ports-0.1.6.tar.gz.
> ===>  Patching for dialog4ports-0.1.6
> ===>  Configuring for dialog4ports-0.1.6
> ===>  Building for dialog4ports-0.1.6
> --- dialog4ports.o ---
> --- mixedlist.o ---
> --- dialog4ports.1.gz ---
> --- dialog4ports.o ---
> cc -O2 -pipe  -fstack-protector -fno-strict-aliasing -Wall -pedantic -c 
> dialog4ports.c -o dialog4ports.o
> --- mixedlist.o ---
> cc -O2 -pipe  -fstack-protector -fno-strict-aliasing -Wall -pedantic -c 
> mixedlist.c -o mixedlist.o
> --- dialog4ports.1.gz ---
> gzip -cn dialog4ports.1 > dialog4ports.1.gz
> --- dialog4ports ---
> cc -O2 -pipe  -fstack-protector -fno-strict-aliasing -Wall -pedantic 
> dialog4ports.o mixedlist.o -o dialog4ports -lncursesw -lm -ldialog
> ===>  Staging for dialog4ports-0.1.6
> ===>   Generating temporary packing list
> install   -m 555 dialog4ports 
> /data/port-work/usr/ports/ports-mgmt/dialog4ports/work/stage/usr/local/bin
> install  -m 0644 dialog4ports.1.gz 
> /data/port-work/usr/ports/ports-mgmt/dialog4ports/work/stage/usr/local/man/man1
> > Compressing man pages (compress-man)
> root@>>   make install
> ===>  Installing for dialog4ports-0.1.6
> ===>  Checking if dialog4ports already installed
> ===>   Registering installation for dialog4ports-0.1.6
> Installing dialog4ports-0.1.6...
> Child process pid=6648 terminated abnormally: Bus error
> *** Error code 138
> 
> Stop.
> 
>   ... and pkg-static drops a core file.
>   I get this (with different pids) for _every_ port on "make install".
>   Never seen this before.  Google offered no possible causes.
>   "Bus error" means a memory violation - and I have no idea how to 
> proceed.  The core file has no debugging symbols, making a backtrace 
> useless.
> 

Let me guess, you have (NFSv4) ACLs enabled somewhere.  The HEAD was
supposedly fixed in r304075, but the change still was not merged to
stable/11.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

problem installing ports

[Robert Huff]

So ...
I replaced my 10.3/i386 system with:

FreeBSD 11.0-RC2 #0 r304729: Wed Aug 24 06:59:03 UTC 2016 
r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64


and kernel+world are working.
Installing ports is a different matter.
1) I created /usr/ports and /usr/doc.
2) I "self-installed" pkg; this brought with it

apr-1.5.2.1.5.4_1
db5-5.3.28_4
expat-2.1.1_2
gdbm-1.12
gettext-runtime-0.19.8.1
indexinfo-0.2.4
readline-6.3.8
serf-1.3.8_1
sqlite3-3.13.0

3) Next:

root@>> pkg install subversion

which I used to populate the ports tree.
4) Now, to install portmaster.  That requires dialog4ports:

root@>>   make clean
===>  Cleaning for dialog4ports-0.1.6
root@>>   make
===>  License BSD2CLAUSE accepted by the user
===>   dialog4ports-0.1.6 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by dialog4ports-0.1.6 for building
===>  Extracting for dialog4ports-0.1.6
=> SHA256 Checksum OK for dialog4ports-0.1.6.tar.gz.
===>  Patching for dialog4ports-0.1.6
===>  Configuring for dialog4ports-0.1.6
===>  Building for dialog4ports-0.1.6
--- dialog4ports.o ---
--- mixedlist.o ---
--- dialog4ports.1.gz ---
--- dialog4ports.o ---
cc -O2 -pipe  -fstack-protector -fno-strict-aliasing -Wall -pedantic -c 
dialog4ports.c -o dialog4ports.o

--- mixedlist.o ---
cc -O2 -pipe  -fstack-protector -fno-strict-aliasing -Wall -pedantic -c 
mixedlist.c -o mixedlist.o

--- dialog4ports.1.gz ---
gzip -cn dialog4ports.1 > dialog4ports.1.gz
--- dialog4ports ---
cc -O2 -pipe  -fstack-protector -fno-strict-aliasing -Wall -pedantic 
dialog4ports.o mixedlist.o -o dialog4ports -lncursesw -lm -ldialog

===>  Staging for dialog4ports-0.1.6
===>   Generating temporary packing list
install   -m 555 dialog4ports 
/data/port-work/usr/ports/ports-mgmt/dialog4ports/work/stage/usr/local/bin
install  -m 0644 dialog4ports.1.gz 
/data/port-work/usr/ports/ports-mgmt/dialog4ports/work/stage/usr/local/man/man1

> Compressing man pages (compress-man)
root@>>   make install
===>  Installing for dialog4ports-0.1.6
===>  Checking if dialog4ports already installed
===>   Registering installation for dialog4ports-0.1.6
Installing dialog4ports-0.1.6...
Child process pid=6648 terminated abnormally: Bus error
*** Error code 138

Stop.

... and pkg-static drops a core file.
I get this (with different pids) for _every_ port on "make install".
Never seen this before.  Google offered no possible causes.
	"Bus error" means a memory violation - and I have no idea how to 
proceed.  The core file has no debugging symbols, making a backtrace 
useless.



Exasperatedly,


Robert Huff
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Committers needed

[Kurt Jaeger]

Hi!

> Hexchat still doesn't compile when gcc is installed:
> https://bugs.freebsd.org/211327

Done.

> Build fix and missing run dependencies for devel/stack:
> https://bugs.freebsd.org/211312

Done.

> PRs with maintainer timeouts or approval:
> https://bugs.freebsd.org/211223

Committed to HEAD, discussing MFH

> https://bugs.freebsd.org/211288

Committed to HEAD, discussing MFH

> https://bugs.freebsd.org/211663
> https://bugs.freebsd.org/211664
> https://bugs.freebsd.org/211573
> https://bugs.freebsd.org/211624

Pending other tasks...

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Lars Engels]

On Fri, Aug 26, 2016 at 09:34:32AM +0200, Raul wrote:
> 
> Lars Engels  escribió:
> 
> >> still with 'libcli-1.9.6_1' installed
> >> removing ssl from USES let it run again
> > Please delete devel/libcli as a workaround.
> 
> Ok so, without libcli and with ssl:
> 
> []
> Performing sanity check of icinga2 configuration:  
> /usr/local/lib/icinga2/libcli.so: Undefined symbol  
> "_ZN6icinga14ConfigCompiler15CollectIncludesERNSt3__16vectorIPNS_10ExpressionENS1_9allocatorIS4_RKNS_6StringESB_SB_"
> []
> 
> with libcli and ssl:
> 
> []
> Performing sanity check of icinga2 configuration:  
> /usr/local/lib/icinga2/libremote.so: Undefined symbol  
> "_ZTVN6icinga18GetScopeExpressionE"
> []
> 
> with libcli and without ssl it works
> 

Meh, thanks!


Upstream now has a patch that I will try.


pgpOYH3_en2C8.pgp
Description: PGP signature

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Raul]

Lars Engels  escribió:


still with 'libcli-1.9.6_1' installed
removing ssl from USES let it run again

Please delete devel/libcli as a workaround.


Ok so, without libcli and with ssl:

[]
Performing sanity check of icinga2 configuration:  
/usr/local/lib/icinga2/libcli.so: Undefined symbol  
"_ZN6icinga14ConfigCompiler15CollectIncludesERNSt3__16vectorIPNS_10ExpressionENS1_9allocatorIS4_RKNS_6StringESB_SB_"

[]

with libcli and ssl:

[]
Performing sanity check of icinga2 configuration:  
/usr/local/lib/icinga2/libremote.so: Undefined symbol  
"_ZTVN6icinga18GetScopeExpressionE"

[]

with libcli and without ssl it works

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Committers needed

[Kubilay Kocak]

On 26/08/2016 4:01 PM, Tobias Kortkamp wrote:
> Hi,
> 
> could someone take a look at these PRs?
> 
> Hexchat still doesn't compile when gcc is installed:
> https://bugs.freebsd.org/211327
> 
> Build fix and missing run dependencies for devel/stack:
> https://bugs.freebsd.org/211312
> 
> PRs with maintainer timeouts or approval:
> https://bugs.freebsd.org/211223
> https://bugs.freebsd.org/211288
> https://bugs.freebsd.org/211663
> https://bugs.freebsd.org/211664
> https://bugs.freebsd.org/211573
> https://bugs.freebsd.org/211624
> 
> Thanks!

Hey Tobias :)

Given the extent of your contribution and proactivity, I'd be happy to
offer you Bugzilla 'editbugs' permissions so you can triage /
'maintainer timeout'  / classify issues without having to wait for anyone.

Jump on #freebsd-bugs on freenode IRC if you (or anyone else) are keen
to join the triage crew

./koobs
Bugmeister

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: problem with net-mgmt/icinga2 upgrading from 2.4.10 to 2.5.1 (r420729)

[Lars Engels]

On Thu, Aug 25, 2016 at 10:36:06PM +0200, Raul wrote:
> 
> Lars Engels  escribió:
> 
> >> []
> >> # service icinga2 start
> >> Performing sanity check of icinga2 configuration:
> >> /usr/local/lib/icinga2/libcli.so: Undefined symbol
> >> "_ZN6icinga14ConfigCompiler15CollectIncludesERNSt3__16vectorIPNS_10ExpressionENS1_9allocatorIS4_RKNS_6StringESB_SB_"
> >> FAILED
> >> []
> >
> > This is now fixed.
> 
> I'm sorry to say it but not in my case (openssl-1.0.2_14)

:-/
> 
> []
> Performing sanity check of icinga2 configuration:  
> /usr/local/lib/icinga2/libremote.so: Undefined symbol  
> "_ZTVN6icinga18GetScopeExpressionE"
> []
> 
> still with 'libcli-1.9.6_1' installed
> removing ssl from USES let it run again
> 

Please delete devel/libcli as a workaround.


pgp6ZNyUifNEb.pgp
Description: PGP signature

Re: security/strongswan start=route issue

[Franco Fichtner]

Hi,

> On 26 Aug 2016, at 9:00 AM, abi  wrote:
> 
> I'd like to open PR on upstream, but I want be sure that the problem exists 
> not only for me, as the problem looks strange.
> The issue is that tunnel behaves different if it autostarts (auto=start) and 
> when it starts when traffic registered between left and right side. 
> (auto=route).

This works fine in our OPNsense setups.

Make sure you use ping with the option "-S $LEFT_IP", it will
only auto-route local traffic that originates from within your
leftsubnet.


Cheers,
Franco
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

security/strongswan start=route issue

[abi]

Hello,

I'd like to open PR on upstream, but I want be sure that the problem exists not 
only for me, as the problem looks strange.
The issue is that tunnel behaves different if it autostarts (auto=start) and 
when it starts when traffic registered between left and right side. 
(auto=route).

The latter method not works. I see tunnel up, route table updated, but no 
traffic flows.
So, the test is very easy:
1. Stop strongswan
2. Change /usr/local/etc/ipsec.conf tunnel config to auto=route
3. Start strongswan and try to ping the right side.
4. The tunnel should up, but no reply to pings.

If it matters, I use virtual ip (as it's a laptop without left network and 
without external ip). 

-- 
abi 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Committers needed

[Tobias Kortkamp]

Hi,

could someone take a look at these PRs?

Hexchat still doesn't compile when gcc is installed:
https://bugs.freebsd.org/211327

Build fix and missing run dependencies for devel/stack:
https://bugs.freebsd.org/211312

PRs with maintainer timeouts or approval:
https://bugs.freebsd.org/211223
https://bugs.freebsd.org/211288
https://bugs.freebsd.org/211663
https://bugs.freebsd.org/211664
https://bugs.freebsd.org/211573
https://bugs.freebsd.org/211624

Thanks!
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"