Web Analytics Made Easy -
StatCounter
Saturday, August 2, 2025 3:44:06 AM

I have some older Vigor routers using Linux OS that I am replacing with DrayOS routers and I need to copy ov er functionality. There are two sites, linked by a dedicated connection via the providers own backbone connecton which acts as if it were a straight cable connection. This was previously achieved using a VLAN and dedicated ports. How can I configure two ned 2962 vigor routers to achieve the same thing?

4 days ago
#323 Quote
I have some older Vigor routers using Linux OS that I am replacing with DrayOS routers and I need to copy ov er functionality. There are two sites, linked by a dedicated connection via the providers own backbone connecton which acts as if it were a straight cable connection. This was previously achieved using a VLAN and dedicated ports. How can I configure two ned 2962 vigor routers to achieve the same thing?
0
4 days ago
#324 Quote
To replicate the old VLAN + dedicated port setup using DrayOS on two new Vigor 2962 routers, you'll want to mirror the previous configuration: a transparent Layer 2-style bridge over the provider's backbone using dedicated interfaces and a VLAN tag if needed.

Here's a methodical way to recreate that:

Objective
Connect Site A and Site B using a dedicated Layer 2 link over your provider's backbone-replicating the "cable-like" behavior using VLAN tagging and dedicated physical ports.

General Strategy
Choose a dedicated LAN port on both routers.
Create a VLAN (e.g. VLAN 99) and assign it to that port.
Set the port to Trunk or Tagged Mode, depending on whether the VLAN tag must be retained or stripped.
Create a static route or bridge that passes traffic between the VLAN interfaces or to the internal network.
Step-by-Step: DrayTek Vigor 2962 (DrayOS)
1. Pick Your Physical Ports
Decide which LAN port is physically connected to the provider backbone on each Vigor 2962 (e.g. LAN Port 4).

2. Create the VLAN
Go to:

LAN VLAN

Enable VLAN Mode

Add a new VLAN ID (e.g., 99)

Set:

LAN Port 4 Tagged for VLAN 99 (or Untagged, depending on the provider)
All other ports No or untagged with different VLANs
Tick Enable Inter-LAN Routing if you want routing between this VLAN and other LANs.

3. Assign an IP Interface (Optional)
If you want the routers to talk to each other (e.g. for routing):

LAN General Setup LANx (choose unused LAN subnet like LAN2)

Assign LAN2 to VLAN 99

Set:

Static IP for Site A (e.g. 10.99.99.1/30)
Static IP for Site B (e.g. 10.99.99.2/30)
This gives you IP routing across the VLAN, which you can then use for site-to-site traffic.

4. Set Up Static Routing (if needed)
If each site has its own internal LAN (e.g. 192.168.1.0/24 and 192.168.2.0/24):

Routing Static Route

On Site A:

Destination: 192.168.2.0
Mask: 255.255.255.0
Gateway: 10.99.99.2
Interface: VLAN or LAN2
On Site B:

Destination: 192.168.1.0
Gateway: 10.99.99.1
5. Firewall / Inter-LAN Permissions
Check:

Firewall Filter Setup

Make sure Inter-LAN routing is allowed for the VLANs and no rules block traffic between the subnets.

6. (Optional) Transparent Bridge Mode
If you truly need Layer 2 bridging (e.g. to extend a subnet without routing), use:

LAN Port Settings Set LAN Port 4 to be a member of LAN1 or use Bridge Mode in advanced settings.

Be careful-bridging two subnets can expose broadcast/multicast storms unless properly filtered.

Testing & Validation
Plug in directly to LAN4 on each router with static IPs (on VLAN 99 subnet) and ping between.
Add LAN routes and test full site-to-site connectivity.
Watch logs in:
Diagnostics Routing Table and ARP Table

Summary: Configuration Overview
Site  Port Used  VLAN ID  IP Address  Purpose
A  LAN4  99  10.99.99.1  Link to Site B
B  LAN4  99  10.99.99.2  Link to Site A
Would you prefer to keep everything Layer 2 (i.e. literally same subnet extended) or are you OK with routing between the sites?

Let me know if you'd like a backup config template or need to script this with CLI for both routers.
0