StarV3 possible problem

[dtoman]

Hi,

It seems that link made of two WAR based devices with StarV3 1.1.0 (1338) doesn't handle properly some packets (spanning tree BPDUs and cisco CDP).

Situation:
we have two locations interconnected by two wireless link (vds tunnel used to create bridged link on WAR devices). There is cisco switch on each side and STP is used to block one of the link. One link is made on WAR and StarOS the second is made on Alvarion OFDM radios in licenced band.

All worked as expected when the WARs were running StarVX. After I upgraded to StarOS V3 1.1.0 the switches are not able to see the bridging loop. There is no signs of STP BPDUs being received from other switch (I tried to disable STP on both WAR). And more the switches are not seeing each other using cisco discovery protocol (CDP) although each switch logs that it is sending CDP hellos to the interface attached to WAR.

'Normal' data packets seems to be delivered fine.

Is it knowng bug? Or is there a chance I made a mistake in configuration?


Regards
Dalibor Toman

[lonnie]

Have you tried the newest firmware? It allows transparent bridging with using VDS which does give a lower throughput.

Just put radio and ethernet into the same bridge group and it enables a special mode for the client. On the AP end you do the same, with radio and ethernet in the same bridge group and then it can talk with the client bridge system.

Make sure to put an IP on only one port so that you can connect to the system for configuration.

Hi,

It seems that link made of two WAR based devices with StarV3 1.1.0 (1338) doesn't handle properly some packets (spanning tree BPDUs and cisco CDP).

Situation:
we have two locations interconnected by two wireless link (vds tunnel used to create bridged link on WAR devices). There is cisco switch on each side and STP is used to block one of the link. One link is made on WAR and StarOS the second is made on Alvarion OFDM radios in licenced band.

All worked as expected when the WARs were running StarVX. After I upgraded to StarOS V3 1.1.0 the switches are not able to see the bridging loop. There is no signs of STP BPDUs being received from other switch (I tried to disable STP on both WAR). And more the switches are not seeing each other using cisco discovery protocol (CDP) although each switch logs that it is sending CDP hellos to the interface attached to WAR.

'Normal' data packets seems to be delivered fine.

Is it knowng bug? Or is there a chance I made a mistake in configuration?


Regards
Dalibor Toman

[dtoman]

Hi,

I didn't try the latest version althought I knew it was released - it is because there was no bridge improvements mentioned in change list. The change log contain only 'custom channel scan list option'.
Shade - if you mentioned the VDS/bridge improvement in the changelog I
could test the 1.1.1 release. Just now our climbers are replacing the WAR boards with another type of radios....


Thanks for the answer

[dtoman]

Note: I will check the StarOS bridge behavior on desk next week.

And - I thought the transparent bridging was not included in V3 becaue there was some troubles with it in the VX version (we didn't observe problems). I think I have read something about it somewhere (this forum, maybe)...

Regards
D. Toman

[lonnie]

All that is required is to put the radios into a bridge group with an Ethernet and it forms a bridge. It uses the transparent WDS support we added in May. It works well and is very easy to setup.

From the changelog on the download page (which is cumulative):
------------------------------------------------------------------
Change log for star-v3 v1.0.0(beta-18) build 1061
May 3, 2006
*) atheros general fixes and updates
*) added the ability to disable unused atheros cards
*) client-mode led blink rate is now correct, and based on signal strength
*) added atheros dynamic wds support
*) added isc dhcp server support
*) added ping watchdog support


Note: I will check the StarOS bridge behavior on desk next week.

And - I thought the transparent bridging was not included in V3 becaue there was some troubles with it in the VX version (we didn't observe problems). I think I have read something about it somewhere (this forum, maybe)...

Regards
D. Toman

[dtoman]

Hi,
thanks for the info. I didn't noticed the wds bridge implementation in beta18.