�
�
26.01.2015, 23:35, Olivier Cochard-Labbé oliv...@cochard.me:
On Sun, Jan 25, 2015 at 9:37 PM, John Baldwin [1]j...@freebsd.org
wrote:
Author: jhb
Date: Sun Jan 25 20:37:32 2015
New Revision: 277714
URL: [2]https://svnweb.freebsd.org/changeset/base/277714
On Monday, January 26, 2015 09:34:39 PM Olivier Cochard-Labbé wrote:
On Sun, Jan 25, 2015 at 9:37 PM, John Baldwin j...@freebsd.org wrote:
Author: jhb
Date: Sun Jan 25 20:37:32 2015
New Revision: 277714
URL: https://svnweb.freebsd.org/changeset/base/277714
Log:
natd(8) will work
On 26 Jan 2015, at 22:24, John Baldwin j...@freebsd.org wrote:
On Monday, January 26, 2015 09:34:39 PM Olivier Cochard-Labbé wrote:
On Sun, Jan 25, 2015 at 9:37 PM, John Baldwin j...@freebsd.org wrote:
Author: jhb
Date: Sun Jan 25 20:37:32 2015
New Revision: 277714
URL:
On Mon, Jan 26, 2015 at 10:50 PM, Nick Hibma n...@van-laarhoven.org wrote:
On 26 Jan 2015, at 22:24, John Baldwin j...@freebsd.org wrote:
It might. What happened for me is that I was using nat over wlan0 for
VM's
on my laptop to reach the outside world, but wlan0 doesn't get an IP
On Sun, Jan 25, 2015 at 9:37 PM, John Baldwin j...@freebsd.org wrote:
Author: jhb
Date: Sun Jan 25 20:37:32 2015
New Revision: 277714
URL: https://svnweb.freebsd.org/changeset/base/277714
Log:
natd(8) will work with an unconfigured interface and effectively not do
anything until the
Author: jhb
Date: Sun Jan 25 20:37:32 2015
New Revision: 277714
URL: https://svnweb.freebsd.org/changeset/base/277714
Log:
natd(8) will work with an unconfigured interface and effectively not do
anything until the interface is assigned an address. This fixes
ipfw_nat to do the same by
