Do Virtual AP's work with SR2s or is the card bust.

Running 2.9.38 - other os/s also seem to work the same tried 2.9.34/29

After a 46degC day in Saturday when the Aircon in our comms room stopped along with the adjacent FM transmitter, we decided to replace a flakey sector Senao miniPCi AP with a new WRAP board with a SR2.
Our configuration is
WAN on Ether2
Hotspot on wlan1
PPPOE server on wlan2 Virtual AP
2xWDS links on WLAN1
This has worked ok before - but this is our first SR2.

The SR2 reports
int wir info print
0 interface-type=Atheros AR5213
chip-info="mac:0x5/0x9, phy:0x43, a5:0x46, a2:0x0, eeprom:0x4008"
pci-info="00:0d.0" capabilities=tx-power-control,ack-timeout-control,
virtual-ap,alignment-mode,noise-floor-
control,scanning,burst-support,nstreme,
sniffing,compression,power-channel
default-periodic-calibration=enabled...
1 interface-type=virtual-AP
so it thinks it can support a VAP.

IPs are assigned thus
ip address print
Flags: X - disabled, I - invalid, D - dynamic

ADDRESS NETWORK BROADCAST INTERFACE

0 xxx.11.202.82/28 xxx.11.202.80 xxx.11.202.95 ether2
1 xxx.11.202.102/30 xxx.11.202.100 xxx.11.202.103 wds1
2 xxx.11.202.106/30 xxx.11.202.104 xxx.11.202.107 wds2
3 10.82.50.1/24 10.82.50.0 10.82.50.255 wlan1 (hotspot)
4 10.82.60.1/24 10.82.60.0 10.82.60.255 wlan2 (pppoe)
5 192.168.0.1/24 192.168.0.0 192.168.0.255 wlan1
The last three are pooled..

A pppoe-server server is assigned to VAP wlan2

With the VAP Wlan2 disabled then the WDS links work on wlan1
ping xxx.11.202.101
xxx.11.202.101 64 byte ping: ttl=64 time=26 ms
xxx.11.202.101 64 byte ping: ttl=64 time=19 ms
xxx.11.202.101 64 byte ping: ttl=64 time=4 ms
xxx.11.202.101 64 byte ping: ttl=64 time=98 ms
xxx.11.202.101 64 byte ping: ttl=64 time=4 ms
xxx.11.202.101 64 byte ping: ttl=64 time=10 ms
xxx.11.202.101 64 byte ping: ttl=64 time=4 ms
7 packets transmitted, 7 packets received, 0% packet los
for example.
Enable the VAP on wlan2
ping xxx.11.202.101 on wlan1
xxx.11.202.101 ping timeout
xxx.11.202.101 ping timeout
3 packets transmitted, 0 packets received, 100% packet loss

mode=ap-bridge ssid=xyzz area=""
frequency-mode=manual-txpower country=no_country_set antenna-gain=0
frequency=2437 band=2.4ghz-b scan-list=default rate-set=default
supported-rates-b=1Mbps,2Mbps,5.5Mbps,11Mbps
supported-rates-a/g=6Mbps,9Mbps,12Mbps,18Mbps,24Mbps,36Mbps,48Mbps,
54Mbps
basic-rates-b=1Mbps basic-rates-a/g=6Mbps max-station-count=2007
ack-timeout=dynamic tx-power-mode=default noise-floor-threshold=default
periodic-calibration=default periodic-calibration-interval=60
burst-time=disabled dfs-mode=none antenna-mode=ant-a wds-mode=static
wds-default-bridge=none wds-default-cost=100 wds-cost-range=50-150
wds-ignore-ssid=no update-stats-interval=disabled
default-authentication=yes default-forwarding=no default-ap-tx-limit=0
default-client-tx-limit=0 proprietary-extensions=post-2.9.25
hide-ssid=no security-profile=default disconnect-timeout=3s
on-fail-retry-time=100ms preamble-mode=both compression=no
allow-sharedkey=no

1 X name="wlan2" mtu=1500 mac-address=02:15:6D:53:31:D5 arp=enabled
disable-running-check=no interface-type=virtual-AP
master-interface=wlan1 ssid="abcdd" area="" max-station-count=2007
wds-mode=disabled wds-default-bridge=none wds-default-cost=100
wds-cost-range=50-150 wds-ignore-ssid=no default-authentication=yes
default-forwarding=no default-ap-tx-limit=0 default-client-tx-limit=0
proprietary-extensions=post-2.9.25 hide-ssid=no
security-profile=default

Any clue or is the card or os bad

Thanks
Ken K.

I reset the router config overnight to no avail, so we took out the SR2 and
replaced it with an Atheros card, to noavail.
As may have been evident from my previous post we run two SSID’s
one for Hotspots and one for PPPOE’s, and this occurs across an OSPF
semi mesh.

The problem now seems that with the AP which has worked in this configuration for 18months is as soon as the PPPOE SSID on the VAP matches thePPPOE used on the mesh then the WDS which associates by the Hotspot SSID locks up.

There isnt a second association on the router for the VAP
access point when the SSID is enabled. None of the other possible
association points have WDS enabled in their Virtual Access Point.

Could a RAM problem in the WRAP Board cause this..

Thanks Kenk