eibgrad
Part of the Furniture
Not say I am happy but I was kinda ‘lonely’ with my problem.
So, it looks up Purana has same issue with mine… unfortunately
Let’s hope for a solution or maybe some workaround
Without it we must stick with old firmware atm.
Thanks in advanced
I'm not sure it is the same. You have introduced Wireguard into the picture, whereas (at least so far) @Purana has NOT.
As I said before, I'm still baffled why Wireguard is part of the discussion. As far as I can tell, it appears you have a functional, bi-directional, site-to-site OpenVPN tunnel between site A and B. I'm guessing you want to add accessibility to either site A or B *remotely* using Wireguard rather than OpenVPN, and that has created a conflict. Even using a remote OpenVPN client into site A instead of Wireguard could to lead to conflicts. I have seen users mistakenly using the same IP network on the co-located OpenVPN client and server tunnels (10.8.0.x), when in fact they need to be different. But Wireguard opens the door to other unknowns (at least to me; I don't have access to it w/ my AC68U). These VPNs typically manipulate both the routing tables and the firewall, increasing the likelihood of conflicts. But w/ nothing but your description to go by, I'm left to guess where that conflict lies.