daily CVS update output

2015-01-17 Thread NetBSD source update 

Updating src tree:
P src/distrib/sets/lists/base/ad.aarch64
P src/distrib/sets/lists/base/ad.arm
P src/distrib/sets/lists/base/ad.mips
P src/distrib/sets/lists/base/ad.powerpc
P src/distrib/sets/lists/base/ad.riscv
P src/distrib/sets/lists/base/md.amd64
P src/distrib/sets/lists/base/md.sparc64
P src/distrib/sets/lists/base/shl.mi
P src/distrib/sets/lists/debug/ad.aarch64
P src/distrib/sets/lists/debug/ad.arm
P src/distrib/sets/lists/debug/ad.mips
P src/distrib/sets/lists/debug/ad.powerpc
P src/distrib/sets/lists/debug/ad.riscv
P src/distrib/sets/lists/debug/md.amd64
P src/distrib/sets/lists/debug/md.sparc64
P src/distrib/sets/lists/debug/shl.mi
P src/doc/3RDPARTY
P src/doc/CHANGES
U src/external/bsd/am-utils/amd2netbsd
P src/external/bsd/am-utils/bin/fsinfo/Makefile
P src/external/bsd/am-utils/dist/COPYING
P src/external/bsd/am-utils/dist/ChangeLog
P src/external/bsd/am-utils/dist/INSTALL
P src/external/bsd/am-utils/dist/Makefile.am
P src/external/bsd/am-utils/dist/NEWS
P src/external/bsd/am-utils/dist/README
U src/external/bsd/am-utils/dist/README.release
U src/external/bsd/am-utils/dist/README.release-announce
P src/external/bsd/am-utils/dist/bootstrap
P src/external/bsd/am-utils/dist/buildall
P src/external/bsd/am-utils/dist/config.guess
P src/external/bsd/am-utils/dist/config.sub
U src/external/bsd/am-utils/dist/configure.ac
cvs update: `src/external/bsd/am-utils/dist/configure.in' is no longer in the 
repository
P src/external/bsd/am-utils/dist/depcomp
P src/external/bsd/am-utils/dist/install-sh
U src/external/bsd/am-utils/dist/ltmain.sh
P src/external/bsd/am-utils/dist/missing
P src/external/bsd/am-utils/dist/mkinstalldirs
U src/external/bsd/am-utils/dist/vers.m4
P src/external/bsd/am-utils/dist/ylwrap
U src/external/bsd/am-utils/dist/ylwrap.amd
P src/external/bsd/am-utils/dist/amd/Makefile.am
P src/external/bsd/am-utils/dist/amd/am_ops.c
P src/external/bsd/am-utils/dist/amd/amd.8
P src/external/bsd/am-utils/dist/amd/amd.c
P src/external/bsd/am-utils/dist/amd/amd.h
P src/external/bsd/am-utils/dist/amd/amfs_auto.c
P src/external/bsd/am-utils/dist/amd/amfs_direct.c
P src/external/bsd/am-utils/dist/amd/amfs_error.c
P src/external/bsd/am-utils/dist/amd/amfs_generic.c
P src/external/bsd/am-utils/dist/amd/amfs_host.c
P src/external/bsd/am-utils/dist/amd/amfs_link.c
P src/external/bsd/am-utils/dist/amd/amfs_linkx.c
P src/external/bsd/am-utils/dist/amd/amfs_nfsl.c
P src/external/bsd/am-utils/dist/amd/amfs_nfsx.c
P src/external/bsd/am-utils/dist/amd/amfs_program.c
P src/external/bsd/am-utils/dist/amd/amfs_root.c
P src/external/bsd/am-utils/dist/amd/amfs_toplvl.c
P src/external/bsd/am-utils/dist/amd/amfs_union.c
P src/external/bsd/am-utils/dist/amd/amq_subr.c
P src/external/bsd/am-utils/dist/amd/amq_svc.c
P src/external/bsd/am-utils/dist/amd/autil.c
P src/external/bsd/am-utils/dist/amd/clock.c
P src/external/bsd/am-utils/dist/amd/conf.c
P src/external/bsd/am-utils/dist/amd/conf_parse.y
P src/external/bsd/am-utils/dist/amd/conf_tok.l
P src/external/bsd/am-utils/dist/amd/get_args.c
P src/external/bsd/am-utils/dist/amd/info_exec.c
P src/external/bsd/am-utils/dist/amd/info_file.c
P src/external/bsd/am-utils/dist/amd/info_hesiod.c
P src/external/bsd/am-utils/dist/amd/info_ldap.c
P src/external/bsd/am-utils/dist/amd/info_ndbm.c
P src/external/bsd/am-utils/dist/amd/info_nis.c
P src/external/bsd/am-utils/dist/amd/info_nisplus.c
P src/external/bsd/am-utils/dist/amd/info_passwd.c
P src/external/bsd/am-utils/dist/amd/info_sun.c
P src/external/bsd/am-utils/dist/amd/info_union.c
P src/external/bsd/am-utils/dist/amd/map.c
P src/external/bsd/am-utils/dist/amd/mapc.c
P src/external/bsd/am-utils/dist/amd/mntfs.c
P src/external/bsd/am-utils/dist/amd/nfs_prot_svc.c
P src/external/bsd/am-utils/dist/amd/nfs_start.c
P src/external/bsd/am-utils/dist/amd/nfs_subr.c
P src/external/bsd/am-utils/dist/amd/ops_TEMPLATE.c
P src/external/bsd/am-utils/dist/amd/ops_cachefs.c
P src/external/bsd/am-utils/dist/amd/ops_cdfs.c
P src/external/bsd/am-utils/dist/amd/ops_efs.c
U src/external/bsd/am-utils/dist/amd/ops_ext.c
P src/external/bsd/am-utils/dist/amd/ops_lofs.c
U src/external/bsd/am-utils/dist/amd/ops_lustre.c
P src/external/bsd/am-utils/dist/amd/ops_mfs.c
P src/external/bsd/am-utils/dist/amd/ops_nfs.c
P src/external/bsd/am-utils/dist/amd/ops_nfs3.c
U src/external/bsd/am-utils/dist/amd/ops_nfs4.c
P src/external/bsd/am-utils/dist/amd/ops_nullfs.c
P src/external/bsd/am-utils/dist/amd/ops_pcfs.c
P src/external/bsd/am-utils/dist/amd/ops_tfs.c
P src/external/bsd/am-utils/dist/amd/ops_tmpfs.c
P src/external/bsd/am-utils/dist/amd/ops_udf.c
P src/external/bsd/am-utils/dist/amd/ops_ufs.c
P src/external/bsd/am-utils/dist/amd/ops_umapfs.c
P src/external/bsd/am-utils/dist/amd/ops_unionfs.c
P src/external/bsd/am-utils/dist/amd/ops_xfs.c
P src/external/bsd/am-utils/dist/amd/opts.c
P src/external/bsd/am-utils/dist/amd/readdir.c
P src/external/bsd/am-utils/dist/amd/restart.c
P src/external/bsd/am-utils/dist/amd/rpc_fwd.c
P src/external/bsd/am-utils/dist/amd

Automated report: NetBSD-current/i386 build failure

2015-01-17 Thread NetBSD Test Fixture 
This is an automatically generated notice of a NetBSD-current/i386
build failure.

The failure occurred on babylon5.NetBSD.org, a NetBSD/amd64 host,
using sources from CVS date 2015.01.17.17.48.41.

An extract from the build.sh output follows:

#format  man4/cypide.html4
if test "" != "yes"; then  
/tmp/bracket/build/2015.01.17.17.48.41-i386/tools/bin/nbmandoc -Thtml 
-Oman=../html%S/%N.html -Ostyle=../style.css  
/tmp/bracket/build/2015.01.17.17.48.41-i386/src/share/man/man4/cypide.4 > 
cypide.html4.tmp &&  mv cypide.html4.tmp cypide.html4;  else  
PATH=/tmp/bracket/build/2015.01.17.17.48.41-i386/tools/lib/groff:${PATH} 
/tmp/bracket/build/2015.01.17.17.48.41-i386/tools/bin/nbgroff -Tlatin1 
-mdoc2html 
/tmp/bracket/build/2015.01.17.17.48.41-i386/src/share/man/man4/cypide.4   > 
cypide.html4.tmp && mv cypide.html4.tmp cypide.html4;  fi
--- dependall-crypto/external ---
--- config.o ---
--- dependall-external ---

/tmp/bracket/build/2015.01.17.17.48.41-i386/src/external/bsd/am-utils/dist/amd/amq_subr.c:557:5:
 error: passing argument 2 of 'xdr_long' from incompatible pointer type 
[-Werror]
--- dependall-share ---
--- cxdtv.html4 ---
--- dependall-external ---
 if (!xdr_long(xdrs, &m->modify)) {
 ^
In file included from 
/tmp/bracket/build/2015.01.17.17.48.41-i386/destdir/usr/include/rpc/rpc.h:48:0,
 from 
/tmp/bracket/build/2015.01.17.17.48.41-i386/src/external/bsd/am-utils/dist/include/am_defs.h:284,
 from 
/tmp/bracket/build/2015.01.17.17.48.41-i386/src/external/bsd/am-utils/dist/amd/amq_subr.c:48:

/tmp/bracket/build/2015.01.17.17.48.41-i386/destdir/usr/include/rpc/xdr.h:283:15:
 note: expected 'long int *' but argument is of type 'time_t *'
 extern bool_t xdr_long(XDR *, long *);
   ^
--- dependall-crypto/external ---
#   compile  kdc/config.o
/tmp/bracket/build/2015.01.17.17.48.41-i386/tools/bin/i486--netbsdelf-gcc 
-O2-std=gnu99   -Werror
--sysroot=/tmp/bracket/build/2015.01.17.17.48.41-i386/destdir -DHAVE_IPV6 
-DHAVE_CONFIG_H -I. 
-I/tmp/bracket/build/2015.01.17.17.48.41-i386/src/crypto/external/bsd/heimdal/sbin/kdc
 
-I/tmp/bracket/build/2015.01.17.17.48.41-i386/src/crypto/external/bsd/heimdal/dist/kdc
 
-I/tmp/bracket/build/2015.01.17.17.48.41-i386/src/crypto/external/bsd/heimdal/include
 
-I/tmp/bracket/build/2015.01.17.17.48.41-i386/src/crypto/external/bsd/heimdal/dist/include
 
-I/tmp/bracket/build/2015.01.17.17.48.41-i386/src/crypto/external/bsd/heimdal/dist/lib/krb5

-I/tmp/bracket/build/2015.01.17.17.48.41-i386/src/crypto/external/bsd/heimdal/include/krb5
  -c
/tmp/bracket/build/2015.01.17.17.48.41-i386/src/crypto/external/bsd/heimdal/dist/kdc/config.c
--- dependall-share ---
#format  man4/cxdtv.html4
if test "" != "yes"; then  
/tmp/bracket/build/2015.01.17.17.48.41-i386/tools/bin/nbmandoc -Thtml 
-Oman=../html%S/%N.html -Ostyle=../style.css  
/tmp/bracket/build/2015.01.17.17.48.41-i386/src/share/man/man4/cxdtv.4 > 
cxdtv.html4.tmp &&  mv cxdtv.html4.tmp cxdtv.html4;  else  
PATH=/tmp/bracket/build/2015.01.17.17.48.41-i386/tools/lib/groff:${PATH} 
/tmp/bracket/build/2015.01.17.17.48.41-i386/tools/bin/nbgroff -Tlatin1 
-mdoc2html 
/tmp/bracket/build/2015.01.17.17.48.41-i386/src/share/man/man4/cxdtv.4   > 
cxdtv.html4.tmp && mv cxdtv.html4.tmp cxdtv.html4;  fi
--- ddb.html4 ---
--- dependall-usr.bin ---
--- debug.o ---
--- dependall-share ---
#format  man4/ddb.html4
if test "" != "yes"; then  
/tmp/bracket/build/2015.01.17.17.48.41-i386/tools/bin/nbmandoc -Thtml 
-Oman=../html%S/%N.html -Ostyle=../style.css  
/tmp/bracket/build/2015.01.17.17.48.41-i386/src/share/man/man4/ddb.4 > 
ddb.html4.tmp &&  mv ddb.html4.tmp ddb.html4;  else  
PATH=/tmp/bracket/build/2015.01.17.17.48.41-i386/tools/lib/groff:${PATH} 
/tmp/bracket/build/2015.01.17.17.48.41-i386/tools/bin/nbgroff -Tlatin1 
-mdoc2html /tmp/bracket/build/2015.01.17.17.48.41-i386/src/share/man/man4/ddb.4 
  > ddb.html4.tmp && mv ddb.html4.tmp ddb.html4;  fi
--- dependall-usr.bin ---
#   compile  elf32/debug.o
/tmp/bracket/build/2015.01.17.17.48.41-i386/tools/bin/i486--netbsdelf-gcc 
-O2   -std=gnu99-Wall -Wstrict-prototypes -Wmissing-prototypes 
-Wpointer-arith -Wno-sign-compare  -Wno-traditional  -Wa,--fatal-warnings 
-Wreturn-type -Wswitch -Wshadow -Wcast-qual -Wwrite-strings -Wextra 
-Wno-unused-parameter -Wno-sign-compare -Werror 
--sysroot=/tmp/bracket/build/2015.01.17.17.48.41-i386/destdir 
-D_rtld_tls_allocate=_elf32__rtld_tls_allocate 
-D_rtld_tls_free=_elf32__rtld_tls_free -DELFSIZE=32 
-I/tmp/bracket/build/2015.01.17.17.48.41-i386/src/libexec/ld.elf_so 
-DLIBDIR=\"/usr/lib\" -D_RTLD_SOURCE  -c
/tmp/bracket/build/2015.01.17.17.48.41-i386/src/libexec/ld.elf_so/debug.c -o 
debug.o
--- dependall-external ---
cc1: all warnings being treated as errors
*** [amq_subr.o] Error code 1
nbmake[10]: stop

Re: npf blocks ipv6 fragmented packets (?)

2015-01-17 Thread Greg Troxel 

Markus Kilbinger  writes:

> Tracking it down (a bit) i've found that simply activating npf without any 
> rule
>
>   ntpctl start
>
> 'blocks' a
>
>   ping6 -s 2048 testhost
>
> which worked w/o npf aktivated flawlessly.
> BTW: ipv4 fragmented packets seems to be handled correctly under npf
> ('ping -s 2048' works).
> This happens under HEAD and netbsd-7.
>
> Is this a known limitation of npf? Or a bug?
> Send-pr?

If it's not documented in the man page, sure, file a PR.
Actually, even if documented, a PR is in order...


pgpUX557sapm3.pgp
Description: PGP signature

Re: pf--?

2015-01-17 Thread Dave Huang 

On 2015-01-17 7:09, Thomas Klausner wrote:
Is the functionality you need already there in npf, or what in 
particular would you be missing 


Does npf have ALTQ integration? As far as I know, altqd only supports 
basic classification, and pf is required for fine-grained rules.


--
Name: Dave Huang |  Mammal, mammal / their names are called /
INet: k...@azeotrope.org |  they raise a paw / the bat, the cat /
FurryMUCK: Dahan |  dolphin and dog / koala bear and hog -- TMBG
Dahan: Hani G Y+C 39 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++

Re: pf--?

2015-01-17 Thread Mindaugas Rasiukevicius 
Hauke Fath  wrote:
> On Sat, 17 Jan 2015 00:50:16 +0100, Thomas Klausner wrote:
> > Is there still much point in keeping pf(4) in NetBSD now that we have
> > npf(4) (and also ipfilter(4))?
> 
> We run a busy pf based router @work, and it generally "just works" 
> where ipf(4) broke - has 
>  ever 
> been fixed?
> 
> And npf(4) - no offense meant to its authors - is neither stable nor 
> feature complete at this point - watch the steady trickle of PRs 
> against it.

Umm, can you be more specific?  I get problem reports after some major
changes are committed.  This happens when you have active development,
unlike with other packet filters.  Currently, I am aware of only one
major stability problem (PR/49488) and I am looking into that.  Again,
it happen after my latest changes to connection tracking.

-- 
Mindaugas

Re: pf--?

2015-01-17 Thread Mindaugas Rasiukevicius 
Thomas Klausner  wrote:
> Is there still much point in keeping pf(4) in NetBSD now that we have
> npf(4) (and also ipfilter(4))?
> 

There are some missing features we need to implement before being able to
fully replace it.  Once those are done, I am all for nuking pf(4).

-- 
Mindaugas

Re: pf--?

2015-01-17 Thread Thomas Klausner 
On Sat, Jan 17, 2015 at 12:58:03PM +0100, Hauke Fath wrote:
> We run a busy pf based router @work, and it generally "just works" 
> where ipf(4) broke - has 
>  ever 
> been fixed?
> 
> And npf(4) - no offense meant to its authors - is neither stable nor 
> feature complete at this point - watch the steady trickle of PRs 
> against it.

Is the functionality you need already there in npf, or what in
particular would you be missing?
 Thomas

Re: pf--?

2015-01-17 Thread Hauke Fath 
On Sat, 17 Jan 2015 00:50:16 +0100, Thomas Klausner wrote:
> Is there still much point in keeping pf(4) in NetBSD now that we have
> npf(4) (and also ipfilter(4))?

We run a busy pf based router @work, and it generally "just works" 
where ipf(4) broke - has 
 ever 
been fixed?

And npf(4) - no offense meant to its authors - is neither stable nor 
feature complete at this point - watch the steady trickle of PRs 
against it.

> The last time it was updated was, according to the CHANGES files, in
> 2008, to the version coming with OpenBSD 4.2.

It works for me. Answering your question: Yes, there is.

Maybe drop it after NetBSD 10?  ;)

Cheerio,
hauke

-- 
Hauke Fath
Ernst-Ludwig-Straße 15
64625 Bensheim
Germany