"
Hi,
Thanks for your reply but I think I resolved it. After many hours of tshooting and reconfig here are some "lessons learned" for me that might help:
1. Disable any ISP/IDS services. It was CrowdSec that was triggering that "Permission denied".
2. Make sure the interface naming/assignment is exactly as it was prior to upgrade. I had to create dummy vlans so that opt9 would be assigned to my desired interface so that things would start to work again. (maybe there are better ways but hey, it worked!)
3. Double check fw rules, they might seem fine but a Gateway in a random lan/vlan might be set to "none" and the weirdness start.
4. WireGuard should be called WierdGuard, why it worked sometimes and sometimes not, why sometimes it was using my dns and sometimes none at all or why every time I rebooted opnsense something got fixed and something else broke, I could not figure it out.
Seems like network goblins keep following me even after i leave the office.
Maybe these are common knowledge for you but for me it was a nice learning session. As of now everything seems to be back in order.
regarding "Notice kernel <7>[4458] arpresolve: can't allocate llinfo for 192.168.3.5 on ix0" it might have been related to some misconfigured FW rule that made WAN believe that client was connected to it in L2, but did not have time to investigate further as i haven't noticed it anymore in the logs (FW rule tinkering might have fixed it).
Thanks for your reply but I think I resolved it. After many hours of tshooting and reconfig here are some "lessons learned" for me that might help:
1. Disable any ISP/IDS services. It was CrowdSec that was triggering that "Permission denied".
2. Make sure the interface naming/assignment is exactly as it was prior to upgrade. I had to create dummy vlans so that opt9 would be assigned to my desired interface so that things would start to work again. (maybe there are better ways but hey, it worked!)
3. Double check fw rules, they might seem fine but a Gateway in a random lan/vlan might be set to "none" and the weirdness start.
4. WireGuard should be called WierdGuard, why it worked sometimes and sometimes not, why sometimes it was using my dns and sometimes none at all or why every time I rebooted opnsense something got fixed and something else broke, I could not figure it out.
Seems like network goblins keep following me even after i leave the office.
Maybe these are common knowledge for you but for me it was a nice learning session. As of now everything seems to be back in order.
regarding "Notice kernel <7>[4458] arpresolve: can't allocate llinfo for 192.168.3.5 on ix0" it might have been related to some misconfigured FW rule that made WAN believe that client was connected to it in L2, but did not have time to investigate further as i haven't noticed it anymore in the logs (FW rule tinkering might have fixed it).
