The 'enagent' is coming from the unbound package I had installed. I can disable that.
Can all of these scenarios be achieved on a single device -- yes, but it's far more complicated.
It's how it is now and it's working perfectly. The only problem is this odd gateway issue. I didn't pick one or the other because I use them all in different ways.
You need to understand why your packets are dying in transit
That's why I posted, looking for ideas on how I can monitor the problem to come up with points to look at. Right now, it's not clear at all what is causing this because it's only happening with this 23.03 router.
Nothing else on the LAN is seeing this issue which tells me it's nothing on my main firewall and something to do with my openwrt network configuration.
If I had to guess, perhaps a incorrect firewall rule improperly mangling or redirecting packets (???)
I eliminated that because the same router, running 18.x.x., connected to the same cable was not experiencing this problem. I would have noticed it.
Since your config provide us nothing, it's hard to tell why
Agreed and it's why I posted looking for ideas. While the syntax of the file may not be optimal, it does work, albeit, with this odd gateway issue.
Your 192.168.0.1 and 192.168.1.1 devices are informing you that packets died in transit
if you don't understand why this is an issue, feel free to ask more questions
I understand why this is an issue and is why I posted :).
I'm out of ideas in terms of how to diagnose this.
The first step might be to correct the syntax/directives in the network files?
I can't share the 192.168.1.1 config, it's huge and it's pfsense. What config aspect might I share that could help?
openwrt router (192.168.1.5)
--- pfsense firewall on LAN (192.168.1.1)
------ providers modem (192.168.0.1) with DHCP handing static IP to pfsense