You have hidden way to much information, just the WAN public information and the only thing that would relevent is the username and password on pppoe.
1. Improve Interface list entries, but I dont see a trusted or management vlan?? Ahh you are mixing apples and oranges. Once you go vlans so will change BRIDGE LAN to a vlan and call it home vlan.
In vlan filtering its practice to not have the bridge do any dhcp, much less confusing and less error prone.
/interface list
add name=WAN
add name=LAN
add name=TRUSTED
/interface list members
add interface=pppoe-out (???) list=WAN
add interface=1.2 list=LAN
add interface=1.3 list=LAN
add interface=1.4 list=LAN
add interface=1.5 list=LAN
add interface=1.1 list=LAN
add interface=1.1 list=TRUSTED
/ip neighbours discovery
set discover-interface-list=TRUSTED
/tool mac-server
set allowed-interface-list=NONE
/tool mac-server mac-winbox
set allowed-interface-list=TRUSTED
add comment=admin-home interface=bridge1 name=bridge1.1 vlan-id=11
/ip dhcp-server
add add-arp=yes address-pool=192.168.50.0/24 interface=bridge1.1 lease-time=8h \
name=192.168.50.0/24
/ip address
add address=192.168.50.1/24 interface=bridge1.1 network=192.168.50.0
NOTES:
a. you seem to have two or three WANS, please explain
b. you are missing a DHCP server for
vlan 1.2 ??
c. you seem to have two separate wireguard interfaces, one being for the router (its the server assuming for admin to access router and LAN)?
and the other is for windscribe and to clarify only for one user??
Other observations
SET INTERNET DETECT TO
NONE, its known to cause issues.
See this article for /interface bridge ports and vlans...........
viewtopic.php?t=143620
To configure for vlans,
What i recommend is create an offbridge port for local emergency access.
So remove etherX from /interface bridge port settings.
Modify the following entry
/ethernet
set [ find default-name=etherX ] name=OffBridgeX
Give it an Ip address
/ip address
add address=192.168.77.1/30 interface=OffBridgeX network=192.168.77.0
Add it to the Interface List Members
/interface list
add name=TRUSTED
/interface list member
add interface=bridge1.1 list=LAN
add interface=OffBridgdeX list=LAN
add interface=bridge1.1 list=TRUSTED
add interface=OffBridgdeX list=TRUSTED
Now you should be able to plug your laptop into ether24, change the IPV4 settings on the laptop to 192.168.77.2, then using winbox enter the router with username and password.
Do all the initial config here as well!
Note the netmask of 30 on the address only allows two addresses to work on the router, .1 and .2.
+++++++++++++++++++++++++++++++
Ran out of time will look at rest of config later.
I had a few more minutes and the rest of the config is a bloated mess. You have strived for complex when simplicity is the key to success.
Simple is often more secure as well and your attempts to allow direct access to the router via public addresses is a big security error.
Access to the router should only be done when behind the router either from a trusted subnet or after coming in on a vlan.
Firewall rule should focus on allowed traffic, not blocking traffic, and simply drop all else at the end of each chain.