Date: Sun, 10 Jan 2010 04:30:22 +0900 From: Hajimu UMEMOTO <ume@freebsd.org> To: David Horn <dhorn2000@gmail.com> Cc: freebsd-ipfw@freebsd.org Subject: Re: Unified rc.firewall ipfw me/me6 issue Message-ID: <ygeaawnt6sx.wl%ume@mahoroba.org> In-Reply-To: <25ff90d61001021736p7b695197q104f4a7769b51b71@mail.gmail.com> References: <25ff90d60912162320y286e37a0ufeb64397716d8c18@mail.gmail.com> <ygek4wmyp3j.wl%ume@mahoroba.org> <25ff90d60912180612y2b1f64fbw34b4d7f648762087@mail.gmail.com> <yged42c4770.wl%ume@mahoroba.org> <25ff90d61001021736p7b695197q104f4a7769b51b71@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
>>>>> On Sat, 2 Jan 2010 20:36:45 -0500
>>>>> David Horn <dhorn2000@gmail.com> said:
dhorn2000> On a separate note, you may want to consider adding an explicit
dhorn2000> "allow" in the default rc.firewall to support dhcpv6-client requests.
dhorn2000> (at least in client case, but potentially workstation as well)
Good catch! The client type firewall rule allows DHCP, implicitly.
I've committed to allow DHCPv6 as well for the client type firewall.
Since the workstation type firewall rule explicitly allows DHCP, we
have the rule to allow DHCPv6 already.
Sincerely,
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
ume@mahoroba.org ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ygeaawnt6sx.wl%ume>