Messages

mtr works for me too on icmp2. ipv4 & ipv6.

-icmp2 working for me too.

# opnsense-revert opnsense && opnsense-patch 3a9f98843b 182bab339a

Working the same here too.

@csutcliff did you use IPv4 connectivity setting? It's gone from the GUI but I suppose you did because you said it keeps working.

Since when did you start using this anyway? 24.1.9?


Cheers,
Franco

Yes I was previously using this setting, I think since March 2021 when I first got ipv6 enabled with a previous ISP. At least

Code Select Expand

<dhcp6usev4iface>1</dhcp6usev4iface> is present in my oldest backup from June 2022.

Ok, so far so good. :)

Finished the POC: https://github.com/opnsense/core/commit/e6f0ac158dc

# opnsense-revert opnsense && opnsense-patch e6f0ac158dc

If all goes well it should start dhcp6c automatically now in the latest config you mentioned.

IPv4 connectivity setting is gone now and the default. You need it anyway since you want DHCPv6 over PPPoE.


Cheers,
Franco

Tested this and it seems to continue working as normal with my UK PPPoEv4 and DHCPv6 setup.

I still have the gateway monitor issue that started with 24.7 where the ipv6 gateway monitor won't start with a public ipv6 monitor IP set. It works fine with nothing set and using the default gateway IP as the monitor. WAN & gateway are fe80 link local addresses with my public prefix on LAN which may be relevant.

I have the same issue with the smart plugin.

Regarding the CPU temperature, the new widget will only show the first core if all the cores report the same temperature. If they differ it will expand to show them individually.

had my first crash with rc2 (debug kernel), submitted the report and put a link to the kernel.0 in the notes.

csutcliff, you are our only hope!

You're a prime candidate for the RC2 debug kernel since you have that non-obvious ip6_input() crash.


Cheers,
Franco

Thank you, I wasn't sure if I was "the one" since I didn't save the output from the crashes, only submitted it to you

I'm already on the rc2 but I'll install that debug kernel now.

just sent another crash report for 24.7.r1_7

Just to make sure we're on the same page here, there can be crashes in programs that you can report from the GUI, restart said program and everything else on the FW continues working normally. The OPNsense team receives the crash reports and the issue is fixed one way or another and available shortly in an update.


This thread is about kernel panics on 24.1.r1 and the OS being rebooted automatically --  of which I had none for the last few kernels I tested on 3 FWs.

Uptime on 24.7.r1_7 is now over 10 hours.

Yes I'm talking about kernel crashes where it dumps page after page of debug into the screen and reboots, I'm submitting the reports it has generated after reboot which do include kernel dump info etc. had 2 kernel crashes with _7 yesterday but none so far today.

just sent another crash report for 24.7.r1_7

I haven't seen any crash report with the particular stack trace today matching any of _2, _5 or _7 so far. Also no crash on my main production box.


Cheers,
Franco

I've sent two, one on _5 and one on _7. Have no idea if they made it to you since there is no feedback after sending. I did wait until the wan was up before submitting (since 24.7 the pppoe connection takes a few minutes to come up after reboot)

Edit: just realised you are meaning there is nothing matching this specific crash.

I have intel nics and still crashing every few hours with  _5 kernel. (sent crash reports)

Yes, I believe the test kernel is otherwise the same as vanilla 22.7.5 & 22.7.6 kernel just with that change reverted.

Fix here:

https://www.reddit.com/r/opnsense/comments/xw4oiz/comment/ir4vchi/?utm_source=share&utm_medium=web2x&context=3

https://forum.opnsense.org/index.php?topic=29916.0

It's a bug in 22.7. Revert to 22.1 for now

I think I've got some attention on this via Reddit.