ipfw2 (was Re: Hard-coded M_* flags)

joerg at britannica.bec.de joerg at britannica.bec.de
Sun Jun 11 05:33:48 PDT 2006

On Sun, Jun 11, 2006 at 07:16:53PM +0900, YONETANI Tomokazu wrote:
> On Thu, Jun 08, 2006 at 12:41:51PM +0900, YONETANI Tomokazu wrote:
> > [hardcoded M_ flags]
> >   M_SKIP_FIREWALL: defined as 0x4000, which conflicts with M_EXT_CLUSTER
> >     /sys/net/ipfw/ip_fw2.c
> Can I commit the following patch?  This only helps ipv4-only environment,
> but those who are in ipv6 network are not probably using ipfw2.
> Without this, you get a kernel panic in m_free() as soon as ipfw2
> sends out a packet generated by send_pkt().

Can you work on a patch to put it into fw_flags instead? That would
resolve the problem in a better way IMO.


More information about the Submit mailing list