Intel NUC just crashed again and reboot.

N8LBV

I'm really new at this.
I'll have to find out what exactly to report or attach and where.
I have dump files presented in the web interface after the crash.
I'm not sure if they contain any sensitive info.
I'm guessing here is not the place to post.
I'll have to try 2.6 and see if it's happy on this hardware.
Hardware passed all memtests and such and a bunch of windows stress tests.
I'm very confident the hardware is not bad.

N8LBV

I'm posting a new thread to try to focus on this and move forward with 1.7
and what to do about this Realtek NIC aside from the obvious to bin it.

stephenw10

Are you still seeing this after switching to the alternative re(4) driver?

N8LBV

@stephenw10 NO. it's working "great" after switching the driver!
It's still not an Intel NIC.

And I will not be putting anything with Realtek out at any customer other than testing.
This was my first ever encounter with Realtek in PFSense :)
It was a little confusing at first mainly because I was testing in PFSense 2.7DEV.
And any post about it was discussed around 2.6.0

I'm still not sure if the driver/driver fix procedure is "different" for 2.7._ than 2.6.0

I pretty much since January have been moving forward with 2.7 due to the problems I had with site-site VPNs in 2.6.0

I could never get those to stay up.
Restarting them was manual , labor intensive and time consuming and a bit frustrating.
Switching to 2.7 in January instantly solved that problem for me.

stephenw10

In realtek-re-kmod pkg is not in the 2.6 repo so it's slightly more difficult to install since you need to pull it from the appropriate FreeBSD pkg repo.
On the other hand 2.6 is built on a FreeBSD release version which means pkgs can be updated from there. 2.7 is built on a FreeBSD 14 snapshot which means most packages will refuse to install or run if you try to use anything from outside our repo.

Steve