| ï
No luck. I downgraded to lower firmware and
nothing.
I am going to try and reset it by using the
button on PowerShot and trying from scratch. Otherwise, I have to dump the
equipment and move to something else. Way too much time spent on this
what-should-be-simple setup. It did work for about 5 mins until I tried enabling
WEP. Ever since though, nothing.
Where are you located that you have 55MPH wind?
I'm in PA and have the same problem. Trees down everywhere :-(
Where can I get 1.4j.9? Maybe that will do
it?
===
Rick Kosick
StarLinX Internet Service
----- Original Message -----
Sent: Friday, November 14, 2003 10:47
AM
Subject: Re: [smartBridges] Why not to
use smartBridge...
Hi Rick,
Turns out that I'm also having problems getting
2 aPPOT units to bridge. At first, I was having trouble with one of the
appot to broadcast it's ssid. The other appot did not take up the ssid
changes I made to it. Whenever sniffing wirelessly, its ssid appeared as
airPointProOutdoorTOTAL. After re-flashing the rom, rebooting, and
switching from wireless bridge mode to client bridge mode then back to
wireless bridge mode, the ssid appears properly on the second unit.
(Note, that the ssid as seen from the monitor program would always appear as
the correct one. It was only from looking at the wireless broadcast that
I could see that the ssid was incorrect.)
Well, anyway it is way too
windy here today for me to continue (55 mph winds!), so I'll take another look
at it tomorrow.
Any luck with your setup???
Sevak
On Thu,
2003-11-13 at 09:19, Rick Kosick wrote:
ï
Software: 1.6
Firmware: 1.4j.8
Both
sides.
===
Rick Kosick
StarLinX
Internet Service
----- Original Message -----
From: Sevak
Avakians
To: [EMAIL PROTECTED]
Sent: Thursday, November 13, 2003 9:11 AM
Subject:
Re: [smartBridges] Why not to use smartBridge...
Rick, if you got
the firmware off the website, it may not be the latest. Usually sb
has a beta version that they post on this list and most of us use before
it is posted to the website.
Check the version number using
simpleNMS or the firmware upgrade utility.
Sevak
On Thu,
2003-11-13 at 09:05, Rick Kosick wrote:
ï
I don't
know the actual version number but I just downloaded it off the website
in the past few days and it is the very latest on both
sides.
This part about it bringing the switch to its knees
is VERY disturbing because a switch, by its design, should not allow
that to happen normally. I can see it happening to a
hub.
I was working on this remotely (from home) at late
hours both times and had to drive to the NOC to remedy it because I
couldn't access any machines via PC Anywhere. The whole network crashed
basically.
===
Rick Kosick
StarLinX Internet Service
----- Original Message -----
From: Blazen
Wireless
To: [EMAIL PROTECTED]
Sent: Thursday, November 13, 2003 8:59
AM
Subject: Re: [smartBridges] Why not to use
smartBridge...
Interesting
what firmware were you using which should not affect your switch like
that just curious to know..
----- Original Message -----
From: Rick
Kosick
To: [EMAIL PROTECTED]
Sent: Thursday, November 13, 2003 5:39
AM
Subject: [smartBridges] Why not to use
smartBridge...
So far I've
come up with three good reasons to not continue to use smartBridges
but I'm open to suggestions for fixing these problem. Pardon my
frustration but I have 3 years of wireless experience and its taking
me more than 10 hours of fiddling to get a simple Wireless Bridge to
Wireless Bridge up and running and I am sitting here with more
problems than solutions right now.
1) Last week I
plugged the ethernet side of an APPO into an APCC PNET4 ethernet
surge supressor where there where three other devices plugged in.
This caused severe packet loss on the other devices. Pinging the
other devices between each other would result in 4 out of 10 pings
timeing out.
SOLUTION: Bypass the ethernet surge
supressor.
2) Right now I
have two APPO's configured in Wireless Bridge mode (which won't
work, see #3). At my NOC side its plugged into a D-Link DES3226
Managed Switch. If I put the APPO into Access Point mode, it KILLS
the traffic on my switch entirely to the point where
workstations and servers can barely reach each other. As soon as I
unplug the APPO's ethernet connection from the switch, immediately
everything goes back to normal. This has happened twice now in my
quest to get my wireless link working.
SOLUTION: No idea. Maybe avoid Access Point
mode?
3) I have to admit I did enjoy 3 minutes of
Wireless Bridge mode where everything worked as it was expected, but
I got adventerous and enabled WEP. This did not work out for some
reason and now, after disabling WEP... I cannot get the Wireless
Bridge mode to work again. I've reset to Defaults and started over,
still nothing. I simply cannot get Wirless Bridge to Wireless Bridge
mode to work at this point. I've been through the "recycling both
sides", "double checking MAC#'s", etc. You'd think that if this was
going to work at all, I would have accidentally made it work by
now.
SOLUTION: None as of
yet.
Clearly, when considering points #1 and #2 above, there is
more happening on the ethernet side of the link than just ethernet.
Something is different than a standard ethernet connection
because this radio clearly caused major packet loss between the
other devices plugged into am ethernet surge supressor. Maybe
power is leaking through from the PowerShot device? And, its ability
to completely bring a managed switch to its knees just reassures
this..
===
Rick Kosick
StarLinX Internet
Service
|
