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

Forum Discussion

Malvineous's avatar
Malvineous
Aspirant
Jul 27, 2023

How to make management VLAN on WAX610 persist across power cycles

Hi all,

 

I've gotten a new WAX610 and I want to set it up with two WiFi SSIDs on different VLANs, and with a management VLAN.  Unfortunately I can't work out how to make these settings stick - every time I reboot the AP, it loses the VLAN settings and goes back to the default of no VLAN/untagged.

 

If I go into the web interface, under Configuration, IP, then LAN, there is an 802.1Q VLAN section.  In there I change the Management VLAN from 1 to something else, and untick "Untagged VLAN".  I click Apply and get a popup warning me the device will get a new IP, and I click OK.

 

A moment later I see on my DHCP server that the AP is requesting an IP over the correct management VLAN, and the new (different) IP is assigned.  Great.

 

However now I can't access the web interface any more, it just comes up blank.  Based on my experience with this problem it is because the Javascript app that runs the web interface only responds to the device's IP address, and now that the IP has changed, it won't respond as it's still expecting the original (non-VLAN) IP.

 

Ok, so I power cycle the AP to bring it up on the new IP address thinking that should get the web interface working again, but instead it drops off the network completely - no DHCP requests or anything.  I take the switch port it's connected to off trunk mode and back to an access port and suddenly DHCP works, it gets assigned the old IP, and when I log in to the web interface the VLAN settings have reverted back to what they were originally (i.e. VLANs are all off, management VLAN is back at 1).

 

How can I get the VLAN settings to persist across a power cycle?

2 Replies

  • Hello Malvineous 

     

    And welcome to the NETGEAR Community! 🙂 
     Set the 802.1Q VLAN and management
    VLAN
    The 802.1Q VLAN protocol on the access point logically separates traffic on the same
    physical (wired) network. This protocol can work with tagged and untagged VLANs, as
    follows:
    • Untagged VLAN. The access point sends untagged frames from its Ethernet interface.
    Incoming untagged frames are assigned to the untagged VLAN. By default, the
    untagged VLAN is VLAN 1. By default, the access point functions with an untagged
    VLAN.
    • Tagged VLAN. The access point tags all frames that it sends from its Ethernet
    interface. Only the incoming frames that are tagged with known VLAN IDs are
    accepted.
    The management VLAN is used for managing traffic such as Telnet, SNMP, HTTP, and
    HTTPS traffic sent to and from the access point. Frames that belong to the management
    VLAN and that are sent over the trunk do not receive an 802.1Q header. If a port is a
    member of a single VLAN, its traffic can be untagged.
    To set the 802.1Q VLAN and management VLAN:
    1. Open a web browser from a computer that is connected to the same network as the
    access point or directly to the access point through an Ethernet cable or WiFi
    connection.
    2. Enter the IP address that is assigned to the access point.
    A login window opens.
    3. Enter the access point user name and password.
    The user name is admin. The password is the one that you specified. The user name
    and password are case-sensitive.
    If you previously added the access point to a NETGEAR Insight network location and
    managed the access point through the Insight app or Insight Cloud portal, enter the
    Insight network password for that location.
    The Dashboard page displays

     

    Link for reference : https://www.manualslib.com/manual/1865056/Netgear-Wax610.html?page=131
      
    Have a lovely day,

    Nivedita Pa
    Netgear Team 

    • Malvineous's avatar
      Malvineous
      Aspirant

      Yes I already read that in the manual, and I am familiar with how VLANs work, but I was asking why the VLAN settings get lost after every reboot.  I opened a support case and after one week of back and forth and repeating myself it finally got through to a level 3 technician who followed my instructions and confirmed that there is a bug in the firmware that causes this VLAN problem, and they are now working on a fix.  Unfortunately there is no ETA on the fix so I had to return the WAX610 for a refund as without this feature it is unusable for me, and I do not wish to buy a product I cannot use for months after its purchase.

       

      I am quite surprised that a company like Netgear would not test their products properly, especially ones sold as business products, but I have learned my lesson and I will stick to other brands in future.

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