Hello, I'm having issues with my 2 WAX630E units.VLANs are not working properly. Configuration:- Netgear MS510TXM Managed switch- 2 WAX630E AP, AP1 and AP2- 2 VLANs: A & B- 2 SSID: SSID A for VLAN A and SSID B for VLAN B on both AP, same configuration- AP1 & AP2 switch port configuration identifcal: Trunk Port, both VLAN A & B are tagged- 2 clients: a Laptop and a Printer- There is a Router / firewall allowing everything from VLAN A to VLAN B (for testing purposes) What I observe:Laptop on AP1 SSID A + Printer on AP1 SSID B: HTTP access to printer configuration KOLaptop on AP2 SSID A + Printer on AP2 SSID B: HTTP access to printer configuration KOLaptop on AP1 SSID A + Printer on AP2 SSID B: HTTP access to printer configuration OKLaptop on AP2 SSID A + Printer on AP1 SSID B: HTTP access to printer configuration OKLaptop wired VLAN A + Printer on AP1 SSID B: HTTP access to printer configuration OKLaptop wired VLAN A + Printer on AP2 SSID B: HTTP access to printer configuration OK Ping from laptop to printer works in all 6 scenarios.This not expected behaviour is observed as long as the clients are connected to the same AP. Any know issue ?Any suggestion to fix this ? Regards,Toni.

Thanks tchubaba for you're feed-back. I will wait for the support feed-back about a potential fix date as I still hope this VLAN bug is fixed. Indeed all other features I need work well and I believe the WAX630E is still a strong access point for anyone not needing VLAN capability. But if no clear anwser, I will sadly have to return the access points and buy other brand AP as VLAN capability is mandatory for my use cases. Actually WAX630E shouldn't be advertised as supporting VLANs until the bug is fixed. I will keep the thread updated as soon as I have a feed-back from support.Could be useful for other WAX630E users.

After reading this thread and others like it, I'm furious, happy, vindicated, relieved, and disturbed simultaneously. All of these appear to mention what, for all accounts, seems to be the same issue I've spent almost a year dealing with. I have had persistent problems with my network since rebuilding it last spring. My setup includes 3 WAX630E units, a WAX620, and a WAX610Y, all managed via Netgear Insight. This is complemented by switches: 1x MS510TXM, 1x GS110TPv3, and 2x GS108Tv3. These switches are not set to Insight Managed Mode, so I can utilize IGMP snooping, MLD snooping, and DHCP relay functionalities, which are unavailable through Insight management. Despite my CompTIA Network+ certification and a fundamental solid understanding of networking, I'm stymied by an inter-VLAN communication issue particularly affecting wireless devices. Devices such as wireless speakers, printers, and anything that “casts” intermittently respond to pings but fail to work correctly for their intended purposes. Even after setting up IGMP/MLD snooping correctly, which has resulted in a much smoother, faster, more responsive network experience with no issues when adding smart home devices—direct wireless device-to-wireless device communication remains a challenge. Another issue I've encountered is a peculiar scenario where my Firewalla Gold Plus router assigns guest VLAN IPs to each AP, but only while in Insight mode; this is despite being connected to ports properly tagged for VLAN trunking with the PVID set as VID1. I can ping the APs using these guest VLAN IPs; however, I cannot access their web interfaces via this IP, which aligns with expected VLAN isolation protocols. However, while the management VLAN IPs are still pingable, their web interfaces are inaccessible. This behavior is not only unusual but also very concerning. I have not been able to determine why this happens, but it goes away on its own. Furthermore, it is ridiculous that, while in Insight-managed mode, one cannot change the PVID of eth1 on the WAX630E. This limitation forces me to choose between being able to properly isolate traffic on my network as the AP is advertised as capable of doing or being able to manage all my insight-managed access points singerly via Insight Cloud Management, a service provided by Netgear so that the access points may communicate with each other to optimize radio power, channel, and frequencies. The inability to fully utilize all the product's capabilities simultaneously without being told about this limitation is 100% unacceptable. We have been forced into an unwelcome trade-off. It certainly makes one wonder if Netgear was aware of this limitation when the device was released yet chose not to disclose it. While I understand the community will not have a solution to these device issues, I'm keen to know if anyone has heard of any efforts by Netgear to address them or problems similar to what I’ve explained. Any information on upcoming firmware updates or any potential recall would be beneficial. Any insights into Netgear’s actions to remedy (or not remedy) this situation would be very welcome. I appreciate any help you can provide.

DavidGo please chime in here, appears different users are experiencing issues on the WAX630E

Hi ToniRod, I will ask our support team to reach out to you and log a case. Best Regards, Julien R.

Perhaps you shouldn't then. Perhaps you should find some more fulfilling activities so that you can live a happier life. Life's too short to live it so bitter. I wish you the best.

ToniRod

Guide

Jul 23, 2023

WAX630E VLAN bug

Hello,

I'm having issues with my 2 WAX630E units.

VLANs are not working properly.

Configuration:

- Netgear MS510TXM Managed switch

- 2 WAX630E AP, AP1 and AP2

- 2 VLANs: A & B

- 2 SSID: SSID A for VLAN A and SSID B for VLAN B on both AP, same configuration

- AP1 & AP2 switch port configuration identifcal: Trunk Port, both VLAN A & B are tagged

- 2 clients: a Laptop and a Printer

- There is a Router / firewall allowing everything from VLAN A to VLAN B (for testing purposes)

What I observe:

Laptop on AP1 SSID A + Printer on AP1 SSID B: HTTP access to printer configuration KO
Laptop on AP2 SSID A + Printer on AP2 SSID B: HTTP access to printer configuration KO
Laptop on AP1 SSID A + Printer on AP2 SSID B: HTTP access to printer configuration OK
Laptop on AP2 SSID A + Printer on AP1 SSID B: HTTP access to printer configuration OK
Laptop wired VLAN A + Printer on AP1 SSID B: HTTP access to printer configuration OK
Laptop wired VLAN A + Printer on AP2 SSID B: HTTP access to printer configuration OK

Ping from laptop to printer works in all 6 scenarios.

This not expected behaviour is observed as long as the clients are connected to the same AP.

Any know issue ?

Any suggestion to fix this ?

Regards,

Toni.

34 Replies

Replies have been turned off for this discussion

schumaku
Guru - Experienced User
Jul 23, 2023
This reads more like a firewall or filtering issue. Or are we facing some mDNS (Multicast DNS gateway) configuration on these WAX630E?
- ToniRod
  Guide
  Jul 24, 2023
  Hi, actually mDNS is disabled on both AP.
  
  Regarding firewall, all traffic is allowed from VLAN A to VLAN B.
  
  I'm facing the issue only when the printer and the laptop are connected to the same Access Point but with different VLAN SSID. Connecting them to two different Access Points, and still with different VLAN SSID works well, which suggests it's not a firewall issue.
  - schumaku
    Guru - Experienced User
    Jul 24, 2023
    ToniRod wrote:
    I'm facing the issue only when the printer and the laptop are connected to the same Access Point but with different VLAN SSID. Connecting them to two different Access Points, and still with different VLAN SSID works well, which suggests it's not a firewall issue.
    
    Two SSIDs. still two networks, two different VLANs, two different IP subnetworks. And the IPv4 traffic must flow over the firewall. What does Wireshark collect when attempting to access the printer Web UI from the laptop? Sure, there could be additional L3 or L2 issues prohibiting establishing a connection, e.g. on the WAX630E. Start capturing traffic, proof a ping will go through, then we can see what fails on establishing a TCP session.
ivant088
Aspirant
Jul 28, 2023
I have the same problem with wax630e. File sharing and chromecast do not work across vlan. Ping no issue. Previous wireless access point from another brand works fine in this setup.
- schumaku
  Guru - Experienced User
  Jul 28, 2023
  DavidGo please chime in here, appears different users are experiencing issues on the WAX630E
rivadavia
Tutor
Feb 28, 2024
I'm also facing this exact same issue. The TCP session connects to the wireless device on a different VLAN but it will not pass traffic. Ping also works. This only happens if the two wireless devices are on the same AP but different VLANs. This is a significant bug. Can we get an update or do I need to return this product? I have verified it is not a router/firewall problem.

Thanks
- Halcyonon
  Tutor
  Feb 28, 2024
  rivadavia if you have a closing return window, I suggest you take it, until Netgear starts being more responsive on this issue.
- tchubaba
  Guide
  Feb 28, 2024
  rivadavia I second Halcyonon 's thoughts here. This is an issue that's been known for several months but there's still no fix available. There's no telling if/when there will be one. So if this is a feature that's a must for you (as it was for me) better return the AP now before you are stuck with it.
rivadavia
Tutor
Mar 01, 2024
I opened a case and spoke with support who stated that the problem is being actively worked on but that they can't make any claims about when the fix will be released. I guess I will be keeping the device and eagerly awaiting the fix.
- gregd00
  Aspirant
  Mar 26, 2024
  rivadavia Any updates from support on this issue?
  I have a WAX615 and am having the same issue. A bummer since I can't return this AP have had it from a while now
  - rivadavia
    Tutor
    Mar 26, 2024
    So after giving support packet dumps, network diagrams, multiple explanations, the level 3 support rep said "Oh yeah we know about that problem, we don't have any plan or estimate of resolution, you should return the access point" So I returned it. Needless to say I won't be considering Netgear for my future networking needs.

Forum Discussion

WAX630E VLAN bug

34 Replies

Related Content

WAX630e redundancy

Re: WAX630E VLAN bug

wax630 web interface white screen

WAX630E Firmware Update Fail

WAX630 Guest WiFI setup

NETGEAR Academy

ProSupport for Business