Hi.
Please, support vlan dot1q technology in your products - Motorola Canopy.
Canopy is nice for us, only unsupporting of dot1q is weak.
Scheme - Cisco router === Ethernet trunk === Canopy AP - - - Canopy SM
is great for connecting clients.
In this case, Canopy SM is one dot1q vlan.
In Cisco config very simple
int fa0/0
description Canopy AP-0
!
int fa0/0.10
description Client’s Network-1
encapsulation dot1q 10
ip address x.x.x.x 255.255.255.252
!
int fa0/0.20
description Client’s Network-2
encapsulation dot1q 20
ip address y.y.y.y 255.255.255.252
!
P.S.: Sorry for terrible English!
P.P.S.: I hope, this letter was readed Canopy developers
With best regards, Pavel S. Shirshov
Pavel,
Canopy developers are well aware of this request. VLAN support is being reviewed for future releases.
P.S. Your english was great. There was nothing terrible about it!
Regards,
Canopy_support
Canopy_Support wrote: Pavel,
Canopy developers are well aware of this request. VLAN support is being reviewed for future releases.
I would like to strongly emphasize the need for 802.1q support. We generally are using Cisco switches at our popsites in order to support VLAN capabilities into our access points. I currently run 802.1q trunking THROUGH BH20 units between switches. Unfortunately, we are unable to use the MicroCMM in our network due to its lack of 802.1q support, and we must significantly rewire the original CMMs in order to bypass the internal ethernet switch which doesn't support any type of management whatsoever.
Regards,
Ron
I’ve had to take the CMM switch out too. It would have saved me a lot of time and cable to have a decent switch in the CMM. While you are at it, QOS support would be a plus.
Dave
It’s nice to see I’m no the only one cramming a managed switch in to the CMM.
Just for fun I sent an email to Canopy Tech Support asking about the VLAN tagging. This is the response I got…
Thank you for your inquiry.
We are constantly looking for ways to deliver more value to our customers,
whether it is via feature enhancements, new technologies or advanced volume
manufacturing. However, our policy is to not comment, speculate or address
rumors of this nature regarding future events or planned product
announcements.
If you need to reply to this email, please include the original email
message for our reference.
Thank you,
The Motorola Canopy Team
1-888-605-2552
:?:
I think they’re letting the cleaning guy respond to emails now. :lol:
Just joking. But they sure are good at avoiding any problems. Generic email I guess.
Aaron
http://motorola.canopywireless.com/press/102704c.php
That is NOT Motorola saying they support VLAN. But maybe this Robert knows a hack to make it work.
"We’ve been able to test Canopy’s Advantage platform with some of our new 900 Megahertz radios and we experienced significant improvements in data throughput and reduced latency. Not only are these important for data services, but as a result we can provide VoIP and virtual local area network (VLAN) enhanced services to our customers," said Robert Zakarian, president and chief executive officer of Community WISP, a Wireless Internet Solutions Provider in the Greater Boston Area.
That is NOT Motorola saying they support VLAN. But maybe this Robert knows a hack to make it work.
I know a way to make it work. Canopy will pass VLAN tagging so all we need to do is put a managed switch at each customers location, with a dedicated AP for each customer, and a managed switch inside the CMM.
Motorola must have a better way than this. I hope they tell us soon. I wonder if the Advantage platform will do VLAN tagging by itself. I hope so.
Thanks for the article, mattmann72. 
Here is my application.
I have a set of BH’s. At each end I have a managed switch doing VLAN tagging for security reasons. I would like to use SNMP to monitor the BH radios but they do not decognize the 802.1Q tag and therefore will not respond to any data, unless I turn the tags off.
All I want is for Canopy to see the tags and read them. If the packets are tagged with a VID that matches the radios, then either respond with tagged packets if it is a request for that radio, or just forward the packets. If the packets are tagged with a different VID than it’s own, then just forward them.
That should be simple enough.
Anyone have a different application?
Aaron
Holy Crap!! If you read this…
http://motorola.canopywireless.com/press/112304.php
…about half way down, it talks about the Advantage radios supporting VLAN tagging. At least, that’s what I get out of it.
Aaron
Aaron,
You are correct. We will have VLAN tagging capabilities built into the SM’s. Please see the following for high level 6.1 features:
http://www.canopywireless.com/softwareu … hp?catid=1
Thanks for the info, Canopy Guy. Is there any word on when 6.1 will be released?
Thanks again.
Aaron
There are no dates which I can comment on at this time. I can assure you that due to the added features we want to put this release through rigorous testing. So we are working hard on it and it should be available soon.
Canopy_Support wrote: Aaron,
You are correct. We will have VLAN tagging capabilities built into the SM's. Please see the following for high level 6.1 features:
http://www.canopywireless.com/softwareu ... hp?catid=1
This is great news if you run SMs, but what if you run BH and BH20s and CMM2/Micro? I'm about to have to pull a CMM/Micro out of a site because it won't support 802.1q, and drop a bastardised CMM2 with Cisco2912 in its place.
Regards,
Ron
I guess we will find out on Wednesday. That’s when the 6.1 firmware will be released for download.
I wonder if the Canopy Guys an tell us inadvance if 6.1 will allow backhauls to support 802.1q VLAN tagging? :?:
Aaron
I found a way around this problem for me.
We use cisco switches here, 3550 at the main tower and 2900xl at the hops/pops.
If you set your config like so… VLAN1 will always go over the trunk. So if you assign you BH10 or BH20 IP address to the vlan1 (primary or secondary) you will be able to communicate with your BH unit over the 802.1q trunks using native vlan (default VLAN1) and you can tag other vlans for your customers or other traffic.
I have BH units off of VLAN1 which WILL ride over your 802.1q trunks.
But, if you terminate your trunk at a switch at you pop and have a backhaul attached to that port, then you can assign the BH ipaddress to the trunk vlan as a secondary.
My example…
interface Vlan1
ip address 10.0.10.1 255.255.255.0 secondary
ip address 10.0.30.1 255.255.255.0 secondary
ip address 10.0.40.1 255.255.255.0 secondary
ip address 10.0.50.1 255.255.255.0 secondary
ip address 10.0.60.1 255.255.255.0 secondary
ip address 10.0.70.1 255.255.255.0 secondary
ip address 12.252.228.49 255.255.255.240
!
interface Vlan101
description Paxton Tower CCU101
ip address 10.0.11.1 255.255.255.0 secondary
ip address 12.252.243.1 255.255.255.0
!
interface Vlan102
description Paxton Tower CCU102
ip address 10.0.12.1 255.255.255.0 secondary
ip address 12.252.246.1 255.255.255.0
!
interface Vlan111
description Paxton Tower NCL111
ip address 12.252.228.157 255.255.255.252
!
interface Vlan301
description Loda Water Tower CCU301
ip address 10.0.31.1 255.255.255.0 secondary
ip address 12.252.244.193 255.255.255.192
!
interface Vlan401
description CissnaPark Elevator CCU401
ip address 10.0.41.1 255.255.255.0 secondary
ip address 12.252.245.1 255.255.255.128
!
interface Vlan411
description CissnaPark Elevator NCL411
ip address 12.252.228.141 255.255.255.252
!
interface Vlan501
description Gilman Elevator CCU501
ip address 10.0.51.1 255.255.255.0 secondary
ip address 12.252.245.129 255.255.255.128
!
interface Vlan601
description Milford Water Tower CCU601
ip address 10.0.61.1 255.255.255.0 secondary
ip address 12.252.244.129 255.255.255.192
!
interface Vlan701
description Danforth Elevator CCU701
ip address 10.0.71.1 255.255.255.0 secondary
ip address 12.252.231.1 255.255.255.192
!