Port Forwarding utilizing particular VLAN on CIsco RV134W

The problem you are encountering is probably going as a consequence of a misunderstanding of how VLAN tagging and port forwarding work together between your Cisco RV134W VDSL gateway and the D-LINK DGS-1210-28 swap. Let’s break down the elements and the anticipated habits:

VLAN Configuration:

1. Change Configuration:

   • The port related to the RV134W is about to Untagged VLAN 30.
   • When a port is about to Untagged for a selected VLAN, it signifies that any visitors coming into or leaving this port is taken into account a part of that VLAN with none VLAN tags.

2. Gateway Configuration:

   • The port on the RV134W is about to Tagged VLAN 1 (Default VLAN).
   • When a port is about to Tagged for a selected VLAN, it signifies that visitors coming into or leaving this port is tagged with that VLAN ID.

Port Forwarding and VLAN Interplay:

While you configure port forwarding on the RV134W, it forwards the visitors to the desired native IP tackle inside its VLAN context. Because the RV134W is tagging the visitors with VLAN 1, and your swap port is about to Untagged VLAN 30, there’s a mismatch.

Anticipated Habits:

1. Site visitors Tagging:

   • Site visitors leaving the RV134W will probably be tagged with VLAN 1.
   • Your swap port expects visitors with none VLAN tags and assigns it to VLAN 30.

2. Packet Dealing with:

   • The RV134W forwards the packet with a VLAN 1 tag.
   • The swap port receives this tagged packet, however since it’s set to Untagged VLAN 30, it may not deal with the tagged packet accurately.

Resolution:

To make sure the visitors is accurately forwarded and tagged, you might want to align the VLAN configurations between the gateway and the swap. Listed here are the steps:

1. Change Port Configuration:

   • Change the port configuration on the swap to Tagged VLAN 30.
   • This implies the port on the swap related to the RV134W ought to count on and deal with VLAN 30 tagged visitors.

2. Gateway Port Configuration:

   • Change the VLAN configuration on the RV134W port to Tagged VLAN 30.
   • This implies the RV134W will tag the outgoing visitors with VLAN 30, which matches the swap’s expectations.

3. Constant VLAN Tagging:

   • Make sure that each units use the identical VLAN tagging to keep away from mismatches.

Instance Configuration:

Change Port Configuration (D-LINK DGS-1210-28):

• Port X (related to RV134W): Tagged VLAN 30

Gateway Port Configuration (Cisco RV134W):

• Port Y (related to Change): Tagged VLAN 30

Verification:

• Confirm the VLAN configuration on each units.
• Check the connectivity and port forwarding rule.
• Make sure that the safety cameras are reachable and that visitors is accurately routed by VLAN 30.

By aligning the VLAN tagging on each the gateway and the swap, you make sure that visitors is accurately recognized and dealt with, resolving the forwarding concern.