No Internet access after WAC540 firmware update (9.1.0.13)

[podex]

I am using 3 WAC540 in an Inside configuration at my restaurant. It worked fine until I updated the firmware to the current version 9.1.0.13.

The setup is quite simple, just the 3 devices connected to a standard GW providing DHCP and internet access. No special features enabled in the 540s.

The sympotoms are as following:

• The WAC540 devices can connect to the Internet, Insight Management Cloud Portal is working fine and reports no problems.
• Also devices connected to the wired LAN ports can connect to the Internet.
• Mobile phones (iPhone and Android 10) can
  • pair with the SSID (shared on all devices),
  • get an IP adress with correct DNS and routing and
  • access to the portal on the (local) IP of the 540.
  • But they cannot connect to the Internet.

I did read the notification and there a problem is mentioned but there is no URL filtering enabled

https://kb.netgear.com/000062510/WAC540-WAC564-Firmware-Version-9-1-0-13

Any hints what's going wrong? As I said everything worked fine before the FW upgrade.

Many thanks in advance for any comments...

KR,

Christof

[RaghuHR · Accepted solution]

Hi @podex 

Have you enabled client isolation? Could you please save the detailed logs from monitoring page and send it to us? You can upload into google drive and send me link via PM.

Thanks,

Raghu

[podex]

I had a look on the LOGs and there is a statement 

[Fri Dec 4 12:35:06 2020] [INFO ] : Ignoring events on Non trunk Ports

My router does not have a VLAN tagging in use. Could it be that after the FW update this is needed? Is there any tutorial how to do this? 

[RaghuHR · Accepted solution]

Hi @podex 

Have you enabled client isolation? Could you please save the detailed logs from monitoring page and send it to us? You can upload into google drive and send me link via PM.

Thanks,

Raghu

[podex]

Hi @RaghuHR,

Thanks for the answer!

In the mean-time I contacted NETGEAR support (after I've found where to do it 😉 and was told to switch off the Client Isolation feature. This solved the problem, the clients now can connect to the internet.

I think there will be a bug report issued on this topic from the support team, let's see what's the outcome.

KR,
Christof