Problem with ipnat on 8.0 RC1

2018-06-11 Thread pimin inwa
Running:
NetBSD mail.wan.vpn 8.99.18 NetBSD 8.99.18 (GEMINI) #0: Sun May 27 09:56:42
PDT 2018  r...@mail.wan.vpn:/usr/src/BUILD_OBJ/sys/arch/i386/compile/GEMINI
i386

The GEMINI conf is different from GENERIC as follows:
1c1
< # $NetBSD: GENERIC,v 1.1180 2018/06/07 13:36:29 thorpej Exp $
---
> # $NetBSD: GENERIC,v 1.1178 2018/05/15 01:53:27 thorpej Exp $
25c25
< #ident"GENERIC-$Revision: 1.1180 $"
---
> #ident"GENERIC-$Revision: 1.1178 $"
27c27
< maxusers  64  # estimated number of users
---
> maxusers  128 # estimated number of users
32,33c32,33
< makeoptions   SPECTRE_V2_GCC_MITIGATION=1 # GCC Spectre variant 2
<   # migitation
---
> #makeoptions  SPECTRE_V2_GCC_MITIGATION=1 # GCC Spectre variant 2
> # # migitation
80c80
< options   RTC_OFFSET=0# hardware clock is this many mins. west of
GMT
---
> options   RTC_OFFSET=480  # hardware clock is this many mins. west of
GMT
114c114
< #options  DEBUG   # expensive debugging checks/support
---
> options   DEBUG   # expensive debugging checks/support
122c122
< #makeoptions  DEBUG="-g"  # compile full symbol table
---
> makeoptions   DEBUG="-g"  # compile full symbol table
185c185,187
< #options  GATEWAY # packet forwarding
---
> options   GATEWAY # packet forwarding
> options   IPFORWARDING=1  # grasping at straws with NAY problems
> options   MBUFTRACE
189c191
< #options  IPSEC_DEBUG # debug for IP security
---
> options   IPSEC_DEBUG # debug for IP security
194,196c196,198
< #options  CAN # Controller Area Network protocol
< #options  PPP_BSDCOMP # BSD-Compress compression support for PPP
< #options  PPP_DEFLATE # Deflate compression support for PPP
---
> options   CAN # Controller Area Network protocol
> options   PPP_BSDCOMP # BSD-Compress compression support for PPP
> options   PPP_DEFLATE # Deflate compression support for PPP
204c206
< #options  ALTQ# Manipulate network interfaces' output
queues
---
> options   ALTQ# Manipulate network interfaces' output
queues

The ipnat and ipf conf files used to work under NetBSD 6.??

This rule:

map re1 172.16.89.50/32   -> 50.251.213.138/32

 should map the system at .50 straight thru the NAT machine ... no??
Some connections go thru but, others timeout.  I can get to those timed out
systems from the NAT'ng system.

tcpdump in the interior NIC shows the the packets arriving but, nothing on
the outboud NIC.

Am I missing something between 6.?? and 8.0 ?

Hints appreciated.

TIA,
Paul N.
-- 



daily CVS update output

2018-06-11 Thread NetBSD source update


Updating src tree:
P src/external/gpl3/gcc/lib/libubsan/Makefile
P src/games/rogue/Makefile
P src/lib/libc/citrus/modules/citrus_mapper_std.c
P src/sbin/fsck_ffs/Makefile
P src/sbin/ifconfig/af_inet.c
P src/sys/arch/acorn32/stand/lib/Makefile.inc
P src/sys/arch/arm/vexpress/vexpress_platform.c
P src/sys/arch/evbarm/conf/VEXPRESS_A15
P src/sys/arch/evbarm/vexpress/vexpress_start.S
P src/sys/arch/hppa/spmath/Makefile.inc
P src/sys/arch/i386/stand/lib/Makefile.inc
P src/sys/arch/ia64/stand/efi/libefi/Makefile.inc
P src/sys/arch/usermode/usermode/machdep.c
P src/sys/arch/usermode/usermode/trap.c
P src/sys/dev/fdt/fdt_subr.c
P src/sys/dev/fdt/fdtbus.c
P src/sys/dev/pci/if_msk.c
P src/sys/dev/pci/if_mskvar.h
P src/sys/dev/pci/ixgbe/ixgbe_82599.c
P src/sys/dev/pci/ixgbe/ixgbe_api.c
P src/sys/dev/pci/ixgbe/ixgbe_type.h
P src/sys/dev/pci/ixgbe/ixgbe_x540.c
P src/tools/compat/compat_defs.h
P src/tools/compat/configure
P src/tools/compat/configure.ac
P src/tools/compat/nbtool_config.h.in
P src/usr.bin/dc/Makefile
P src/usr.bin/gprof/Makefile
P src/usr.bin/gzip/gzip.c

Updating xsrc tree:


Killing core files:




Updating file list:
-rw-rw-r--  1 srcmastr  netbsd  57348546 Jun 12 03:03 ls-lRA.gz


Re: VirtualBox mouse problem

2018-06-11 Thread Valery Ushakov
On Mon, Jun 11, 2018 at 21:53:13 +0300, Arto Huusko wrote:

> Valery Ushakov kirjoitti 10.6.2018 klo 20:19:
> 
> > NetBSD vboxguest driver now provides wsmouse(4) interface so X11 can
> > use stock "ws" driver.
> 
> Thanks, using "ws" driver fixed the issue. But note that I was trying to
> use stock "mouse" driver, not vboxmouse driver.

Sorry, I have zero clue about X11 drivers :)

With the new additions you get

  wsmouse1 at vboxguest0 mux 0

and wsmouse1 will only ever feed absolute position events into the
wsmouse mux (src/VBox/Additions/common/VBoxGuest/VBoxGuest-netbsd.c)


> However, mouse buttons 6 and 7 still do not work correctly: xev shows
> the same events for buttons 4 and 6 and for 5 and 7.

See above.  This should not be a problem with additions.  Button press
events come from wsmouse0 that talks to the emulated mouse, not to the
vboxguest driver.

That seems like a vbox bug, I see the same problem in a linux guest
(horizontal scrolling reported as 4/5 instead of 6/7, as the host
does).


> Another problem is that pkgsrc modular xorg xf86-input-ws does not
> attach mouse at all: it tries to attach the mouse as a touchscreen and
> fails due to some unsupported ioctl.

Sorry, I dont't have time to build and test modular xorg.  It would be
nice if someone could investigate this.


-uwe


Re: VirtualBox mouse problem

2018-06-11 Thread Arto Huusko

Valery Ushakov kirjoitti 10.6.2018 klo 20:19:


NetBSD vboxguest driver now provides wsmouse(4) interface so X11 can
use stock "ws" driver.


Thanks, using "ws" driver fixed the issue. But note that I was trying to
use stock "mouse" driver, not vboxmouse driver.

However, mouse buttons 6 and 7 still do not work correctly: xev shows
the same events for buttons 4 and 6 and for 5 and 7.

Another problem is that pkgsrc modular xorg xf86-input-ws does not
attach mouse at all: it tries to attach the mouse as a touchscreen and
fails due to some unsupported ioctl.

Arto


Re: More build.sh ctf fallout on a linux host

2018-06-11 Thread maya
On Thu, Jun 07, 2018 at 06:47:13AM -0400, Chuck Zmudzinski wrote:
> Hello,

Thanks, I committed that.
I tried to match compat_defs.h's existing style better.


Automated report: NetBSD-current/i386 test failure

2018-06-11 Thread NetBSD Test Fixture
This is an automatically generated notice of new failures of the
NetBSD test suite.

The newly failing test cases are:

usr.bin/cc/t_ubsan_int_add_overflow:int_add_overflow
usr.bin/cc/t_ubsan_int_add_overflow:int_add_overflow_pic
usr.bin/cc/t_ubsan_int_add_overflow:int_add_overflow_pie
usr.bin/cc/t_ubsan_int_add_overflow:int_add_overflow_profile
usr.bin/cc/t_ubsan_int_divzero:int_divzero
usr.bin/cc/t_ubsan_int_divzero:int_divzero_pic
usr.bin/cc/t_ubsan_int_divzero:int_divzero_pie
usr.bin/cc/t_ubsan_int_divzero:int_divzero_profile
usr.bin/cc/t_ubsan_int_neg_overflow:int_neg_overflow
usr.bin/cc/t_ubsan_int_neg_overflow:int_neg_overflow_pic
usr.bin/cc/t_ubsan_int_neg_overflow:int_neg_overflow_pie
usr.bin/cc/t_ubsan_int_neg_overflow:int_neg_overflow_profile
usr.bin/cc/t_ubsan_int_sub_overflow:int_sub_overflow
usr.bin/cc/t_ubsan_int_sub_overflow:int_sub_overflow_pic
usr.bin/cc/t_ubsan_int_sub_overflow:int_sub_overflow_pie
usr.bin/cc/t_ubsan_int_sub_overflow:int_sub_overflow_profile
usr.bin/cc/t_ubsan_vla_out_of_bounds:vla_out_of_bounds
usr.bin/cc/t_ubsan_vla_out_of_bounds:vla_out_of_bounds_pic
usr.bin/cc/t_ubsan_vla_out_of_bounds:vla_out_of_bounds_pie
usr.bin/cc/t_ubsan_vla_out_of_bounds:vla_out_of_bounds_profile

The above tests failed in each of the last 3 test runs, and passed in
at least 27 consecutive runs before that.

The following commits were made between the last successful test and
the failed test:

2018.06.09.22.39.29 christos src/external/gpl3/gcc/lib/libasan/Makefile,v 
1.24
2018.06.09.22.40.00 christos src/external/gpl3/gcc/lib/Makefile.sanitizer,v 
1.5
2018.06.09.22.41.55 christos src/lib/libc/Makefile.inc,v 1.19
2018.06.09.22.41.55 christos src/lib/libpthread/Makefile,v 1.89
2018.06.09.22.41.55 christos src/libexec/ld.elf_so/Makefile,v 1.138
2018.06.09.23.45.56 christos src/lib/libpthread/Makefile,v 1.90

Log files can be found at:


http://releng.NetBSD.org/b5reports/i386/commits-2018.06.html#2018.06.09.23.45.56