I've recently had some strange occurrences with HP switches and MT APs, specifically the cAP Lite and the wAP. I'm not doing anything particularly clever - I'm not using CAPsMAN, just a stand-alone unit. Using RouterOS v6.41 and ProCurve firmware P.2.22 (full version string is "HP ProCurve 1810G - 24 GE, P.2.22, eCos-2.0, CFE-2.1").
Switch - reset to defaults, three vLANs created (vLAN tags 1 (default - already present), 2 and 3), switch IP set to 192.168.99.2/24. Ports 1 and 2 are set to vLAN tag vLANs 1,2 and 3. No untagged traffic on those ports. Port 3 is an untagged port for vLAN 1, into which a laptop is plugged with an IP of 192.168.99.99/24. vLAN 1 is the admin vLAN.
So far so good - I can ping and manage the switch via its web interface.
wAP - reset to defaults with no default config, i.e. MAC-winbox access only. Configured to have a vLAN interface "vl-admin" on the ethernet interface, and an IP address of 192.168.99.3/24 is attached to the vLAN interface.
This too is good - no problems - I attach the wAP to port 1 of the switch (which has vLANs 1,2 and 3 tagged) and from an untagged port, can happily ping or ssh to 192.168.99.3 from my laptop. Excellent - all working as planned.
/interface vlan add interface=ether1 vlan-id=1 name=vl-admin /ip address add address=192.168.99.3/24 interface=vl-admin
Then I add a second vLAN interface:
Fine, still working. So now a bridge
/interface vlan add interface=ether1 vlan-id=2 name=vl-two
Again, fine. Now add the vlan interface to the bridge...
/interface bridge add name=br-two
A couple of seconds after doing that, the entire switch stops passing traffic. No response to the switch management interface, no traffic to the wAP, nothing... Physical links are still there, but no traffic passing.
/interface bridge port add bridge=br-two interface=vl-two
If I unplug the wAP, everything comes back to life. Plug it in, and after ethernet has negotiated, it goes down again.
Plug the wAP directly into the laptop, it works fine if I create a vLAN interface to talk to vLAN1 - I can log in and everything looks fine. If I remove the vlan port from the bridge and plug it back into the switch's tagged port, it works fine again until I re-add the vlan interface to the bridge.
Even if I remove all IP addresses from the wAP and use MAC telnet to manage the wAP, the moment the vLAN interface is attached to the bridge, the entire switch goes out to lunch.
This sounds completely braindamaged to me and unless I'd seen it with my own eyes, I wouldn't have believed it.
My only guess is something like LLDP or spanning tree is doing something weird, but I have no evidence to support this - logs from the wAP and switch do not show anything useful so far.
Does anyone have any ideas or am I going mad?