On Sun, 28 Jan 2007 15:32:08 -0500, "Bill Kearney"
wkearney-99@hot-mail-com wrote:
I have the
shore-link router acting as a client but also running DHCP services. The
on-boat router runs nothing, it's just an access point. The ethernet wire
goes between the LAN side of each router. The WAN ports on both of them are
unused. I actually run my gear all into one ethernet switch. That's also
where my Raymarine E-80 is networked along with the SR1000 Sirius marine
weather unit. It's all worked quite nicely this past summer.

-Bill Kearney

Ok, so I have configured a little differently. I use the on-board
WRT54G as an access point as you do, but also use the NAT/DHCP
services in it and I bring in the Wireless Client in through the WAN
port.

I chose to do it this way to be able to preserve the hardware firewall
in the WRT54, separating my on-board network from what ever I attach
to. With more and more open WiFi systems being hosted at a municipal
level (and hence lots of different users on these open WiFi networks),
I want to keep a firewall between me and any outside network I connect
to.

I though about configuring as you have, sure would have solved the
access issues to the Shorelink / Wireless Enternet device I am having,
but I could not see a way to keep a firewall. With your
configuration, is there a firewall in your shorelink / Wireless
client, or somewhere else? Does the open Firmware retain that
capability even when running in Shorelink / Wireless Ethernet mode?

-al-