SXK80 Vlan Tag

---

BruceGuo wrote:

Can you check if UM is helpful?

---

Fear it isn't enough, or I have trouble finding the right spot. There is some vague refernece of a predefined "Bridge/VLAN group" only, defaulting to VLAN 1 on (both) the internal and the Internet side.

---

BruceGuo wrote:

If no, please discribe your network topology so we cna help you

---

Let's reflect what is implemented on the "consumer" routers and how a "random" engineer would like to see this implemented on the VLAN-capable routers like the Orbi Pro AX models:

VLAN Bridge Group

Basic router: We can define an _additional_ WAN-side (IPTV) network, based on the VLAN number, and bridge this VLAN 1:1 to a switch port, an aggregated switch port, or a Wireless (effectively that radio specific single SSID). The selected ports and WiFi are removed from the LAN-side of the NAT router, the ISP provided tagged VLAN network is bridged to these ports as an untagged network. Technically, this network is (on the ISP infrastructure) already a NATed and isolated RFC1918 IP subnet. Read all DHCP, IGMP Multicast (IPTV) goes stright through. 

Translating this to the VLAN capable router like the Orbi Pro AX: Instead of select port(s) and SSID, we need the ability to bring this IPTV VLAN (ISP number) to a local VLAN, ideally with the ability to renumber the VLAN from the ISP side to the LAN side. Anything else can be configured on the Orbi Pro AX as it already exists.

VLAN Tag Group



Basic router: The router can handle two VLANs on the Internet/WAN side. One (optional) for the Internet, which come in to the router either on an untagged VLAN (as in this example, this "Internet" is greyed) and goes to the router normal NAT router process. And the second IPTV VLAN (as in the above example): We can define an _additional_ WAN-side (IPTV) network, based on the VLAN number, and bridge this VLAN 1:1 to a switch port, an aggregated switch port, or a Wireless (effectively that radio specific single SSID). The selected ports and WiFi are removed from the LAN-side of the NAT router, the ISP provided tagged VLAN network is bridged to these ports as an untagged network. Technically, this network is (on the ISP infrastructure) already a NATed and isolated RFC1918 IP subnet. Read all DHCP, IGMP Multicast (IPTV) goes straight through.

Translating this to the VLAN capable router like the Orbi Pros: Instead of select port(s) and SSID, we need the ability to bring this IPTV VLAN (ISP number) to a local VLAN, ideally with the ability to renumber the VLAN from the ISP side to the LAN side. Anything else can be configured on the Orbi Pro AX as it already exists. This allows to connect the IPTV Settop device direct to the ISP provided network, and IPTV works like a charm, and so does the Internet access say for Netflix et all over a Carrier Grade NAT device. Disadvantage: Because this is an isolated network, you can't use a mobile phone "remote" or "controller" for the Settop device, you can't access say a DLNA Media Server on the LAN.

The "prefect" Solution (as implemented on the ISP provided routers)

Instead of just bridging, the ISP specific traffic needs to be NATed and merged into a single subnet, and the IPTV Settop device is operated in the primary network. This is not a fancy idea, much more it's required (and implemented by good ISPs) so the user can use e.g. direct discover and access the IPTV Settop device from a mobile device acting as a controller (Device remote, DLNA controller, ...) without connecting to another network/SSID, and the Settop box can have access to LAN resources like a DLNA Media Server on a NAS.

Said that: If Netgear is keen to be better than the ISP provided routers, a lot more must be done 8-)

Regards,
-Kurt

PS. If I have missed such an existing feature on the Orbi Pro AX, it's because I don't own such a device (Orbi Pro AX PLM is apparently not interested to support us helping people with hardware.