Hi Scott,

 

From the following setup, I hope that you have connected "bridge 1" to the internet thru ROUTER.

 

INTERNET -> bridge 1 -> ap 1 -> lan -> bridge 2 -> ap 2 -> Client

Computer

 

With the newer firmware(0.01.04 or 0.01.07) loaded on the "bridge 1", the "Clients" will not be able to get to internet thru router. This is correct symptom as the "bridge 1"does Mac translation causing this design unsuitable for routing. It can only work between on the site to site.

 

To workaround this problem, you can downgrade the "bridge 1" to older firmware 0.09.10, and this will become transparent bridge with single Mac support. The "bridge 1" is connected directly to the router so it can see only the router as single client.

In order to downgrade to the old firmware, please install the simpleMonitor 1.43 which is already built in with old firmware 0.09.10.

http://www.smartbridges.com/new/support/ab.php

 

Alternatively, replace the "bridge 1" with airPoint/Pro and configured in CB mode and this will provide you with transparent bridge and multi MAC support.

 

This issue has been posted in our website and here is the link for your reference.

http://www.smartbridges.com/new/support/faq_ab.php#155

 

Thank you

 

Seeni

sB Tech Support

[EMAIL PROTECTED]

 

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Brooks
Sent: Wednesday, September 24, 2003 8:33 AM
To: '[EMAIL PROTECTED]'
Cc: 'Sajid Ikram'
Subject: [smartBridges] Problems with bridge->ap->bridge->ap link

 

Due to some line of sight issues, we have the following setup.

 

Internet -> bridge 1 -> ap 1 -> lan -> bridge 2 -> ap 2 -> Client

computer

 

Between Bridge 1 and AP 1 is about 500m and the RSSI/LQ is great on that

shot.  Between Bridge 2 and AP 2 it's about 8 miles and the RSSI is

about 50% and the LQ is around 75%.

 

We are seeing the following issue.  From the client computer we can ping

any local IP address, ssh into our servers, do pretty much anything we

need to, except connect out to an external host on the network.

 

>From what we have found is that it looks to be an issue with the bridges

and how they handle mac addresses.  For example if I try to ping the IP

address 204.244.59.X from the client computer it times out, if I then

ssh into our router from our client computer, then ssh into 204.244.59.X

and try pinging the client computer the ping goes through.  Finally, if

I try pinging 204.244.59.X from the client computer after pinging it

from 204.244.59.X it goes through.  This leads me to think that the

bridges have a hard time learning the mac addresses they should send

data to, and after data comes back one way they are able to find out the

proper mac addresses.

 

We plan on replacing one of the bridges with another AP in client bridge

mode, and then see if it solves the problem, but has anyone else run

into the same issue, or something similar.

 

--

Scott Brooks

Network Operations Analyst

Binary Solutions Ltd.

[EMAIL PROTECTED]

 

----------ANNOUNCEMENT----------

Don't forget to register for WISPCON IV

http://www.wispcon.info/us/wispcon-iv/wispcon-iv.htm

 

The PART-15.ORG smartBridges Discussion List

To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges <yournickname>

To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges)

Archives: http://archives.part-15.org 

Reply via email to