Hi  @JMo_C137 

As configured now, it should be working on wired. If you need wireless, you should set up the VLAN to pass it over. The core is to set up the VLAN.

Hi  @JMo_C137 

JMo_C137 wrote

it is currently wired in and NOT working.. getting wireless to work is a bonus if I get the wired connection working first

LAN2 should work as the IPTV port. If it doesn't work properly, please specify.

Wireless should be properly configuring the VLAN to pass over the traffic to an IPTV stuff.

  @JMo_C137 

Have you power cycled your router since you created the above config? (which looks correct to me btw).

  @JMo_C137 

Jack a laptop into LAN2 and you can see much more easily if it's getting an IP or not.  I wonder if you need to create a new subnet defintion for your IPTV devices...I'm trying to imagine how TPLink may have implemented this is the backend, as the functionality of their gateway ports is less than a managed switch.  So this begs the question of how an IP on one port would be treated differently than a similar IP on another port (specifically, get tagged with the IPTV VLAN ID).  This would be easier to figure out inside the switch, if the devices connected to the IPTV ports were given different IPs from a separate subnet.   If I get a chance, I'll try to mock this up as there seems to be zero documentation on how to do this properly.

  @JMo_C137 

Looks like it's going to be painful.  For a start, it sees you need to spoof your HH3000's MAC address on your WAN interface for IPTV DHCP to work...and it gets uglier from there.

Have a look at this post, it's for pfsense, but you should be able to translate most of it to Omada-ish.

https://www-idscomm-ca/blog/bell-fibe-internet-iptv-with-pfsense