Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - darkcrucible

#1
Looks like the RRD issue was due to an unrelated issue fixed with the most recent hotfix.
After a reset of the NetFlow data, I see flowd.log* in the tmpfs version of /var/log. It now comes back after a reboot as well. Everything seems fine. Perhaps it was the shortlived upgrade to 24.7.11 before 11_2.
#2
I was trying to reduce the number of writes to disk by turning on the RAM disk option for /var/log and /tmp.
When I rebooted, RRD stopped working but netflow was still operational. I noticed that disk usage was not going down much and the flowd.log* files were missing in the new /var/log. There are other files not present in the ramdisk like pf.today, ipfw, etc. Those appear to persist on the disk but are not used on the ram disk.

When looking at the mounts, in the system there are two for /tmp and /var/log:
zroot/tmp                    213G    948K    213G     0%    /tmp
tmpfs                        7.8G    580K    7.8G     0%    /tmp
zroot/var/log                213G     89M    213G     0%    /var/log
tmpfs                        7.8G    3.1M    7.8G     0%    /var/log

Is the tmpfs being mounted too late?
I think you can "over mount" a file system in a folder that's in use. Processes that are using the original FS's stuff will continue to do so. This kind of defeats the purpose of the ram disk. Am I all mistaken on this?
#3
Unfortunately my ISP does not offer native IPv6. The best they offer is 6rd which is too bad.

Anyways I've been using opnsense since 24.7.1. I believe this issue has affected all dot releases since then. I still see this on 24.7.6.

If I reboot the opnsense box, radvd and the LAN's dhcp6 fail to load. There's not much special on my setup. I use manual outbound NAT for static port (have outbound for link-local & LAN networks). I also set the MTU of WAN to 1500. I think even disconnecting the WAN Ethernet for a moment then reconnecting can trigger this too.

I'll get messages like this:
2024-09-29T12:11:30-07:00       Warning radvd   sendmsg: Can't assign requested address
2024-09-29T12:11:30-07:00       Warning opnsense        /usr/local/etc/rc.bootup: dhcpd_radvd_configure(auto) found no suitable IPv6 address on lan(igc1)


Perhaps radvd/dhcpdv6 is being started too soon before 6rd is done? Just speculation

Last thing to note for now, if I restart the radvd & dhcpd6 services then IPv6 works as normal. Any reboot requires manually logging in to restart the services.