Well if you havent figured it out from the references, try again!
By the way I did see reference to vlan1 here:
My cisco switch is set a Native VLAN ID 9
Trunk Port (Port 24) with native vlan set as
1: I get IP for VLAN 9 ( 192.168.9.0/24 ) - as default and if I tag different VLAN IDs I get those IPs too
Trunk Port (Port 24) with native vlan set as 9 : I do not get anything , nothing nada, total lose unless I set Port 24 native vlan id to
1
and of course here.
VLAD
1D
In other words suggesting set native vlan to one on the cisco so that its the same as other vendors.............
(1) First mistake, three bridges, the point about vlans is you only need one bridge in 99% of cases.
and by the way, the local unused subnet I turned into vlan5, apples and apples, why stick an orange in there???
and by the way, I removed the wan bridge......
(2) Second mistake, horrible nomenclature making a bridge name VLANS, or LAN for that matter.
(3) Annoying, sloppy organization, even the vlans are not ordered 15, then 9 etc.........
(4) Lack of use of interface lists so added real ones (which often can work efficiently with firewall rules)
/interface list
add name=WAN
add name=LAN
add name=Management
(5) Your IP DHCP
client config is screwed, tells one you have some sort of error in that part of the config --- slave error.
Its probably due to your use of bridges for wans - in bridge ports you identify etherports 9, and 10 as being WAN affiliated
I want to know how a single dhcp client setting can be used for two interfaces?? and then you add etherport 5 as well (3 wans?? )
add bridge=WAN comment="Ether9 - VM" hw=no interface=ether9
add bridge=WAN comment="Ether10 - Talktalk FTTC" interface=ether10
/ip dhcp-client
add comment=defconf disabled=no interface=WAN
# DHCP client can not run on slave interface!
add disabled=no interface=ether5
(6) BOTH /interface bridge ports and /interface bridge vlan settings are nowhere near where they should be............ AND Its not clear where the cisco switch is involved in all of this.............
You seem to indicate in text that its providing all the Vlans and if so, then one wouldnt provide DHCP on teh router.
if not which etherport is GOING to the cisco switch??
IN other words, you need to detail what is going out on each etherports 1-8, what are they each connected to dumb device and on which vlan,
or managed device and which vlans are tagged over it, assuming 9,10 are used for wans.
(7) I note that there is an extra POOL config for VPN but no other related IP address, dhcp server etc settings but will assume thats NORMAL for vpn ipsec configs.........
(8) Why identify subnets or vlans in FIREWALL ADDRESS LIST? One can identify them as their interface directly, or by source-address?
Firewall address lists are common for a group of IPs within a subnet or IPs across subnets or any of the former with a subnet or two. In other words anytime you have any grouping with individual IPs involved, its time for a firewall address list.
(9) As noted your firewall rules are disorganized and bloated..........
(10) First sourcenat rule would probably not work how its setup best to use interface-list=WAN where both WANS are identified properly as list members (no bridge required).
(11) What is the purpose of the five disabled sourcenat rules.............. just remove them, all noise.
(12) All your destination nat rules are missing where the port forwarding is coming from or going to...........
Static WANIPs use dst-addresses=actual WANIP
Dynamic WANIPs use in-interface-list=WAN unless you have some users locally that must use wanip to access servers vice the more direct lanip to lanip traffic??
IF so you will likely need to learn about hairpin nat -
viewtopic.php?t=179343