VOIP and IPTV VLANs on separate physical ports

[thoresson]

Still not getting this to work. This is the settings I thing you suggest.

For IPTV (I’ve tried to add the STB’s MAC address to the field for MAC address override)

For LAN (only changes done in the Physical settings

When I create the virtual interface, what protocol should it use? DHCP is the default setting. But since I just want to bridge eth1.243 with eth2, I would guess that the Omnia should bother with DHCP requests to my ISP at all, just leave that to the STB? Should I choose another? I’ve tried creating a unmanaged bridge as well, not working either.

[thoresson]

@Ondrej_Caletka

See the image (and the erratum) in this post. Simply port 0 - 4 are connected to the physical sockets, port 5 (nicknamed as CPU in LuCI) is connected to eth0 and port 6 is connected to eth2.

So none of the ports in the Switch config is WAN?

And I don’t get Port 6/eth2. Isn’t eth2 equivalent of physical port labeled number 4?

[Ondrej_Caletka]

@thoresson

When I create the virtual interface, what protocol should it use? DHCP is the default setting. But since I just want to bridge eth1.243 with eth2, I would guess that the Omnia should bother with DHCP requests to my ISP at all, just leave that to the STB?

You should not run any protocol on top of this interface. Choose Unmanaged. You should not change the MAC address of the bridge as this could lead to some problems with duplicate MAC address. Since you don’t run any protocol on top of the bridge, it’s MAC address is irrelevant.

@thoresson

So none of the ports in the Switch config is WAN?

Exactly. WAN is directly connected to the SoC as eth1 interface.

@thoresson

And I don’t get Port 6/eth2. Isn’t eth2 equivalent of physical port labeled number 4?

Only in default configuration. By default, there are two VLANs in the switch, one interconnecting ports 0-3 and port 5, ie. eth0, the other interconnects port 6, ie. eth2 with port 4 exclusively. But you are free to alter the configuration of the switch.

[thoresson]

@Ondrej_Caletka

You should not run any protocol on top of this interface. Choose Unmanaged. You should not change the MAC address of the bridge as this could lead to some problems with duplicate MAC address. Since you don’t run any protocol on top of the bridge, it’s MAC address is irrelevant.

Makes sense! Thanks.

@Ondrej_Caletka

Only in default configuration. By default, there are two VLANs in the switch, one interconnecting ports 0-3 and port 5, ie. eth0, the other interconnects port 6, ie. eth2 with port 4 exclusively. But you are free to alter the configuration of the switch.

Ah! Now I think I start to understand this! There are physical ports where cables are attached and the three interfaces eth0-eth2. But there are no hardwiring between the ports and the interfaces? How these are connected are possible to configure using the Switch. Have I got that right?

Port 5 is labelled CPU in the Switch config?

And the SPF port is, like WAN, absent from the Switch config?

[Ondrej_Caletka]

@thoresson

Ah! Now I think I start to understand this! There are physical ports where cables are attached and the three interfaces eth0-eth2. But there are no hardwiring between the ports and the interfaces? How these are connected are possible to configure using the Switch. Have I got that right?

Yes, except eth1, which is hardwired to the WAN socket and SFP cage (WAN socket is unusable when SFP module is plugged in). LAN ports 0 – 4, interface eth0 and eth2 all all connected to a manageable switch, which can interconnect arbitrary combinations.

@thoresson

Port 5 is labelled CPU in the Switch config?

Yes.

@thoresson

And the SPF port is, like WAN, absent from the Switch config?

Yes, it’s directly connected to eth1 and can’t be used together with wired WAN socket.

[thoresson]

Ok. Now got traffic both RX and TX on br-IPTV. But the STB still can’t get an IP-address. Are there any tools on the Omnia that I can use to inspect those few packages received and transmitted?

These are my current settings.

Interface IPTV

(Why is there VLAN’s eth0.237 and eth0.243? I’ve not configured those in my Switch config. See further down.)

Interface LAN

Switch config

Port 4 in Switch config is physical port labelled LAN4, right?

My STB is not in the ARP table anymore, which is expected now, since LAN4 is a bridge in unmanaged mode?

[thoresson]

@Ondrej_Caletka

OK, in that case you will have to make the traffic between eth2 and internal switch tagged and deploy both VLANs on the switch. So in switch config, add a new vlan similar to the 243. Select different physical port to which your IP phone is connected to. This port should be untagged and present only in this one VLAN. Then, swhich port6 on both vlans 243 and 237 to tagged mode. The interfaces in the bridge will then be eth2.237 and eth2.243.

If I get what you are writing here, eth2.237 and eth2.243 should be available choices in the interfaces Physical settings once I’ve created those VLANs. But, as you can see in this screenshot, what I get is eth0.237 and eth0.243.

And, to repeat from the post I just made, this is my current switch configuration:

[Ondrej_Caletka]

@thoresson

If I get what you are writing here, eth2.237 and eth2.243 should be available choices in the interfaces Physical settings once I’ve created those VLANs. But, as you can see in this screenshot, what I get is eth0.237 and eth0.243.

Create them yourself using Custom Interface option. There is no direct connection between switch config and interface setup so new VLAN interfaces do not appear automatically.

[thoresson]

Still no luck. The problem is that I don’t know wether I’m doing something wrong in the configuration of the router, or if there are some additional settings the my ISP require that I’m not aware of. For now, if we assume that all that needs to be done is what we already have discussed, this is, step by step, what I’ve done trying to follow @Ondrej_Caletka’s instructions. (For now just focusing on IPTV; VoIP will have to wait.)

Create a new interface for WAN

I click *Add new interface…"

…with the name IPTV, Unmanaged as protocol and bridged between eth2 and a new virtual interface with the name eth1.243.

Remove eth2 from lan

And then I remove eth2 from lan.

This should bridge my ISP’s VLAN243 to LAN4 on my Turris Omnia. And, if I understand the instructions above, all needed to get my STB connected to my ISP’s network.

But my STB doesn’t get any ip-address.

Is that because I’ve done something wrong above?

Or is it because I haven’t got all the details for my ISP’s IPTV service correct?

[thoresson]

@thoresson

Or is it because I haven’t got all the details for my ISP’s IPTV service correct?

Because I had the wrong information from my ISP. Right after I’d posted this, I tried google again. And this time found forum threads where VLAN id 845 was used. Tried that.

And am now watching tv!

On to VoIP-configuration.

[Julius]

Can you show your switch configuration? I can’t seem to get my IPTV working.

[thoresson]

Sure! As soon as I’ve the possibility, I’ll post a screenshot of it here.

[thoresson]

This is my switch configuration:

And you also need to create two virtual interfaces for each VLAN – one external, one internal – and bridge them together. One example:

[thoresson]

I’m using a set top box for IPTV that my ISP sent me. And a box for VOIP as well, also from my ISP. Each connects to a dedicated port on my Omnia, using the Switch and Interface configuration I just posted.