"Kurt R. Todoroff" <kurt.r.todoroff@comcast.net> hath wroth:
>My restaurant point of sale cash register system consists of a POS
>server in my office and three POS terminals at the front line and
>drive-through stations. I am using a Linksys BEFSR41 router. Since
>neither DSL nor cable is available at my location, my ISP provides
>wireless Internet service via a small antenna on the roof which
>communicates with an antenna on the water tower a couple of tenths of a
>mile down the road. The wireless service uses PPPoE. Its typical
>bandwidth is 800k.
>
>The Linksys router stops functioning and requires restarting at least
>once each day. I unplug the power cable from the back of the router,
>wait five seconds, then plug the power cable into the router, then wait
>thirty seconds. This becomes aggravating if this occurs during a credit
>card transaction.
True. The BEFSR41 and it's wireless cousin, the BEFW11S4v4 have a
reputation for crashing without much provocation. My limited
tinkering with running both off of battery power has not yielded any
improvements in uptime. Running router exploits tests from:
<https://office.learnbydestroying.com:8080/>
will hang some versions of the BEFSR41 and the BEFW11S4v4. I haven
recently received new firmware which may solve the BEFW11S4v4 problem,
but I forgot to try it.
Comparing that with the WRT54G/GS running DD-WRT v23 SP2 and SP3 is
much better. My office at:
<https://office.learnbydestroying.com:8080/>
shows 15 days uptime. My neighborhood WLAN at:
<https://home.learnbydestroying.com:8080/>
shows only 9 hours of uptime because I have it rebooting every
evening. The reboots were not inspired by a hung router. It's
beacause of a bug in the SSH server that causes it to be inaccessible
to remote access after about 3 days of operation. The wireless LAN
and router remain up, but I can't remotely monitor it.
I also have similar coffee shop systems running a mix of WRT54G/GS and
Buffalo WHR-HP-54G and WHR-G54S routers, running mostly DD-WRT v23 SP2
and OpenWRT running WhiteRussian 0.9 (old). All of these have had
uptime issues at some point in time. As experimentation with new
firmware releases appear, the bugs and glitches come and go.
Sometimes, it affects uptime, but more often, some new feature breaks
some old working feature. Much of the exercise is dedicated to
finding the one true versions that has everything you need working.
>My research suggests that this router has a history of this behavior. I
>wish to replace it in order to eliminate the problem. Since I will be
>replacing the router, I have decided to offer wireless Internet access
>to my customers. I have conferred with my ISP about the terms of
>service. Providing Internet access to my customers does not violate the
>terms of service. I am searching for a "g" router that costs less than
>eighty dollars. I plan to disable wireless capability until I have
>determined how I can isolate my server from external intrusion by others
>who are using my router. My POS server is the heart of my business.
>Without it, I'm dead in the water.
Ask your wireless ISP if he can deliver two IP addresses via whatever
you're using for connectivity. With two addresses, you can have two
seperate networks, which only share the 800Kbit/sec bandwidth, but are
otherwise completely isolated from each other. His wireless bridge
radio should easily be able to do that.
The catch is that you will need two routers. One for your POS system,
and one for the customers to wreak havoc. The ethernet output of the
bridge radio goes to a cheap 4 port ethernet switch or hub. From
there, it goes to the two seperate routers. There are many advantages
to this arrangement, not the least of which is lack of complexity,
guaranteed isolation, and the ability to throttle or just turn off the
wireless part when you need the bandwidth. Monitoring the wireless
network might be a problem, but that can be handled with a single PC
using two ethernet cards, one for each network. I've done it like
this, and several other ways in the past.
The DD-WRT firmware is especially suited for running a coffee shop
type of open wireless network. It has various authentication and
authorization schemes built in.
<http://www.dd-wrt.com/wiki/index.php/Chillispot>
V23 SP3 added WifiDog:
<http://dev.wifidog.org>
Or, you could subscribe to a service to run your hotspot for you.
>I have used D-Link routers for the past four years very successfully. I
>have installed six of them (DI-604, DI-524, DI-624) at home, my
>sister's, my father's, my daughter's, and at my other business. Setup
>has always been a piece of cake. I purchased a D-Link WBR-2310 last
>week and installed it at my restaurant to replace the Linksys BEFSR41.
>Setup was a nightmare. I returned it to OfficeDepot and exchanged it
>for another WBR-2310. This one was even worse. It wouldn't even
>recover after I performed a hard reset.
The WBR-2310 is a DI-624 in a new package. Look at the FCC ID number
on the serial number tag for a clue. FCC ID: KA2-DI624D2 I've had
mixed experiences with DLink products over the years. Some are quite
good (DWL-900AP+, DI-604 revE) while other are not my idea of quality.
At this time, I'm doing battle with a pair of new DLink 8 port gigabit
switches, that appear to be the cause of random network packet loss.
Let's just say, you've been lucky.
>This was when I decided to look
>into Linksys. The WRT54G/GL/GS seemed to fit the bill. However, I have
>read that the WRT54G suffers from the same problem that the BEFSR41 does.
They all do. It just varies by frequency. Bottom of the line routers
are not designed for high uptime. I had one local customer ask me to
see if I could do something about his router that was hanging. I
found some neighbor had hacked into his system and was using it for
Bitorrent file sharing. The router couldn't handle the load and would
crash. Eliminate neighbor by tightening the security, and the router
was stable. About a year ago, I was using a BEFW11S4v4 for the
neighborhood WLAN. It hung erratically, so I just installed an AC
power appliance timer to power cycle the box twice a day. End of hang
problem. Whatever works.
If you want high uptime, you'll have to pay for it. Look into
wireless products by Sonicwall, Cisco, and 3com.
>I will look at Netgear routers as well.
Same story. The various mutations of the WGR614 are not all that good
with uptime. I have 2 of them running mountaintop weather stations.
The AC power to these routers is not the best and tends to hang thing.
I have the modems, routers, and controllers on various UPS power
supplies, and they still tend to hang. At this time, I have no remote
reboot system installed, so I have to drive to the mountain to cycle
the power. One a 3rd site, I replaced the WGR614v5 with a Buffalo
WHR-G54S running DD-WRT something. It's been about a month and now it
only hangs when the backup generator is tested or running. Prior to
that, I tried an ancient Sonicwall SOHO-10, which worked prefectly,
but didn't have wireless.
>I appreciate any experience and insight and recommendations that you can
>offer. I have no need for 802.11n capability. I would consider
>purchasing one if the price was right. I need a reliable router that
>does not require daily restarts, and that will shield my server from
>local attacks.
I think you had better look into what it takes to administer a public
wi-fi hot spot. Unauthorized access and abuse are the biggest
headaches. You may find the equipment (RADIUS server), the monitoring
software, and the access key administration, to be too much for your
establishment. Arranging to have a service provider manage the hot
spot would probably be a worthwhile exercise. Answering dumb wireless
setup questions has turned into a time burner for one pizza parlor.
Also, there is the problem of the table hog, who buys one cup of
coffee, and monopolizes the table with his laptop all afternoon.
See the FAQ on how to setup a hotspot:
<http://wireless.wikia.com/wiki/Wi-Fi_How_To#Setup_a_hotspot>
There are also turnkey hotspot solutions, which I'm too lazy to
itemize. Here's one:
<http://www.hotspotsystem.com>
or join a free wireless network:
<http://www.fon.com>
Otherwise, if you want to do it yourself, I think Linksys hardware is
suitable, but I prefer Buffalo. The GS has more RAM and makes some
things easier assuming you're using DD-WRT or other replacement
firmware.
--
Jeff Liebermann
jeffl@cruzio.com
150 Felker St #D
http://www.LearnByDestroying.com
Santa Cruz CA 95060
http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558