Your VLAN configuration doesn't look totally correct.
Maybe this will help: https://wiki.mikrotik.com/wiki/Manual:L ... idged_VLAN
But if the routers are the only network equipment, then why use VLANs at all? Just make two bridges and route them normally.
/interface bridge
add name=bridge vlan-filtering=yes
/interface bridge port
add bridge=bridge interface=ether2
add bridge=bridge interface=ether7 pvid=200
add bridge=bridge interface=ether8
/interface bridge vlan
add bridge=bridge tagged=bridge,ether8 untagged=ether7 vlan-ids=200
/ip address
add address=192.168.1.5/24 interface=bridge network=192.168.1.0
/interface bridge
add name=bridge vlan-filtering=yes
/interface bridge port
add bridge=bridge interface=ether1
add bridge=bridge interface=ether2
add bridge=bridge interface=ether3 pvid=200
add bridge=bridge interface=ether4 pvid=200
/interface bridge vlan
add bridge=bridge tagged=bridge,ether1 untagged=ether4 vlan-ids=200
/ip address
add address=192.168.1.6/24 interface=bridge network=192.168.1.0
Only one bridge. Since 6.41+ bridges on RouterOS is VLAN aware.
Why you get loop, I am not sure.
So it seems that first 8 ports are - what we call them here - hybrid ports with internet untagged and VoIP tagged, while the rest of ports are access ports with only internet.But I discovered if I connect a computer to the first 8 ports, I have internet and the same network that the other ports, but if I connect the phone here, I got 172.16.x.x IP in the phone (only access in the menu in the phone for watching the IP)..
So it seems that first 8 ports are - what we call them here - hybrid ports with internet untagged and VoIP tagged, while the rest of ports are access ports with only internet.But I discovered if I connect a computer to the first 8 ports, I have internet and the same network that the other ports, but if I connect the phone here, I got 172.16.x.x IP in the phone (only access in the menu in the phone for watching the IP)..
The trick now is to discover which VLAN ID is used for VoIP. You can try to find that info from phone's menus (VLAN ID is a number between 1 and 4000-something).
If you won't be able to find it, you could try to get it the hard way: plug RB between phone and VoIP port (use two ports on RB that are members of bridge, disable HW offload so that traffic will pass RB's CPU) and sniff traffic off the port where phone is plugged in. Even though registration might fail, there will be some tries using the right VLAN ID.
Since the ISP cannot guarantee what devices may or may not be able to do (feature set), then I would suggest its a hard coded VLAN number (as mkx suggested).
If so then for for the setup I would use the following:
192.168.1.5: (OFFICE ROUTER)Code: Select all/interface vlan add interface=voip-bg name=VOIP-VLAN vlan-id=200 add interface=voip-bg name=Data-VLAN vlan-id=100 add interface=voip-bg name=ISP-vlan vlan-id=3 /interface bridge add admin-mac=CC:2D:E0:2F:07:5C auto-mac=no name= \ voip-bg protocol-mode=none vlan-filtering=yes /interface bridge port add bridge=bridge interface=ether7 add bridge=bridge interface=ether8 /interface bridge vlan add bridge=voip-bg tagged=voip-g,ether7,ether8 \ vlan-ids=200,100,3
----------------------------
Now 192.168.1.6
...Code: Select all/interface bridge add admin-mac=CC:2D:E0:D8:6C:16 auto-mac=no comment=defconf name=Roombridge \ vlan-filtering=yes /interface bridge port add bridge=Roombridge interface=ether1 add bridge=Roombridge interface=ether4 /interface bridge vlan add bridge=Roombridge tagged=Roombridge,ether1,ether4 \ vlan-ids=200,100,3 /interface vlan add interface=Roombridge name=VOIP-VLAN vlan-id=200 add interface=Roombridge name=Data-VLAN vlan-id=100 add interface=Roombridge name=ISP-vlan vlan-id=3
I will assume there is no need to assign DHCP settings for VLAN3 as the voip modem or systems will take care any assignment requirements???
Also, if this is a vlan ISP connection then the op would have to:
a. create an ethernet interface for the ISP (ISP INTERNET)
b. create vlan6 with the parent interface being the ethernet interface in a. (ISP INTERNET)
Otherwise how is the OP getting internet???
[img size=100]h**p://speedtest.ookla.com/result/2186635528.png[/img]
[img size=100]h**p://www.speedtest.net/result/6406510704.png[/img]
/interface vlan
add interface=voip-bg name=VOIP-VLAN vlan-id=3
/interface bridge
add admin-mac=CC:2D:E0:2F:07:5C auto-mac=no name= \
voip-bg protocol-mode=none vlan-filtering=yes
/interface bridge port
add bridge=bridge interface=ether7
add bridge=bridge interface=ether8
/interface bridge vlan
add bridge=voip-bg tagged=voip-g,ether7,ether8 \
vlan-ids=3
/interface bridge
add admin-mac=CC:2D:E0:D8:6C:16 auto-mac=no comment=defconf name=Roombridge \
vlan-filtering=yes
/interface bridge port
add bridge=Roombridge interface=ether1
add bridge=Roombridge interface=ether2
add bridge=Roombridge interface=ether3
add bridge=Roombridge interface=ether4 ingress filtering=yes pvid=3
/interface bridge vlan
add bridge=Roombridge tagged=Roombridge,eth1 \
untagged=eth4 vlan-ids=3
/interface vlan
add interface=Roombridge name=ISP-vlan vlan-id=3
/interface vlan
add interface=voip-bg name=Data-VLAN vlan-id=100
add interface=voip-bg name=ISP-vlan vlan-id=3
/interface bridge
add admin-mac=CC:2D:E0:2F:07:5C auto-mac=no name= \
voip-bg protocol-mode=none vlan-filtering=yes
/interface bridge port
add bridge=bridge interface=eth6 ingress filtering=yes pvid=100
add bridge=bridge interface=ether7
add bridge=bridge interface=ether8
/interface bridge vlan
add bridge=voip-bg tagged=voip-g,ether8 \
untagged=eth6 vlan-ids=100
/interface bridge vlan
add bridge=voip-bg tagged=voip-g, ether7,ether8 \
vlan-ids=3
/interface bridge
add admin-mac=CC:2D:E0:D8:6C:16 auto-mac=no comment=defconf name=Roombridge \
vlan-filtering=yes
/interface bridge port
add bridge=Roombridge interface=ether1
add bridge=Roombridge interface=ether2 ingress filtering=yes pvid=100
add bridge=Roombridge interface=ether3 ingress filtering=yes pvid=100
add bridge=Roombridge interface=ether4 ingress filtering=yes pvid=3
/interface bridge vlan
add bridge=Roombridge tagged=Roombridge,ether1 \
untagged=eth2,eth3 vlan-ids=100
/interface bridge vlan
add bridge=Roombridge tagged=Roombridge,ether1 \
untagged=eth4 vlan-ids=3
/interface vlan
add interface=Roombridge name=Data-VLAN vlan-id=100
add interface=Roombridge name=ISP-vlan vlan-id=3
Yes, the config is for you and assumes the router port connected to the ISP switch is ether7, and the router port connected to the ubiquiti is ether8.
The question remains, why vlan100, and I assume its because you want the data from the ROOM connection to go straight to the internet and not have access to your LAN necessarily.. If so, then you have to be able to tag the ROOM data (PCs) with vlan100. We can replace the vlan200 with Vlan3 and no requirement for DHCP is my conclusion????
Therefore I see two cases.
One can use one port for both data and voip or you can use one port for data and one port for voip (probably better for traffic separation troubleshooting and cconfiguration).
In Case A, I potentially see a problem of duplicating/conflicting internet traffic from two sources in Case B we can isolate due to using vlan for data. Assuming voip vlan is on vlan id:3
Room router has ubiquite connection on ether1 and data going to etherports2,3 and VOIP going on ether4. Case A below describes one big happy LAN that all users share - no separation.
Case B describes the ROOM network as vlan100 and totally separate from the rest of the LAN. If you want to enable any routing between VLAN100 and the regular LAN or vice versa it can be done with firewall rules.
Case A. One LAN, One VLAN for VOIP (ONE PORT FROM SWITCH to PORT 7 of main router, data travels on default VlanID:1)
.15
Code: Select all/interface vlan add interface=voip-bg name=VOIP-VLAN vlan-id=3 /interface bridge add admin-mac=CC:2D:E0:2F:07:5C auto-mac=no name= \ voip-bg protocol-mode=none vlan-filtering=yes /interface bridge port add bridge=bridge interface=ether7 add bridge=bridge interface=ether8 /interface bridge vlan add bridge=voip-bg tagged=voip-g,ether7,ether8 \ vlan-ids=3
.16
Code: Select all/interface bridge add admin-mac=CC:2D:E0:D8:6C:16 auto-mac=no comment=defconf name=Roombridge \ vlan-filtering=yes /interface bridge port add bridge=Roombridge interface=ether1 add bridge=Roombridge interface=ether2 add bridge=Roombridge interface=ether3 add bridge=Roombridge interface=ether4 ingress filtering=yes pvid=3 /interface bridge vlan add bridge=Roombridge tagged=Roombridge,eth1,eth4\ vlan-ids=3 /interface vlan add interface=Roombridge name=ISP-vlan vlan-id=3
Case B - OneLAN, One VLAN for data, One VLan for VOIP Two ports from the switch are used into ports 6,7 but we isolate port 6 just for data on vlan7 and port7 just for voip.
.15
.16Code: Select all/interface vlan add interface=voip-bg name=Data-VLAN vlan-id=100 add interface=voip-bg name=ISP-vlan vlan-id=3 /interface bridge add admin-mac=CC:2D:E0:2F:07:5C auto-mac=no name= \ voip-bg protocol-mode=none vlan-filtering=yes /interface bridge port add bridge=bridge interface=eth6 ingress filtering=yes pvid=100 add bridge=bridge interface=ether7 add bridge=bridge interface=ether8 /interface bridge vlan add bridge=voip-bg tagged=voip-g,ether6, ether7,ether8 \ vlan-ids=100,3
Code: Select all/interface bridge add admin-mac=CC:2D:E0:D8:6C:16 auto-mac=no comment=defconf name=Roombridge \ vlan-filtering=yes /interface bridge port add bridge=Roombridge interface=ether1 add bridge=Roombridge interface=ether2 ingress filtering=yes pvid=100 add bridge=Roombridge interface=ether3 ingress filtering=yes pvid=100 add bridge=Roombridge interface=ether4 ingress filtering=yes pvid=3 /interface bridge vlan add bridge=Roombridge tagged=Roombridge,ether1,ether2,ether3,ether4 \ vlan-ids=100,3 /interface vlan add interface=Roombridge name=Data-VLAN vlan-id=100 add interface=Roombridge name=ISP-vlan vlan-id=3
My assumption is that VoIP is carried over tagged VLAN from ISP's switch ...
I'm pretty sure that phone number used for incoming calls is tied to phone's MAC address (or some other unique identification) and thus it doesn't matter how it's connected to the VoIP network of your ISP, which is determined by VLAN ID. It is, however, important that it is connected to the correct VLAN.
It would be possible to get VoIP working in the other room without knowing the correct VLAN ID, but that would also mean that data devices in the other room would not be part of your LAN. If I understand yiur intentions right, then it is vital to find out the VLAN ID used for VoIP and to correctly setup all routerboards between ISP's switch and the other room.
Use /tool sniffer, set it to sniff off ether3 interface and save full packet contents. Afterwards fetch file to a PC and analyze it using wireshark.But, how can I sniff the packets on eth4 from eth3?
Tomorrow, you are welcome to connect to my computer. A virtual coffee I will send to you jajajajaUse /tool sniffer, set it to sniff off ether3 interface and save full packet contents. Afterwards fetch file to a PC and analyze it using wireshark.But, how can I sniff the packets on eth4 from eth3?
That's exactly the reason why I wrote in one of my previous posts:Packet sniffer is a tool that can capture and analyze packets that are going to, leaving or going through the router (except the traffic that passes only through the switch chip).
(added emphasis).If you won't be able to find it, you could try to get it the hard way: plug RB between phone and VoIP port (use two ports on RB that are members of bridge, disable HW offload so that traffic will pass RB's CPU) and sniff traffic off the port where phone is plugged in. Even though registration might fail, there will be some tries using the right VLAN ID.
As I wrote earlier, give me some temporary communication channel so that we could start talking in a more flexible way then via this forum. The coming week should be as busy as any other one, so every day between 20 and 22 in the evening there is a chance we may do something, except Monday where I know for sure I won't be available.Hello my friend. I am going to be many days at my friend place... How is your week this next week?