Traceroute / ICMP issue after 24.7.1 update

Started by MeltdownSpectre, August 08, 2024, 07:16:38 PM

Previous topic - Next topic
August 09, 2024, 09:47:42 AM #15 Last Edit: August 09, 2024, 09:49:14 AM by doktornotor
Quote from: franco on August 09, 2024, 08:10:55 AM
Might also be possible to confirm with pfctl -d / test traceroute / pfctl -e as a quick test that pf is doing it.

Well yes, disabling the firewall fixes the problem, feel much safer now compared to leaking replies to ping.  ;D :P

Quote from: franco on August 09, 2024, 08:57:09 AM
You can revert the kernel as suggested.

That brings back the kernel that panics with IPS, doesn't it? Just as a warning for people. Might rather live with broken ICMP for the moment.

Now, this crafted ping packets nonsense reminds me of this rant I wrote almost 20 years ago.

Ugh.



August 09, 2024, 09:57:05 AM #18 Last Edit: August 09, 2024, 09:59:45 AM by Patrick M. Hausen
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

@doktornotor

# opnsense-update -zkr 24.7-xen3

I'll leave it there for a while longer then.


Cheers,
Franco

Quote from: Patrick M. Hausen on August 09, 2024, 09:57:05 AM
@doktornotor

http://www.ranum.com/security/computer_security/papers/a1-firewall/index.html

8)

LMAO! Printed that to PDF.  8) ;D


Quote from: franco on August 09, 2024, 09:58:27 AM
@doktornotor

# opnsense-update -zkr 24.7-xen3

I'll leave it there for a while longer then.

Thanks, will be potentially useful for others as well.

Quote from: franco on August 09, 2024, 08:10:55 AM
Jokes aside this should probably be reported to https://bugs.freebsd.org but at this point I have no hopes somebody even cares giving the number of past and pending issues in that general direction.

Done if someone here wants to chime in there - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280701, I most likely won't have time to follow the usual requested steps to reproduce an apparent bug just because it manifests on OPNsense instead of "vanilla" FreeBSD.

Quote from: franco on August 09, 2024, 09:58:27 AM

# opnsense-update -zkr 24.7-xen3

I'll leave it there for a while longer then.

What are the differences and benefits of that "xen Kernel"?

This was the 24.7.1 kernel state before the FreeBSD security advisories hit yesterday with all pressing user reported things fixed.


Cheers,
Franco

August 09, 2024, 12:22:11 PM #24 Last Edit: August 09, 2024, 12:23:56 PM by doktornotor
@franco - added so far requested info (seems to go well as usual  ::)) to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280701; if people want to take over from there, I really don't have days to debug this. 

Summary:
- 24.7 or 24.7-xen3 -> working traceroute
- 24.7.1 - traceroute broken.
- reproduced on a box with default OPNsense firewall rules, DHCP WAN, default LAN.

Wondering who's testing these patches on "stable" really. Sigh.

So it is not a special kernel which should be generally used with opnsense in a Xen hypervisor scenario?

xen, xen2 and xen3 were test patch iterations while working on IPS/netmap crashes within Xen since the problem appeared with FreeBSD 14.1. It was fixed. It's included in 24.7.1 too.


Cheers,
Franco

Thx Franco for the clarification and your relentless commitment

I'm on a bare metal install and also seeing the ICMP issue on traceroutes. Screenshot of my liveview log attempt to run mtr to one of quad9's IPV6 servers.

Quote from: franco on August 09, 2024, 09:58:27 AM
@doktornotor

# opnsense-update -zkr 24.7-xen3

I'll leave it there for a while longer then.


Cheers,
Franco

Is this supposed to revert to a kernel that has the expected ICMP behavior?