But I didn’t quite understand his instructions. I already know I have a working IPTV setup on port 5 with VLAN id 600. So I created a new VLAN 592 to be able to send the PPPoE internet down through port 5, but my current setup does not work.
I tried so far as tcpdumping each port sudo tcpdump -n -e -vv -ttt -i enp0s25 vlan | grep vlan and oddly on each port 2-5 I see vlan 1 (where does that come from!?!!). I see VLAN id 592 on ports 2-4 which shouldn’t be the case and worryingly no VLAN id 592 on 5! So where am I going wrong??
Some things I don’t understand about Mikrotik:
WebFig 6.32.3 is good, but a typical vlan setup seems to span LOTS of menus. Is there a better way to get a summary?! http://192.168.88.1/webfig/#Interfaces comes close but it lacks a lot of details about which ports are connected where!!
I connect to the Internet via a PPPoE client on VLAN id 500. Now what I don’t understand in the UI is where the internet gets mapped to. Am I correct in assuming it’s bridge-local?
Not sure what you’re trying to achieve, why are you creating a new VLAN then? To send PPPoE where??
Create a new VLAN interface on the WAN interface, ID=500 and put the PPPoE client on that VLAN interface, why do you want to dial pppoe from another router??
I am creating VLAN592 not to send PPPoE, but to share the internet that the PPPoE internet provides over “bridge-local” IIUC with the DHCP service 192.168.88.x.
Sorry there was a long delay replying since I going back and forth with Mikrotik support who just suggested a simple port 5 bridge with VLAN600. This approach doesn’t work with my IPTV box. I have no idea why. I suspect the IPTV doesn’t like untagged traffic.
So my current approach was to create VLAN592 on bridge-local and bridge to bridge-iptv. But it doesn’t work. I have no idea why.
You should provide an export of your configuration (edit out any sensitive info) of the router and a diagram of your network devices and connections, otherwise it’s hard to help…
If you use OS X, with winebottler (winebottler.kronenberg.org) to generate a “standard” self-contained app is a two click task.
Imagine how practical it is, that for me and all the colleagues I know, is one of the key factors putting Mikrotik away from the rest, big “irons” included.
There are two key facts also that you will miss if not using it: Neighbor discovery/Mac telnet and RoMON, features that are uber-practical to work in layer 2 with any device, even unconfigured ones.