Attached.
router20210606.1.rsc (4.64 KB)
Sticking with standard config
change this
/ip dhcp-server network
add address=10.0.10.0/24 dns-server=192.168.0.1 gateway=10.0.10.1
add address=10.0.20.0/24 dns-server=192.168.0.1 gateway=10.0.20.1
add address=192.168.0.0/24 dns-server=192.168.0.1 gateway=192.168.0.1
To this And when we get a working config you can modify back for example…
/ip dhcp-server network
add address=10.0.10.0/24 dns-server=10.0.10.1 gateway=10.0.10.1
add address=10.0.20.0/24 dns-server=10.0.20.1 gateway=10.0.20.1
add address=192.168.0.0/24 dns-server=192.168.0.1 gateway=192.168.0.1
Looking at bridge ports you have base vlan traffic untagged for port 2-5, and For some strange reason you have untagged traffic for VLAN60 on ether6.
It doesnt even exist???
Bridge port 7-10 are for tagged vlan traffic assuming going to smart devices that can read vlan tags.
YOur bridge vlan settings are meaningless. Hard to believe you read the best reference and fell so far short LOL.
Not to worry will work on it.
/interface bridge vlan
add bridge=BR1 untagged=ether6 vlan-ids=60[/i]
Again vlan60 doesnt exist so not sure what you mean by it??
This is the rest of it,
_/interface bridge vlan
add bridge=BR1 tagged=
BR1,ether2,ether3,ether4,ether5,ether7,ether8,ether9,ether10 vlan-ids=
10,20,30,9_9
This tells the router that ports ether2-20 are tagged with vlans 10,20,30,99 ??
Where in the heck did vlan30 come from???
So to match what your bridge ports are saying it would be more like
add bridge=BR1 tagged=BR1,ether7,ether8,ether9,ether10 vlanid=10,20
add bridge=BR1 tagged+BR1,ether7,ether8,ether9,ether10 untagged=ether2,ehtr3,ether4,ether5 vlanid=99 ***
Not sure which tagged vlans 7-10 carry 99 so included all so remove those that dont.,
If you do add an unmanaged switch on etherpor6 and make vlan60 for it, then this is okay
add bridge=BR1 untagged=ether6 vlan-ids=60
Working on this now. So, I owe you an apology for the confusion. I was trying to just get ether2 for my desktop working prior to configuring everything else, so a lot of it was half baked. Before my next upload, I’ll get the rest of it filled out so you’re not chasing red herrings for me. So, sorry anav, you’re helping me a lot and I appreciate it.
Question though, if I’m assigning a pvid to a bridge port would that then be added as tagged or untagged on the bridge vlan configuration? Ether 2-6 will not be tagged by anything other than the router as they’re all going to be devices or that unmanaged switch. (I’m assuming untagged)
Attached latest configuration. Still not able to get out to the internet but getting IPs, desktop on ether2 is getting assigned to vlan30 as expected with an IP.
IPv4 Address. . . . . . . . . . . : 10.0.30.242(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, June 7, 2021 3:32:44 PM
Lease Expires . . . . . . . . . . : Monday, June 7, 2021 3:46:21 PM
Default Gateway . . . . . . . . . : 10.0.30.1
DHCP Server . . . . . . . . . . . : 10.0.30.1
Notes on desired layout, different than original request.
#######################################
# VLAN Overview
#######################################
# 10 = VLAN10 - NAS
# 20 = VLAN20 - Cameras
# 30 = VLAN30 - Trusted Devices
# 40 = VLAN40 - Untrusted Devices (IoT & Guest)
# 50 = VLAN50 - Unmanaged Switch from media center
# 99 = BASE (MGMT) VLAN
#######################################
# Interface Overview
#######################################
# ether1 - WAN
# ether2 - VLAN30
# ether3 - VLAN30
# ether4 - VLAN30
# ether5 - VLAN30
# ether6 - hAP - VLAN 40 & 50, tagged by device
# ether7 - N/A
# ether8 - hAP - VLAN 40 & 50, tagged by device
# ether9 - Netgear Family Room - VLAN 50, untagged
# ether10 - CRS112-8P-4S - VLAN 10 & 20, tagged - Cameras and NAS
router20210607.1.rsc (5.74 KB)
Brdige comes with multiple personalities, they are very well explained in this thread. When assigning PVID to bridge, you’re assigning it to bridge port and bridge port is treated just any other port member of bridge (e.g. ether2). Which means that in this case bridge port will be added as untagged to the bridge vlan configuration (unless you manually override that with explicit configuration in which case you risk of messing things).
There are a few problems with your posted configuration:
- ports ether2,ether3,ether4,ether5 are set as untagged members of both VLAN IDs 30 and 99 in bridge vlan configuration. That’s not right, each port can only be member of one VLAN untagged and that should be the one with PVID set (in bridge port configuration).
- your WAN interface is (I guess) pppoe-out1. Not e1-201 and not ether1. So you should set it correctly in /interface list member. This is probably the show stopper about your non-working internet.
Thanks MKX, I missed that pppoe-1 out thing all this time, not ever using it for anger I thought that if it was the type that was assigned a vlan like my bell fibre it was the vlan that was the client.
My apologies to the OP for not picking up on that…
Where I disagree with my esteemed colleague, who wishes he was in the land of maple syrup and no architecture, is the bridge vlan filtering setup.
As stated, ONLY one pvid (one untagged subnet) can be set on any port. I think you can logically understand that as if you had two streams of untagged traffic coming out a wire, how the heck would a dumb or smart device deal with that??
In MT routers, once you designate a pVID, the router will automatically fill in the bridge vlan untagged setting for the correct pvid DYNAMICALLY. Which means, that you dont have to do it on the config. So technically correct. However I Always do manually insert them. WHY because when I make my config I like to map one to one all my settings from the bridge port to the bridge vlans.
The automagic method means that you dont see any entries in the bridge vlan confg when
a. constructing the config
b. troubleshooting the config.
I rely on a more positive handover type approach to life and thus like to touch, and feel the config visually seeing the relationships between bridge ports and bridge vlans, I dont do so well interpolating. Less talented than MKX (in that regard) ![]()
So its personal preference, he is afraid of making errors, I am simply ensuring I dont have errors… do you want to live in the fear state of mkx, or the positive assurance method of anav LOL.
The important thing is I think we are there!!!
As for the config as noted by mkx
(1) /interface list member
add interface=ether1 list=WAN
add interface=pppoe-1out list=WAN or whatever its called is require.
(2) Issues with bridge port. Ethe6 iif untagged requires a PVID. Ether9 if an access port and pvid is correct, change frame types!!.
/interface bridge port
add bridge=BR1 frame-types=admit-only-untagged-and-priority-tagged
ingress-filtering=yes interface=ether2 pvid=30
add bridge=BR1 frame-types=admit-only-untagged-and-priority-tagged
ingress-filtering=yes interface=ether3 pvid=30
add bridge=BR1 frame-types=admit-only-untagged-and-priority-tagged
ingress-filtering=yes interface=ether4 pvid=30
add bridge=BR1 frame-types=admit-only-untagged-and-priority-tagged
ingress-filtering=yes interface=ether5 pvid=30
add bridge=BR1 frame-types=admit-only-untagged-and-priority-tagged
ingress-filtering=yes interface=ether6
add bridge=BR1 frame-types=admit-only-vlan-tagged ingress-filtering=yes
interface=ether8
add bridge=BR1 frame-types=admit-only-vlan-tagged ingress-filtering=yes
interface=ether9 pvid=50
add bridge=BR1 frame-types=admit-only-vlan-tagged ingress-filtering=yes
interface=ether10
(3) The Bridge vlans is a bit messy, lets try to clean up…
/interface bridge vlan
add bridge=BR1 tagged=BR1,ether10 vlan-ids=10,20
add bridge=BR1 tagged=BR1**,ether6**,ether8 vlan-ids=40
add bridge=BR1 tagged=BR1 untagged=ether9 vlan-ids=50
add bridge=BR1 tagged=BR1,ether6,ether8 untagged=ether2,ether3,ether4,ether5
vlan-ids=30
add bridge=BR1 tagged=BR1,ether8,[color=#008000çether9[/color],ether10 untagged=
ether2,ether3,ether4,ether5,ether6 vlan-ids=99
@mkx This is a perfect illustration of why ITS IMPORTANT TO MANUALLY CONFIGURE THE BRIDGE VLAN SO THAT AN UNDERSTANDING OF THE FUNCTIONALITY IS GAINED PRIOR TO USING IT AUTOMAGICALLY!!!
NOTES: There are three types of ports on the MT devices.
Bridge ports
a. trunk port = only allow tagged frames / no pvid / ingress filtering yes
b. access port = only allow priority and untagged frames / PVID required / ingress filtering=yes
c. hybrid port = PVID required
Bridge vlan filtering
i. Trunk ports: tagged for all appropriate vlan-ids (bridge for trunk ports normally tagged as well)
ii. access ports: untagged for all appropriate vlan-ids (mt router does this part automagically if you dont manually assign but not visible in config)
iii. hybrid ports: untagged for single pvid, (see i. for tagged vlans)
note: Devices at other end of hybrid port must be able to deal with untagged and tagged vlans (typically voip phone [tagged goes to phone, untagged goes to PC] or ubiquit wifi,[untagged management vlan to device, tagged vlans for wlan]
anav & mkx … thank you! I have IPs being assigned and I’ve got internet access. Few new questions…
- Enabling the following rules drops my WinBox access on the router. Can’t access the AP or Switch regardless if I’m connected to those. This was taken directly from the example configurations in the references forum post.
/ip neighbor discovery-settings set discover-interface-list=BASE
/tool mac-server mac-winbox set allowed-interface-list=BASE
/tool mac-server set allowed-interface-list=BASE
- Maybe more of a request for direction as you two seem well acquainted with good links, but firewall holes. Now that I have things separated I need to start poking holes. How do I allow traffic to go between two different vlans (from specific devices and/or specific ports)?
I can do the config export if requested, will just be tricky now that I don’t have consoles… have to reset everything. Attached the files used to configure.
MikroTikRouter.rsc (10.5 KB)
MikroTikSwitch.rsc (4.73 KB)
MikroTikAP.rsc (6.1 KB)
Well the source-address-list entry on the input chain for base vlan interface access to the router was optional.
If you have that added and no source address list entries, yeah no way .
So drop the firewall address list or populate it…
Also I have no idea what vlan you are on when trying to get at the router are you on vlan99 (base vlan) or something else…
For additional allow rules between vlans you need to add accept rules for that traffic in the forward chain
Ah, I missed that. I’ve removed that rule for now and have access to the router with winbox from any of the vlans. Still can’t access the switch or AP from winbox.
No need to remove the rule just the part that was blocking…
As for the other items,
a. does a tagged vlan99 reach the smart devices?
b. do the smart devices have IP addresses on the base vlan?
The device I’d like to configure from is on VLAN30 connecting from ether2 on the MikroTik hAP. In winbox, I can see the router but not the hAP. I believe all of my networking devices have an IP in the BASE_VLAN (99)
#######################################
# IP Addressing & Routing
#######################################
# LAN facing AP's Private IP address on a BASE_VLAN
/interface vlan add interface=BR1 name=BASE_VLAN vlan-id=99
/ip address add address=192.168.0.3/24 interface=BASE_VLAN
# The Router's IP this AP will use
/ip route add distance=1 gateway=192.168.0.1
EDIT: Separate test, I can telnet to the devices through my router in winbox. Not sure its really related, but might shed light on the issue
Got it… had to punch a hole in FW for it.