Virtual WAN interface on LAN interface

Peplink appliance ( especially SDX) will be connected to the Switch via single port . (1G SFP or 10G SFP). All LAN and WAN interfaces should be defined as a virtual interface ( vlan interface/subinterface) on this port via dot1q tagging.
What is your comment? Do you already have a plan/roadmap?


VLAN Trunking on LAN ports is available now. I am not aware of WAN interface VLAN trunking being possible yet. Certainly I haven’t seen it. Its a good idea though for the 10Gbe interfaces in particular.

1 Like

Hello @aytan34,
We have a very similar setup running at several locations with other models of Peplink Balance routers.

To make this work, you need to do some careful pre-planning, we recommend moving everything on the LAN network interfaces over the VLANs (FW 6, 7 & 8 support this).
You will need to assign the SFP port to behave like a LAN (not WAN) if that will be your backhaul, this SFP will need to operate in Trunk Mode. Note: in your image, you have highlighted the Ethernet WAN Ports, not the SFP Ports.
Then you will need to assign one of your Ethernet LANs to your reserved VLAN for WAN traffic at the switch and patch this one to each of the WAN Ports (you can duplicate this to a second LAN & WAN if needed).

Setting up the VLANs is the most important part, once setup, the rest of the configuring of the router is made easier by working out the VLANs first.

I can not recommend highly enough to use InControl2 to build this setup with and manage the VLANs. Even if ultimately the solution is going to be within a closed network with no public internet access.
Happy to Help,
Marcus :slight_smile:

1 Like