Cisco Support Community
Community Member

Problem linking 1310 to 350

I have a 1310 providing access to clients via WPA with PEAP against MS IAS. These clients are connecting to our internal native VLAN. Yes - we're also running voice but it is NOT extended to the wireless users. A second SSID allows other unknown clients to connect, but they are tied through trunking to the DMZ segment of an ASA firewall.

So now comes another small group of users who have a 350 bridge that also need to connect to the internal native VLAN.

Might anyone have some pointers on how I can accomplish this? The main site is fully a Cisco shop. 2811 CME/CUE-enabled router. 3560 switch.

This small remote has a linksys router and switch. I had the two linked today over a separate SSID and VLAN with open auth/no encryption - but could not pass traffic. I believe that's related to the fact that the remote devices don't know what to do with the dot1q header.

At layer 3 - our network address is The remote site network is

I have attached the current device configurations for your review... I wish that a newer bridge for the remote site was in the cards, but it's not (for now..) Any pointers/suggestions towards resolution would be greatly appreciated.


Re: Problem linking 1310 to 350

ensure you are configured right ip address in the BVI

Community Member

Re: Problem linking 1310 to 350

I believe the 350 and the 1300 are not compatible. I learned that first hand. Yes they will link, but it will be very sporadic.

Community Member

Re: Problem linking 1310 to 350

I concur. The two are not compatible when you expect to transit VLANs between them. That gem of constraint I finally found in the 1300-series configuration documentation.

Here's the link:

Specifically page 159 where it says:

"Cisco Aironet 1300 and 350 Series Bridges are interoperable when STP is enabled and no VLANs are configured."

Wish I would have known/seen this before hand.

Thanks everyone!

CreatePlease to create content