XMG1915 - VLAN Configuration

Sathish

Port 1: Connected to pfSense router 

Port 2: Connected to Access Point 

I have created static VLAN 20 with the below options

Switching -> VLAN Setup -> Static VLAN -> 20
Port 1 : Fixed -> Tx Tagging (Selected)
Port 2: Fixed -> Tx Tagging (Selected)

Switching -> VLAN Setup -> VLAN Port Setup
In VLAN Port Setup, nothing changed All ports are pointing to PVID 1. 

With this setup I am able to get VLAN related IPs on my wireless. Now, I wanted to assign port 7 on the switch to this VLAN network and made the below changes. 

Switching -> VLAN Setup -> Static VLAN -> 20

Port 1 : Fixed -> Tx Tagging (Selected)
Port 2: Fixed -> Tx Tagging (Selected)
Port 7: Normal -> NO (Tx Tagging) (Unselected)

Switching -> VLAN Setup -> VLAN Port Setup
Port 7: 
Ingress Check: True
PVID: 20
Frame Types: Untag Only

I am not getting an IP address when I connect my PC to port 7

Zyxel_Barry

Hi @Sathish,

It sounds like you're trying to set up VLAN 20 for an untagged device on Port 7 of your XMG1915, but it's not receiving an IP address. The configuration for an access port (where an end device like a PC connects) is slightly different from a trunk port (which carries multiple VLANs).

Here's a breakdown of the common configuration for an access port and some steps to troubleshoot:

• VLAN Configuration for Port 7 (Access Port):

  • Static VLAN Setup:

    • Navigate to Switching > VLAN Setup > Static VLAN.
    • For VLAN 20:
      • Port 1 (connected to pfSense router) should be Fixed with Tx Tagging selected (Tagged). This allows the pfSense to send and receive tagged VLAN 20 traffic.
      • Port 2 (connected to Access Point) should be Fixed with Tx Tagging selected (Tagged). Your Access Point will handle tagging/untagging for wireless clients on VLAN 20.
      • Port 7 (for your PC) should be Fixed and Tx Tagging should NOT be selected (Untagged). This means the switch will remove the VLAN 20 tag before sending traffic to your PC and add the VLAN 20 tag to traffic coming from your PC.

  • VLAN Port Setup:

    • Navigate to Switching > VLAN Setup > VLAN Port Setup.
    • For Port 7:
      • Ingress Check: Set to True. This prevents untagged packets from entering the VLAN if they don't belong to it.
      • PVID: Set to 20. The PVID (Port VLAN ID) tells the switch which VLAN to assign untagged incoming traffic to. For an access port for VLAN 20, the PVID must be 20.
      • Frame Types: Set to Untag Only. This ensures that only untagged frames are expected on this port, and the switch will handle the tagging internally for VLAN 20.

• Troubleshooting Steps:

  1. Verify pfSense Configuration: Ensure that your pfSense router is correctly configured to provide DHCP services for VLAN 20. Since your wireless clients are getting IPs, this is likely already correct, but it's good to confirm.
  2. Check IP Address on PC: After making the changes, try renewing the IP address on your PC connected to Port 7. You can do this by disabling and re-enabling the network adapter or by using ipconfig /release and ipconfig /renew on Windows, or sudo dhclient -r and sudo dhclient on Linux.
  3. Firewall Rules: Double-check if there are any firewall rules on your pfSense that might be blocking DHCP requests or traffic for devices on VLAN 20 when coming from a wired port.
  4. Cable Test: Try a different Ethernet cable for Port 7 to rule out a faulty cable.

To assist you further, please provide the following information:

• Device Model: XMG1915 (confirmed).
• Firmware Version: Please provide the current firmware version of your switch.
• Network Topology Map: A simple diagram showing how your pfSense, XMG1915, Access Point, and PC on Port 7 are connected.
• Screenshot of VLAN Setup > Static VLAN: A screenshot of your complete Static VLAN configuration.
• Screenshot of VLAN Setup > VLAN Port Setup: A screenshot of your complete VLAN Port Setup.

Zyxel_Tina

Hi @Sathish,

To better assist you, please first follow the step mentioned by Zyxel_Barry: change your Port 7 from Normal to Fixed. Additionally, please try leaving Ingress Check and Acceptable Frame Type at their defaults (unselected and All) to help rule out potential causes of this issue.