Working top to bottom dont see much yet but need to add servers, allow DNS and get rid of the default static entry…
/ip dhcp-server network
add address=192.168.88.0/24 comment=defconf gateway=192.168.88.1 dns-server=192.168.88.1
add address=192.168.178.0/24 gateway=192.168.178.1 dns-server=192.168.178.1
/ip dns
set allow-remote-requests=yes servers=1.1.1.1,9.9.9.9 (or whatever public DNS servers you prefer)
/ip dns static {remove this entry}
add address=192.168.88.1 comment=defconf name=router.lan
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Next up Firewall Rules: WHY DO YOU SEPARATE CHAINS.. hard to read and prone to making matching error as ORDER COUNTS, besides the duplicates you have going, a mess!!!
HERE IS WHAT I SUGGEST, DISABLE EVERY RULE THAT is not shown below, which is what you need the rest is extra, for now… to get things working.
/ip firewall filter
add action=accept chain=input comment=
“defconf: accept established,related,untracked” connection-state=
established,related,untracked
add action=drop chain=input comment=“defconf: drop invalid” connection-state=
invalid
add action=accept chain=input comment=“defconf: accept ICMP” protocol=icmp
add action=accept chain=input comment=“Full access to SUPPORT address list”
src-address-list=support
add action=accept chain=input comment=
“defconf: accept to local loopback (for CAPsMAN)” dst-address=127.0.0.1
add action=drop chain=input comment=“defconf: drop all not coming from LAN”
in-interface-list=!LAN
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
add action=accept chain=forward comment=“defconf: accept in ipsec policy”
ipsec-policy=in,ipsec
add action=accept chain=forward comment=“defconf: accept out ipsec policy”
ipsec-policy=out,ipsec
add action=accept chain=forward comment=
“defconf: accept established,related, untracked” connection-state=
established,related,untracked
add action=drop chain=forward comment=“defconf: drop invalid”
connection-state=invalid
add action=drop chain=forward comment=
“defconf: drop all from WAN not DSTNATed” connection-nat-state=!dstnat
connection-state=new in-interface-list=WAN
MANGLING - Not required, you can route lan1 to wan1 and lan2 to wan2 without mangling.
Suggesting removing mangling and put fasstrack rule back at the top of the forward chain.
add chain=forward action=fasttrack-connection connection-state=established,related
FROM
/ip route
add distance=1 gateway=192.168.1.1 routing-mark=LAN1_TO_WAN1
add distance=1 gateway=PLDTEnterprise routing-mark=LAN2_TO_WAN2
add distance=1 dst-address=192.168.178.0/24 gateway=PLDTEnterprise
TO:
/ip route
add distance=1 gateway=192.168.1.1
add distance=1 gateway=PLDTEnterprise
add distance=1 gateway=192.168.1.1 routing-mark=88_Subnet
add distance=1 gateway=PLDTEnterprise routing-mark=178_Subnet
Route Rules
/ip route rule
add action=lookup-only-in-table src-address=
192.168.88.0/24 table=88_Subnet
add action=lookup-only-in-table src-address=
192.168.178.0/24 table=178_Subnet
Note: If you want any usage of the other subnet (failover) then use Action: lookup-in-table (and not lookup-only-in-table).