FreeBSD Quarterly Status Report - First Quarter 2017

2017-05-15 Thread Benjamin Kaduk
FreeBSD Project Quarterly Status Report - 1st Quarter 2017 While a few of these projects indicate they are a "plan B" or an "attempt III", many are still hewing to their original plans, and all have produced impressive results. Please enjoy this vibrant collection of reports, covering

Re: something is not working: ipfw fwd VIA nat TO tun on FreeBSD-11 stable r318266

2017-05-15 Thread Eugene Kazarinov
I downgraded via makeworld from /usr/src to 10.3-STABLE r318297 And now ipnat.rules is working and mapping forwarded packets. Maybe I forgot that pf nat didnt map forwarded packets on 10 version. I install this system some time ago. And dont remember which config is apply (ipnat.rules or pf.conf)

something is not working: ipfw fwd VIA nat TO tun on FreeBSD-11 stable r318266

2017-05-15 Thread Eugene Kazarinov
Hello. After upgrade from 10.3 stable something broke. I have tun0 tun0: flags=8151 metric 0 mtu 1500 options=8 inet 10.10.0.6 --> 10.10.0.5 netmask 0x groups: tun Opened by PID in pf.conf I have rule nat on tun0

zpool imported twice with different names (was Re: Fwd: ZFS)

2017-05-15 Thread Nikos Vassiliadis
Fix the e-mail subject On 05/15/2017 08:09 PM, Nikos Vassiliadis wrote: Hi everybody, While trying to rename a zpool from zroot to vega, I ended up in this strange situation: nik@vega:~ % zfs list -t all NAME USED AVAIL REFER MOUNTPOINT vega1.83G 34.7G

Fwd: ZFS

2017-05-15 Thread Nikos Vassiliadis
Hi everybody, While trying to rename a zpool from zroot to vega, I ended up in this strange situation: nik@vega:~ % zfs list -t all NAME USED AVAIL REFER MOUNTPOINT vega1.83G 34.7G96K /zroot vega/ROOT 1.24G 34.7G96K none vega/ROOT/default

Problems with re(4) Ethernet driver in 11-STABLE and HEAD

2017-05-15 Thread Thomas Mueller
I remember having problems with Realtek 8111E Ethernet on this Intel Ivy Bridge computer a couple years ago, and now the problem has resurfaced. I am fresh from updating FreeBSD to 11-STABLE and HEAD on two partitions, and in both cases can not connect with onboard Ethernet. >From NetBSD