RB750gr3
My networks is 192.168.100.0/24 my local network
port1 → Wan
port2 → Lan
Port3 → Vlan10 with IP 192.168.101.0/24 for share internet to guest wifi
RB941-2nd
Port 1,2,3 and wlan1 is bridge (bridge1) and connected to Lan
Port4 → Vlan10 and bridge (bridge2) with virtual AP wlan2
How to block access to my local network from guest IP range 192.168.101.0/24.
Quick question, it is not clear to me the purpose of the second routerboard?
It would seem you are using it simply or mostly as an access point switch which is vlan aware??
If so how are you connecting the two devices together for the vlans?
I am assuming LAN from the main router is coming out ether2 and going into ether1 of the routerboard, but what about vlan10?
Should I assume it coming out of ether3 and going into ether4 of the routerboard??
Regardless of the current layout, it would appear as though the second RB is simply acting as a switch/bridge. Since all traffic is going to the RB750 for routing, you should be able to create a simple IP firewall filter in the forward chain blocking traffic between the subnets.
You can do this two ways:
Create an address list that contains your local subnets. Then create a filter drop rule that matches the source and destination address list to this rule.
Create two filter drop rules, the first with source 192.168.100.0/24 and destination of 192.168.101.0/24, the second rule using source 192.168.101.0/24 and destination 192.168.100.0/24.
In both cases, if you add additional VLANs/subnets down the road, you will need to adjust these filters to do what you are trying to accomplish. For example, if you add another LAN subnet and you want it to be able to talk to 192.168.100.0/24 but not talk to 192.168.101.0/24, you will need to make sure your rules accommodate that.
I think its a bit clearer
bridge - lan
bridge1 - vlan
(in your original text you had bridge1 - lan and bridge2 - vlan) but I will go with your latest post which matches your config.
So in essence on the RB750 unit, port 3 is a trunk port for vlan10
on the routerboard/ap unit, port 4 is a trunk port for vlan10, however the only output is then to WLAN2 (no other physical ports).
One thing that confuses me on your config for
/ip dhcp-server network is the extra net mask entry???
Mine looks like this…
/ip dhcp-server network
add address=192.168.0.0/24 comment=HomeDHCP dns-server=192.168.0.1 gateway=
192.168.0.1
Your looks like this (how did you get the netmask entry in there, it doesnt show on my config???
/ip dhcp-server network
add address=192.168.101.0/24 dns-server=8.8.8.8 gateway=192.168.101.1
netmask=24 ??
Looking at your filter rules…
For clarity you should separate INPUT CHAIN (first) and then FORWARD CHAIN. Far less confusing.
/ip firewall filter
add action=accept chain=input comment=“Accept Related or Established Connections” connection-state=
established,related MISSING
add action=accept chain=input comment=OpenVPN dst-port=1194 protocol=tcp
add action=drop chain=input comment=“Drop Invalid Connections”
connection-state=invalid disabled=yes (should be enabled).
add action=accept chain=input comment=“Accept Exempt IP Addresses”
src-address-list=“Exempt Addresses” I assume this is for the ADMIN to access the router only from one or two devices? If you need to allow DNS from LAN and VLAN put this requirement in separate input chain rules limited to only DNS.
add action=drop chain=input comment=“Drop all Bogons” src-address-list=Bogons (NOT REQUIRED as you have the below last rule next)
add action=drop chain=input comment=“Drop all other WAN Traffic” disabled=yes (should be enabled)
+++++++++++++++++++++++++++++++++++++++++++++
add action=accept chain=forward comment= “Accept Related or Established Connections” connection-state=
established,related
add action=drop chain=forward comment=“Drop Invalid Connections”
connection-state=invalid disabled=yes (should be enabled)
add action=accept chain=forward comment=“Accept Exempt IP Addresses”
src-address-list=“Exempt Addresses” (Get rid of this one, its too vague/wide in scope and could cause issues)
add action=drop chain=forward comment=“Drop all Bogons” src-address-list=
Bogons
add action=drop chain=forward comment=“Drop all other LAN Traffic”
This is what it could look like if cleaned up a bit and suggestions utilized…
I see no reason why any VLAN user would see any LAN user NOR why any LAN user would see a VLAN user.
Now since on the RB the LAN Traffic is on a bridge and the VLAN is not on the bridge you have layer 2 segmentation. Even if they were on the same bridge, the fact that one is a VLAN also provides L2 segmentation. So on the RB the only way for a cross pollination is perhaps a bad firewall rule. The only one that was suspect for me was the one I recommended to get rid of!
In the routerboard same scenario, the LAN and VLAN are on two different bridges so L2 cross talk is stopped cold (and by the virtue of using VLAN).
However, you now need two forward chain rules and perhaps a third to place just before the drop all rule.
a. allow LAN to WAN traffic
b. allow VLAN to WAN traffic
c. allow admin access too VLAN (optional).