Messages

Yay!  Waiting for this before installing again.

Working here :)

If I run DNSCrypt-proxy and Unbound DNS, do I turn off DNS/TLS? 

- Using OPNsense 23.7.6-amd64.
- I setup an Unbound DNS: Query Forwarding Rule to take care of the old text entry options noted in the older OPNSense tutorial for setting up DNSCrypt-proxy with Unbound DNS, and it seems to work without issue.

So temp will not show under HTOP.  HTOP shows 0.0.% 3000MHz N/A. N/A is where the temp should show.  The 0.0% should show CPU utilization, and the 3000MHz is the incorrectly reported CPU frequency. Tested  using the AMD Ryzen 9 7900x.

Functionally, OPNsense seems to work otherwise, but I wonder if the underpinning BSD operating system is not properly utilizing or optimized for this CPU and AMD 5 Chipset.

newsense, I installed mimugmail's repo yesterday looking for HTOP and did not see it.  Is it by chance under another feature?

There are three selections for sensors, one of those is AMD.  Did not work, and neither do the other two, Intel and I think it is something like APIC.  Also tried a series of CLI commands and nothing literally is reported.

I am running the latest OPNSense on an AMD 7900X as a homelab bench project. It is zippy compared to the Intel I3 have been using.  I have been trying to anticipate the newer firewall options that tend to slow traffic.  Overkill sure, but I had a spare to play with.  Did find one FreeBSD thread that discussed Ryzen 7 support from May 2023.  Mostly laptops in the discussion.  Folks were having a hard time just getting the OS to install.  One noted temps did not work, and I noticed on my workbench today, a similar instance of no temp support, even with the old AMD sensor selected.  Was hoping a forthcoming FreeBSD 14 shift in OPNSense might, just might get it sorted.  I did experience the trials and tribulations of other linux distros getting up to speed with the new hardware in late 2022 and 2023, but I don't typically track BSD distros. Did a spin of PfSense this evening on the CPU, and it has the newer FreeBSD foundation, and no temp joy there in that instance. I'm sure the builders will get around to it at some point.

Any chance we will see support for Temp reporting for AM5 systems?d

Thanks!

Found this post in another forum:

"The new Apple TV 4K supports the new Thread network protocol (https://en.m.wikipedia.org/wiki/Thread_(network_protocol)), which is IPv6 based. Since my network did not have IPv6, the Apple TV created an IPv6 network itself, so the devices on the network would be able to communicate to each other via Thread and to the Apple TV."

I think Sonos also creates its own little network so it can communicate with other Sonos devices.

Locking the DNS in the Apple TV did not fix the debug problem either. 

So using Wireshark, I isolated the debug errors to two Apple TVs.  I went and changed their DNS from automatic to the IP address of the router.  However, these keep showing for the two devices.

4659   109.719105   10.0.0.199   224.0.0.251   MDNS   180   Standard query response 0x0000 AAAA, cache flush fe80::89f:8d31:8766:26ae AAAA, cache flush 2600:4040:b00b:2900:1c39:dadd:666a:a53f AAAA, cache flush 2600:4040:b009:f300::1a1b NSEC, cache flush Master-Bedroom-2.local

I just changed the prefix delegation as you stated and will see what happens from there.

No Joy :( 

Keep getting these:

2023-09-30T08:10:15-04:00
[Error]
opnsense   /usr/local/opnsense/scripts/dhcp/prefixes.php: The command '/sbin/route add -inet6 '2600:4040:b009:f3ec::/62' '2600:4040:b009:f300::1a1b'' returned exit code '1', the output was 'route: writing to routing socket: Network is unreachable add net 2600:4040:b009:f3ec::/62: gateway 2600:4040:b009:f300::1a1b fib 0: Network is unreachable'

None of the IPs shows up in the ARP Table. If I try to convert the IPV6 to IPV4 addresses I get an invalid IP address as well.

Thank you! Found it and set so now will see what happens.  Will report back tomorrow.

Well, it seems there is no "Prevent Release" in the interface settings that I can find...  Wonder it if was deleted when they enabled the lease release capability under Interfaces?

Maurice,

I got around to deleting old IPV6 leases and that did not help.  My router address is different from the one previously listed as b001. They are interestingly very close though.  The new "fake" one is b009 and my actual as of last night was b00b. I know, not making that up... I did deduce that this is a two hour cycle when the debug error messages occur.  Short of a complete reinstall, not sure what else to do now.