Date: Tue, 21 Apr 2015 13:14:43 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ipfw@FreeBSD.org Subject: [Bug 178480] [ipfw] dynamically loaded ipfw with a vimage kernel don't work. Message-ID: <bug-178480-7515-IVYIXnSCN6@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-178480-7515@https.bugs.freebsd.org/bugzilla/> References: <bug-178480-7515@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=178480 smithi@nimnet.asn.au changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |smithi@nimnet.asn.au --- Comment #3 from smithi@nimnet.asn.au --- > I can report that as for FBSD 10.1 there are no filtering problems when > using a dynamically loaded ipfw for firewalling on the jail host and > inside VIMAGE jails. Only ipfw logging inside VIMAGE jails does not work. "Only logging inside VIMAGE jails does not work." is the main issue of this PR and of 178482 (in which I foolishly attempted to participate :) so while this is mostly duplication, is the issue itself still unresolved? Is it to be expected that ipfw in a VNET jail can't log to /var/log/security specifically? Or can it, with particular jail configuration? Is this a VNET jail issue generally, or an ipfw issue specifically? Sorry, but I'm not in a position to test my own curiousity lately, but it seems a strange limitation on ipfw functionality in the jail unless explained by valid but non-obvious security concerns? cheers, Ian -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-178480-7515-IVYIXnSCN6>