You can connect, it’s just that traffic through your tunnel is blocked. The typical solution to this is to add the wireguard interface to the LAN list.
Are you running both Wireguard as the back-to-home option and as the manual added version? Why do you have port 51820 open in your firewall (it is not used by Wireguard according to your configuration).
What endpoint are you using on the device for connecting to home? Do you test it from outside?
As indicated you have to provide much more detail on your requirements for wireguard.
identify all users and the traffic they need
Do you have public IP address?
how many wireguard interfaces are you using?
Am using for remote access … Back to home I use my smartphone… The wireguard is for my Laptop… When am away from home… I have only one Wireguard interface… Soon a I disable the Block all from LAN rule Wireguard works perfectly… But I don’t want to disable this rule
You failed to answer the important question. Do you have a public IP address on the MT router or can you port forward from an ISP modem/router that gets a public IP??
So far you are the only user and use wg on two devices when remote from home to
a. connect to home devices?
b. to connect to router for config purpose?
c. to access internet of home??
My modem is in bridged mode… I have pppoe and I can use the IP cloud domain name to access… I remote VPN to my home to access PC or devices on my network…
Try enabling logging for this “Block from LAN” rule and see what is being dropped.
Your exports above don’t show this rule. Something else must be also missing since you say one thing, but the config is saying a different thing. If you block all traffic from LAN, where do you allow it? The usual approach is to allow what you need and drop everything else. I don’t see anything allowed. The firewall lists are not shown in the firewall rules either.