On Mar 30, 7:48 pm, Wayne.B wrote:
On 30 Mar 2007 09:55:37 -0700, "Skip Gundlach"

wrote:
My setup has a bridge at the top of the mast, and an AP in the boat.
That worked for a time, including with a Vonage router in between.
Somehow it went off the rails, and I'm currently attempting to make it
retrack.

I've been trying some new equipment since our last discussion about
WiFi. My latest acquisition is an Engenius/Senao NOC-3220 EXT which I
have configured as a bridge and interfaced with POE Cat-5 cable. It
took a while to get it working, thanks in part to my inexperience, and
thanks in part to sketchy documentation which unfortunately seems to
be par for the course.

My advice is to get your bridge first configured directly to a laptop
so that you can confirm that your settings are correct. At that point
you should be able to substitute an AP pre-configured on a different
WiFi channel (maybe ch 1 instead of 6).

Once you have the Ap/router working with a PC you should be able to
plug in the Vonage box to the router and have it take off also.

Take it one step at a time. It is important to avoid IP conflicts
and/or incorrect subnet settings.

Hi, Wayne, and list,

My objective is/was/still is to avoid repetitious plugging and
unplugging of cables. For that matter, it's my objective to set it
and forget it as to cables; I want to be able to address the bridge
wirelessly so that each new harbor can be configured without my having
to do the plug and play bit. It had been my original presumption that
I would have to do as you described, but Bill Kearney and others in
this space have asserted that it's not necessary.

I have yet to achieve a stable configuration which doesn't have the
plug/unplug/replug requirement, let alone that plus handset/dial tone
telephony, but my second generation unit(s) have yet to surface as I
have a few more pressing issues to address at the moment. Thus, I
expect to succeed at that eventually. I had it once, but it went
Tango Uniform a while into my experience which was, in a word,
ecstatic, while it lasted.

Thus, for the immediate time, I am doing as Dave has done, and have
nothing other than a mast-top configured bridge, connected to an
antenna and POE, with ethernet to my computer. It allows skype and
google internet telephony, and surf an mail, which suffices for right
now.

L8R

Skip

On 30 Mar 2007 20:01:04 -0700, "Skip Gundlach"
wrote:

For that matter, it's my objective to set it
and forget it as to cables; I want to be able to address the bridge
wirelessly so that each new harbor can be configured without my having
to do the plug and play bit. It had been my original presumption that
I would have to do as you described, but Bill Kearney and others in
this space have asserted that it's not necessary.

At the very least the bridge will have to be reconfigured to address a
new SSID unless you only look for defaults. Reconfiguring should be
really quick and painless once you get the process down.

1. Network scan
2. Select SSID
3. Connect
4. Test with PC
5. Disconnect PC, connect AP/router, test

On Mar 31, 12:11 am, Wayne.B wrote:
On 30 Mar 2007 20:01:04 -0700, "Skip Gundlach"

wrote:
For that matter, it's my objective to set it
and forget it as to cables; I want to be able to address the bridge
wirelessly so that each new harbor can be configured without my having
to do the plug and play bit. It had been my original presumption that
I would have to do as you described, but Bill Kearney and others in
this space have asserted that it's not necessary.

At the very least the bridge will have to be reconfigured to address a
new SSID unless you only look for defaults. Reconfiguring should be
really quick and painless once you get the process down.

1. Network scan
2. Select SSID
3. Connect
4. Test with PC
5. Disconnect PC, connect AP/router, test

Agreed. However, see above. I have no problem with my current
unit. I knew it well enough to guide Lydia by memory to test it when
I first put it in, from the top of the mast.

I just don't want to do the unplug/replug/return-to-setup stages if I
don't have to; I've been repeatedly assured it can be done...

L8R

Skip, off to the Blue Angels and other flying non-pigs :{))

On 31 Mar 2007 05:14:27 -0700, "Skip Gundlach"
wrote:

I just don't want to do the unplug/replug/return-to-setup stages if I
don't have to; I've been repeatedly assured it can be done...

We'll see but I wouldn't get your hopes up. I have spent over 6
months working from the boat in the last 2 years while cruising 8,000
miles, sometimes connecting to 2 or 3 different APs in a single week.
Almost all have unique SSIDs, and many require sign-on through a web
proxy.

I was reluctant to mention the following in my original post due to
the fact that it involves beta software and as such may be flakier
than desired, but DD-WRT firmware does support a wireless repeater
function:

http://www.dd-wrt.com/wiki/index.php...eless_Repeater

It requires the v24 beta firmware, but the finalized v24 firmware is
expected soon. The nice thing about this setup is that you can use
your router as a bridge that is directly wired to your computer. Once
you get it working flawlessly, you just change the "wireless mode"
pull-down menu to select "repeater" and you are doing the same thing
but without the ethernet cable.

Note: I have not tried this. I am not interested in trying it. But
based on my experience with DD-WRT, I know that it works and works
well.

The one aspect of this that I like is that avoids the need for
ethernet up the mast. I am always skeptical that un-tinned, small
guage, solid wire is just not durable in a marine environment. I
expect that I will toy with this in the furture as a means of ensuring
that if even my ethernet cable corrodes to the point of being un
useable, I will just switch to repeater mode and do it wirelessly.


David
S/V Nausicaa

On Mar 30, 8:01 pm, "Skip Gundlach" wrote:
On Mar 30, 7:48 pm, Wayne.B wrote:



On 30 Mar 2007 09:55:37 -0700, "Skip Gundlach"

wrote:
My setup has a bridge at the top of the mast, and an AP in the boat.
That worked for a time, including with a Vonage router in between.
Somehow it went off the rails, and I'm currently attempting to make it
retrack.

I've been trying some new equipment since our last discussion about
WiFi. My latest acquisition is an Engenius/Senao NOC-3220 EXT which I
have configured as a bridge and interfaced with POE Cat-5 cable. It
took a while to get it working, thanks in part to my inexperience, and
thanks in part to sketchy documentation which unfortunately seems to
be par for the course.

My advice is to get your bridge first configured directly to a laptop
so that you can confirm that your settings are correct. At that point
you should be able to substitute an AP pre-configured on a different
WiFi channel (maybe ch 1 instead of 6).

Once you have the Ap/router working with a PC you should be able to
plug in the Vonage box to the router and have it take off also.

Take it one step at a time. It is important to avoid IP conflicts
and/or incorrect subnet settings.

Hi, Wayne, and list,

My objective is/was/still is to avoid repetitious plugging and
unplugging of cables. For that matter, it's my objective to set it
and forget it as to cables; I want to be able to address the bridge
wirelessly so that each new harbor can be configured without my having
to do the plug and play bit. It had been my original presumption that
I would have to do as you described, but Bill Kearney and others in
this space have asserted that it's not necessary.

I have yet to achieve a stable configuration which doesn't have the
plug/unplug/replug requirement, let alone that plus handset/dial tone
telephony, but my second generation unit(s) have yet to surface as I
have a few more pressing issues to address at the moment. Thus, I
expect to succeed at that eventually. I had it once, but it went
Tango Uniform a while into my experience which was, in a word,
ecstatic, while it lasted.

Thus, for the immediate time, I am doing as Dave has done, and have
nothing other than a mast-top configured bridge, connected to an
antenna and POE, with ethernet to my computer. It allows skype and
google internet telephony, and surf an mail, which suffices for right
now.

L8R

Skip

On 31 Mar 2007 19:47:22 -0700, wrote:

The one aspect of this that I like is that avoids the need for
ethernet up the mast.

You've got to get power up there some how.

On Apr 1, 12:13 am, Wayne.B wrote:
On 31 Mar 2007 19:47:22 -0700, wrote:

The one aspect of this that I like is that avoids the need for
ethernet up the mast.

You've got to get power up there some how.

Power run through 14ga. tinned, multi-stranded wire enclosed in a
thick and resliant cover and called "marine grade duplex" is many
orders of magnitude more chafe, UV, corrosion, and voltage drop
resistant than even the best marine grade ethernet cable.

That said, I do have ethernet up my mast, but if it fails and I am not
planning on dropping my stick soon, I'll revert to repeater mode.
Multiple redundancy is good seamanship.... even if WiFi is a non-
mission-critical extravagance

David Braun
S/V Nauisicaa

On 1 Apr 2007 08:32:21 -0700, wrote:

Power run through 14ga. tinned, multi-stranded wire enclosed in a
thick and resliant cover and called "marine grade duplex" is many
orders of magnitude more chafe, UV, corrosion, and voltage drop
resistant than even the best marine grade ethernet cable.

I think we'd all agree with that although 14 ga is way overkill.

That said, I do have ethernet up my mast, but if it fails and I am not
planning on dropping my stick soon, I'll revert to repeater mode.
Multiple redundancy is good seamanship.... even if WiFi is a non-
mission-critical extravagance

All well and good but does it leave you with the option of
reconfiguring your bridge to a new SSID, or sign on to a WiFi proxy
site? In other words, can you still communicate over the repeater
link to the bridge if no shore connection to an AP exists?

On Apr 1, 9:20 am, Wayne.B wrote:
On 1 Apr 2007 08:32:21 -0700, wrote:

Power run through 14ga. tinned, multi-stranded wire enclosed in a
thick and resliant cover and called "marine grade duplex" is many
orders of magnitude more chafe, UV, corrosion, and voltage drop
resistant than even the best marine grade ethernet cable.

I think we'd all agree with that although 14 ga is way overkill.

That said, I do have ethernet up my mast, but if it fails and I am not
planning on dropping my stick soon, I'll revert to repeater mode.
Multiple redundancy is good seamanship.... even if WiFi is a non-
mission-critical extravagance

All well and good but does it leave you with the option of
reconfiguring your bridge to a new SSID, or sign on to a WiFi proxy
site? In other words, can you still communicate over the repeater
link to the bridge if no shore connection to an AP exists?

As I said, I have not done this but based on my knowledge of the DD-
WRT firmware, I'll project what I think the answers would be. If
anyone has direct experience, please correct me.

Regarding new SSID: This is the beauty of the Auto AP script. It sends
out a ping to a time server on the internet every 30 seconds. If the
ping fails, it automatically reconnects to whichever AP has the
strongest signal. It requires no input from the downstream computer.
In fact even when it is used in a wired bridge mode, you will not
always have access to the device as it may be on a different subnet.
This is expalined in the Wiki referenced in the original post.

If you need to sign onto a wifi proxy, you can always contact it
wirelessly by manually changing your IP address to the same subnet as
the bridge/repeater. Make your changes and then go back to DHCP for
bridging into the network of choice. If this fails, you can regain
access to the device that is aloft by cycling its power. This will
return it to its original IP address and you can certainly contact it
as previously described.

Wayne, you seem to be a little skeptical about all this and I can
understand that. I have bought about 5 wireless routers and access
points trying to accomplish this project. Each one had some limitation
in the software that prevented them from working the way I knew they
were capable of operating. Once I discovered DD-WRT, it was this
amazing playground. Every option available in every router plus more
was all rolled into one. Plus contributors were writing code and
scrips that added into the firmware to create even greater
functionality. I suggest that you dig out some old router that you
have lying around and load DD-WRT on it. You will quickly see the
power inherrant in this firmware. But don't forget the Buffalo router.
This is an amazing piece of hardware for the money. I regret that I
didn't take any photos of my project before I bolted it to the top of
my mast, but I may be building a system for a friend and will take a
series of photos of that. It is the 5" x 5" board that makes this
router so ideal for using aloft. I even do some board level mods to
make it easier to fit into a small case.

David
S/V Nausicaa

On 1 Apr 2007 23:39:21 -0700, wrote:

Once I discovered DD-WRT, it was this
amazing playground. Every option available in every router plus more
was all rolled into one. Plus contributors were writing code and
scrips that added into the firmware to create even greater
functionality. I suggest that you dig out some old router that you
have lying around and load DD-WRT on it.

Interesting, good information.

Since I don't have any old routers laying around that are DD-WRT
capable, which would you recommend buying? Do any of them have a way
of recovering from a "bricked" state due to a faulty firmware load?
What programming language is the DD-WRT code written in, and what
development tools do you need for hacking around with it?

One issue that I have is goals and priorities. My priority is
achieving reliable WiFi service on the boat, not becoming a
router/bridge/DD-WRT expert. :-)