This article applies only to EoC software version 2.0.1.r87- 2.9.1.r179

For software version 3.0.22 and above, read more here.


If you wish to extend the EoC installation across an external Cat. (ethernet) network, you must make sure, that the following is in place:

  1. The special internal management frames must have access to the Endpoint Ethernet (EPE). This is done by forwarding the frames in a separate VLAN on all switches.
  2. Make sure, that all available VLANs in the controller are forwarded out of the controller ethernet port, connected to the external network. This is done with the "VLAN Pass-through" rule on the controller and trunks on all the switches.



Management frames - configuring the controller.

The controller is communicating with the endpoints (EPE and EPC) with special management/maintenance frames. This data flow is required for the system to work across an external network.


These management/maintenance frames are untagged traffic (orange in the illustration) and need to be put in a native VLAN on the switches.

The tagged traffic will be forwarded to the endpoints (EPE) connected to the configured ports on the switch, belonging to the same native VLAN!


Start by accessing the controller and enable the "VLAN Pass-through" rule on the ethernet port connected to the external network. In this example, the controller is connected to the switch on port ethernet port 4.


Go to "Network" --> "Ethernet settings" and edit the ethernet port:



Enable the "VLAN pass-through" rule for the ethernet port. Don't forget to save the settings:



The management frames and all available VLANs will now be forwarded out of ethernet port 4 and towards the connected switch.


You can test this, by connecting an endpoint (EPE) directly to the controller on the port you just configured as "VLAN pass-through". Remember to power the endpoint locally, with a power supply.


The external network - configuring the switches.

The controller is now configured and the next step is to configure native VLAN and the desired VLANs on the switches. This part tells you in general terms, what you need to do since the configuration of the switch varies from vendor to vendor.


In this example, we will only operate with the default VLANs already configured on the controller:

  • VLAN 10 (Setup)
  • VLAN 50 (Private)
  • VLAN 80 (IPTV)
  • VLAN 100 (Guest)

If you have added your own VLANs to the system, please include those in the configuration of the switch too.


In order to communicate with the EPE, we need to forward all available VLAN’s and management data, which is untagged.


We will tag the untagged management data to VLAN4000 (or any other available unused VLAN by your choice). All ports on the switch, where you will connect the controller and the Endpoints (EPE) must be configured as follows:


  • VLAN 10, 50, 80, 100 must be created and tagged on the ports.
  • VLAN 4000 must be created and untagged on the ports (native VLAN).
  • The ports must have PVID 4000.
  • Make sure, that Ingress and Egress settings do not exclude untagged traffic.
  • By choice, enable or disable Ingress checking of VLANs (exclude unknown VLANs).


Maybe you want to use the switch for uplink to the router. In that case, A trunk from the switch to the router, with VLAN 50 & 100, could be a good idea. You would be able to utilize the router as a DHCP server on both VLANs (in two different scopes).

Please note: TRIAX cannot help you configure the switch. We can give you the general guidelines, that you need to follow.