Users connected via rfs are unable to ping internet or gateway

[Nilac]

Hello,

I have the following scenario.

Wireless windows 10 client >>Extreme AP621 >> Extreme controller NX5500 version 5.9.4.0-020R >> Meraki firewall
Problem.
I have created a vlan on Meraki (vlan 22) with ip 192.168.22.1. Controller is directly connected into a access vlan on Meraki vlan 22.
Users are able to connect to ssid, but are unable to ping gateway or internet.

Controller config

NX5500#sh run
!
! Configuration of NX5500 version 5.9.4.0-020R
!

wlan 22
 ssid "test"
 vlan 22
 bridging-mode local
 encryption-type ccmp
 authentication-type none
 wpa-wpa2 psk 0 XXXXXXXXX
!
wlan work
 ssid work
 vlan 1
 bridging-mode local
 encryption-type ccmp
 authentication-type none
 wpa-wpa2 psk 0 XXXXXXXXX

nx5500 xxxxxxxxxxxxxxxxxx
 use profile default-nx5500
 use rf-domain xxxxxx
 hostname NX5500Secondary
 ip default-gateway 192.168.12.1
 interface vlan1
  ip address 192.168.12.3/24
 cluster name Cluster
 cluster mode standby
 cluster member ip 192.168.12.2
 cluster member ip 192.168.12.3
!
nx5500 XXXXXXXXXXXXXXXXXXXX
 use profile default-nx5500
 use rf-domain xxxxxxxxx
  ip default-gateway 192.168.12.1
 interface ge2
  switchport mode access
  switchport access vlan 22
 interface vlan1
  ip address 192.168.12.2/24
 interface vlan22
  description "test"
  ip address 192.168.22.2/24
 cluster name Cluster
 cluster mode active
 cluster member ip 192.168.12.2
 cluster member ip 192.168.12.3

ap7522 XXXXXXXXXXX
 use profile anyap-XXX-SITE
 use rf-domain XXXX
 hostname AP1
 interface vlan1
  ip address 192.168.12.10/24

[Christoph_S]

Since bridging mode is set to local, traffic is handled by the APs and those should learn about the default gateway as well. If using DHCP, the following line should be included in the native VLAN settings:

  ip dhcp client request options all
 

If only using static IPs, then you will either need to add the default gateway to the AP profile (on the controller) or add it to each AP as an override in the VLAN interface settings (again on the controller). In this case you will need to configure the DNS IP address/es as well. 

These instructions may help: 

https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-configure-a-new-or-replace-an-exist...

I hope this helps,

Chris

[Christopher_Fra]

The WLANs are locally bridged, so the AP needs to carry VLAN 22 via 802.1q (trunk port) with VLAN 1. The NX will only carry VLAN 1 for adoption/management.