�
�
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
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 using an IP of INADDR_ANY instead of
� aborting the nat setup if the requested interface is not yet
configured.
�
Hi,
I've still a problem with ipfw_nat and unconfigured interface:
On my setup I'm using ipfw with NAT rules using an OpenVPN tunnel
interface as source address for NATting.
During the machine startup, ipfw is started before openvpn (hopefully)
and its configuration mention do to NAT using tun0 IP address.
Then OpenVPN start and create a tun0 and set an IP address on it.
=> But no unicast traffic is allowed on this tun0 interface until I
restart ipfw.
If I correctly understand the log of this commit: This behavior should
be fixed by this commit, right ?
As far as I understand, nat instance is created with an unresolved ip
(0.0.0.0 propagated to libalias) and "tun0" interface name. After
"tun0" creation and address assignment, kernel ipfw_nat ifaddr hook
should take action and update libalias address to primary? IPv4
interface address.
�
References
1. mailto:j...@freebsd.org
2. https://svnweb.freebsd.org/changeset/base/277714
_______________________________________________
svn-src-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
