NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

cwoodfield's avatar
cwoodfield
Aspirant
Nov 30, 2025

GS110EMX not tagging frames

I've had this switch for quite a while but haven't had a need to configure VLANs until now. I've started by moving all the ports to Vlan 2, and configuring ports 7 and 8 - part of an LACP bundle - as tagged interfaces .

 

However, pcaps on my upstream router show that frames coming from the switch over the trunk do not have VLAN tags; it's receiving tagged frames from the router and processing those correctly, but there are no tags from frames coming from the switch seen by the router. 

Any ideas what to check that might be misconfigured?

Configuration screenshots below:

 

Pcap from upstream router shows untagged frames from the switch, while response is properly tagged:

 

 

7 Replies

  • schumaku's avatar
    schumaku
    Guru - Experienced User

    Please also add a screenshot of the VLAN Membership config for the old VLAN, as I'm assuming some previous config remaining.

  • Here's the port membership for VLAN 1. The switch won't allow me to delete it, so I only assigned the tagged LAG to it.

     

    • schumaku's avatar
      schumaku
      Guru - Experienced User

      Clicking on each if the now [T]agged ports, does not offer the unassigned [ ] - like on all other ports for VLAN 1? 

      • cwoodfield's avatar
        cwoodfield
        Aspirant

        So it let me remove those ports from VLAN 1 this time - I think the earlier time was when I didn't have Advanced configuration enabled (I remember seeing an error saying that VLAN 1 was required for IGMP snooping, but I'm not seeing that now). So, rescinding my statement above, apologies.

        I've removed those ports (see screenshots of both VLAN 1 and VLAN 2 below), but I'm still seeing traffic from the switch untagged.

         

  • As an FYI - I am working on the possibility (albeit unlikely) that my upstream router (a Mikrotik RB5009) is stripping the incoming vlan tags off of the packets before handing them to the pcap process. To test that, I attempted to set up a mirror port on the switch, but it appears that I can't use a member of a LAG group as a mirror source:

     

  • To follow up - I confirmed via a colleague running the same model of upstream router (a Mikrotik RB5009) that incoming tagged frames do appear in packet captures with their VLAN tags intact, which brings me back to the assertion that the switch is not tagging frames as it is configured to do.

    As mentioned above, the "gold-standard" confirmation, which would be to examine the traffic via a mirror port, cannot be done since the switch doesn't appear to allow a member of an LACP bundle to be used as a mirror port source. Is this a known caveat or is there a workaround?

  • This reply was moved from another post

    In my prior post here I described an issue I'm having with my GS110EMX, which is not tagging frames on a trunked interface despite an apparently valid configuration. This switch is running 

     

    Yesterday, reading the documentation of another vendor's switch, I came on a setting on that device where the switch did not tag frames if the vlan matched the port's PVID. Given that at the time (our teenager was in the middle of an intense online game), I decided to test this with a new VLAN.

     

    The setup (screenshots below) is as follows:

     

    Port 2 untagged on VLAN 10, PVID set to 10

    Ports 1-6, 9, 10 untagged on VLAN 2, PVID set to 2

    Ports 7/8 (LAG 1, LACP) tagged on VLANS 2 and 10, PVID set to 2.

     

    I plugged my laptop into Port 2, and ran several packet captures from both my client and the upstream router (a Mikrotik RB5009) during my testing. Some interesting (and maddening) results came from this:

     

    • Traffic from untagged VLAN 2 ports appeared up the upstream router untagged, as previously observed.
    • Broadcast DHCP requests from my laptop did not appear on the upstream router, at all. No traffic tagged with VLAN 10 was seen (caveat: I did not test the forwarding of non-broadcast traffic sent from my laptop into port 2 using a static IP configuration on the DHCP client).

    Attached below is a series of screenshots showing the configuration and the resulting PCAPs. Is there anything I'm missing, or is this a failure of the switch hardware itself? And yes, I did powercycle it to make sure that wouldn't change anything.

     

    GS110EMX configuration:

     

    LACP configuration for LAG 1 on Ports 7-8:

    LAG 1 Enabled and set to LACPPorts 7,8 assigned to LAG 1LACP System Priority set to default 32768LACP Priority and Timeout set to default 128/Long

    801.Q Configuration:

     

     

    Basic Port-Based VLAN Status disabled

     

    Basic 802.1Q VLAN Status disabled

    802.1Q Configuration:

    VLAN Configuration showing VLAN membership status for all VLANs: VLAN 1 with no port members; VLAN 2 with all ports as members, VLAN 10 with ports 2,7-8 as members.VLAN Membership for VLAN 2 - Ports 1,3-6,9-10 untagged, Ports 7-8 (LAG 1) taggedVLAN Membership for VLAN 10 - Port 2 untagged, Ports 7/8 (LAG 1) taggedPort PVID configuration: Port 2 PVID set to 10, all others set to 2Client sending broadcast DHCP Discover requests to untagged Port 2. These packets did not appear in a pcap on the upstream router running at the same time.

     

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More