Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 28 Dec 2025 12:28:51 +0300
From:      Andrey V. Elsukov <bu7cher@yandex.ru>
To:        FreeBSD User <freebsd@walstatt-de.de>, Ronald Klop <ronald-lists@klop.ws>
Cc:        FreeBSD CURRENT <freebsd-current@freebsd.org>, David Wolfskill <david@catwhisker.org>
Subject:   Re: CURRENT: kernel panic in IPFW while stopping jails
Message-ID:  <26521766914006@mail.yandex.ru>
In-Reply-To: <20251225190836.6769e6d6@hermann>
References:  <20251225170828.7aef61df@hermann> <902742484.3865.1766683845222@localhost> <20251225190836.6769e6d6@hermann>

index | next in thread | previous in thread | raw e-mail

<blockquote><p>On Thu, 25 Dec 2025 18:30:45 +0100 (CET)<br />Ronald Klop &lt;<a href="mailto:ronald-lists@klop.ws" rel="noopener noreferrer">ronald-lists@klop.ws</a>&gt; wrote:<br /> </p><blockquote> Do you use bpf or tap in your ipfw rules?<br /> A panic with that was mentioned on the 20th. And fixed in the mean time of I<br /> remember correctly. <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291854" rel="noopener noreferrer">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291854</a><br /> Regards,Ronald</blockquote><p><br />Indeed, all boxes in question do have a tap0 at least defined -but in only one<br />case used.</p></blockquote>Hi,<div> </div><div>I don't think it is related to tap0.</div><div>If it is related to recent BPF changes in ipfw, you can try to remove "log" opcode</div><div>from your rules.</div><div> </div><div>-- <br />WBR, Andrey V. Elsukov</div><div> </div>


home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?26521766914006>