Hello All,
How can I have MetaRouter assigned an IP in a VLAN attached to Ether2 ?
Until now I have used a bridge between this vlan and the virtual interface with DHCP server targeting the bridge.
Is there a way to get rid off the bridge and have MetaRouter request an IP on ether2 with eth0.100 declared in OpenWRT or directly on vlan interface with regular eth0 ?
Tried both and I was unsuccessful.
Thank you
Expected my question to be pretty trivial 
Maybe asked another way?
If I want my MetaRouter to have an IP in a range that is declared on the Mikrotik, is it only possible using a bridge between the virtual interface and another interface on the Mikrotik corresponding to IP range ?
Thank you
One last try 
If I want to assign my MetaRouter Virtual Ethernet an IP in one of the ranges declared on the Mikrotik, how would I do it ?
I tried to assign the VIF itself an IP manually (IP > Addresses) and manually configured one in the same range on OpenWRT with no luck.
For instance:
vlan100 : 10.1.0.1/24
vif: 10.1.0.2/24
OpenWRT: 10.1.0.3/24
Thank you
in this case throw all the virtual stuff out of the equation and think in terms of independent devices and physical interfaces.
so, if you have interface with attached Ethernet network to it, and you have another interface on another device that you want to be part of the same Ethernet network but is connected to another interface of the router - you have to bridge 2 router interfaces to extend the Ethernet network to that extra interface on another device.
Hello and thank you for your answer,
That’s what I have done so far but now I also need IGMP Proxy / PIM on this bridge because vlan100 contains printers, etc.
But in an exchange we had on support@ you told me bridges can’t be used in PIM. I’m trying to find a solution…
Thanks
if you have to extend ethernet, there is no other option but bridge. If you can have different network address, then you can use igmp-proxy and routing to access these devices
OK so I will create a range dedicated to a single MetaRouter instance then
What if I split range:
vlan100 - 10.1.0.0/24 (IPs 10.1.0.1 - 10.1.0.254 with broadcast 10.1.0.255)
into:
vlan100 - 10.1.0.0/25 (IPs 10.1.0.1 - 10.1.0.126 with broadcast 10.1.0.127)
vif - 10.1.0.128/25 (IPs 10.1.0.129-10.1.0.254 with broadcast 10.1.0.255)
Can RouterOS handle this ?
No more need for bridge then.
Thank you
yes, RouterOS can do that. /24 is just the most popular option used.
I’ve done so and go rid off the bridge. PIM/IGMP still don’t work though.
But at least no more bridge. Thanks.
ok then, where are the multicast sources, where are multicast destinations? What groups are used and is source part of network that your router interface receiving it?
See: http://forum.mikrotik.com/t/bonjour-multicast-how-to-do-it-with-vlans/75927/1
where are the multicast sources
Sources are in vlan100 - 10.1.0.0/25 (printers, NAS, etc. - all emitting Bonjour frames)
where are multicast destinations
Receivers are in vlan200 - 10.2.0.0/24 (laptops, phone, etc.)
What groups are used
To be able to answer, can you tell me what you are expecting (which tab or /routing print would you need ?)
Cause I configured RP with group 224.0.0.0/4 which I thought would cover all groups.
is source part of network that your router interface receiving it?
Yes both the vlans and RP are on the same router (the Mikrotik).
Thanks for your help, really appreciated!
if you sniff packets on incoming (underlying) interface are they correctly tagged, are there join in /routing pim joins
is there relevant entries in /routing igmp-proxy mfc (this is only place to see MFC entries, for everything else do not mix pim and igmp-proxy configurations)
if you sniff packets on incoming (underlying) interface are they correctly tagged, are there join in /routing pim joins
I can see igmp packages travelling on vlan100 to 224.x.x.x IPs - Those IPs I can see them in PIM/IGMP Groups.
In PIM/Joins I have:
is there relevant entries in /routing igmp-proxy mfc (this is only place to see MFC entries, for everything else do not mix pim and igmp-proxy configurations)
DA, group 239.255.255.250, source 10.1.0.30, upstream interface unknown, downstream interface , packets 1166
10.1.0.30 is the NAS, I never saw frames coming from the printer, that’s a second strange thing.