After prodding this and stephenw10 not finding the NDI, I went back and reactivated the subscription keys I had obtained today and it worked.

I had attempted to do this yesterday but it hard-failed so something between yesterday and today 'unbroke' or something really odd was going on at the NG side of things. At least I'm getting package update lists again.

@jrey said in Grep logs for last hour?:

You could also just ask for the entire hour for the previous hour, regardless of when you start it in the current hour.

this would give you the detail of every record

grep "$(date -v -1H +'%b %d %H:')" /var/log/resolver.log | grep "Restart"

This worked out perfectly for what I was doing. Thanks.

@stephenw10 said in Not getting a DHCP WAN IP Address on netgate hardware.:

The ISP gateway may not appear in a traceroute.

The gateway's address might not appear. However, if it doesn't the hop still does and is indicated by an "*".

I forked this topic since this is not an issue with the driver.

Either test using a different client if you can.

Or test from Windows using the IP address of the LAN IP directly like: nslookup wikipedia.org 192.168.100.1

@NollipfSense said in Is Netgate Management Asleep at the Wheels?:

Some of the members here are corporate executives and board governance member...we're all not fools...

You got it!

Ted

No it won't fall over. It simply won't re-install any packages that are not present in the repo.

Steve

Anything that was happening in 2019 is unlikely to apply to current pfSense. A lot has changed.

We may have strayed from the topic here. 😉

@PhlMike And you're trying to fit a camel through the eye of a needle.

Use a hurricane tunnel then. At least they'll have a /48 to use instead of a useless portion of a /112.

IPv6 simply cannot be tested in any meaningful manner without at least a /56 routed to your customer.

@NollipfSense Yes, it is nice, but I push forward, towards things that I think are more helpful

Yes, it's a known issue. The fix for it is not as easy as it initially seems.

In fact it's two issues. The Space used is incorrectly shown. The automatic BE snapshots created do not check the available space. Both are in the pipeline.

Steve

You can edit the config directly and swap out the igb NICs for igc. Then import it; opt2 will still be ovpns1. Then add the additional igc interfaces.

Steve

@stephenw10 Cool, added a feature request at https://redmine.pfsense.org/issues/14931

@stephenw10
Ahh ok. I’m ignorant when it comes to this stuff. I thought a certain software needed a certain version to be compliant.

@stephenw10 said in Unusual Booting Up Message:

No I doubt it, that wouldn't affect routes added on vtnet1.

That's what was revealed when I reboot...it's still complaining...I may reinstall again.

Yes, that is a bug. It's fixed in 23.09.

Steve

@stephenw10 Yup! That was it. Changing to use the serial interface on the device seemed to work. Thank You!

@ChaosBlades Since the changes announcement of pfsense plus, you can try using this bypass on 2.7CE. https://github.com/MonkWho/pfatt. I had this running on 2.6CE, but at the time I went to Pfsense plus to use the built in AT&T bypass. I don't know if this will run in 2.7CE, I will need to downgrade from Plus to CE at some point, but since I am running the built in bypass I cannot do that easily. Maybe CE will get this feature in a future release.

Hmm, so something dynamic that survives a reboot but is not in the config. 🤔

Hmm, hard to say then. It sounds like the network stack stopped forwarding but the kernel was still running.

I guess I'd try again and grab logs covering the event. If it happens again.

Steve