<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
<br><br>Hi Y'all,<br>
<br>
<br>
<br>
On Fri, 2008-04-25 at 14:57 +1200, Martin Langhoff wrote:
<blockquote type="CITE">
<pre><font color="#000000">On Fri, Apr 25, 2008 at 2:38 PM, John Watlington <<a href="mailto:wad@media.mit.edu">wad@media.mit.edu</a>> wrote:</font><br><font color="#000000">></font><br><font color="#000000">> Proposed change to the hardware spec:</font><br><font color="#000000">></font><br><font color="#000000">> From one to four access points may use an simpler switch,</font><br><font color="#000000">> connected to the server over a 100 Mb/s link. From five to seven</font><br><font color="#000000">> access points will need a better switch, which provides a 1 GB/s</font><br><font color="#000000">> link to the server.</font><br><font color="#000000">></font><br><font color="#000000">> This means that a 1 GB/s interface should be specified for the servers</font>.<br></pre>
</blockquote>
<br>
I feel teleported back to my 3-19-08 mail:<br>
<br>
[...] <br>
(I am thinking server clusters - red hat cluster suite is offering some nice tools which I never got a chance to use / try - thinking 3 servers with fail-over and increased performance for clients (like two servers actually doing something...) would be a starting point)<br>
Birmingham is looking at 49 schools with a total 14,000+ students.<br>
[...]<br>
<br>
<blockquote type="CITE">
<pre><br><font color="#000000">Theoretically, yes... but perhaps this is a bit over the top. For the</font><br><font color="#000000">space we are aiming...</font>
</pre>
</blockquote>
<br>
please define our aim<br>
<br>
<blockquote type="CITE">
<pre><br><font color="#000000"> - the XS services will bottleneck well before saturating 1Gb/s traffic</font><br><font color="#000000"> - 'upstream' services that the XS is routing will bottleneck well before 1Gb/s</font><br><br><font color="#000000">if we see a 7-AP setup, it will be there to support either a large</font><br><font color="#000000">number of laptops or a location with obstacles that needs many</font><br><font color="#000000">antennaes. In any case, it will support laptops mostly peering w</font><br><font color="#000000">eachother.</font>
</pre>
</blockquote>
<br>
how about those 14 - 28 AP setups?<br>
<br>
<blockquote type="CITE">
<pre><br><font color="#000000">If we are designing for a "client base" of laptops that we actually</font><br><font color="#000000">expect to saturate 1Gb, then... we need to start recommending a</font><br><font color="#000000">mid-range server cluster, perhaps a SAN, all costing a few megabucks</font>
</pre>
</blockquote>
--> <a href="http://en.wikipedia.org/wiki/Weasel_words">http://en.wikipedia.org/wiki/Weasel_words</a>
<blockquote type="CITE">
<pre><font color="#000000">;-)</font><br><br></pre>
</blockquote>
<br>
You get pretty decent off-the-shelf hardware for $500 (asus m2n, athlon x2 xx , 2GB RAM) + cost of storage space) per server.<br>
And considering not every deployment is a remote underelectrified mountain / desert / ... area, this should not be light heartedly dismissed.<br>
<br>
<blockquote type="CITE">
<pre><font color="#000000">cheers,</font><br><br><br><br><font color="#000000">m</font>
</pre>
</blockquote>
<br>
And I agree with Aaron Huslage that the nature of the AP is going to be another big hitter. But I really haven't seen the numbers on the budget yet. A decent (non-WRT54(...)) AP comes for $300 - 450 and is still worth considering.<br>
<br>
So long<br>
Stefan
�<br><br /><hr />Immer dabei! <a href='http://redirect.gimas.net/?cat=hmtl&n=M0804HMHandy&d=http://www.gowindowslive.com/minisites/mail/mobilemail.aspx?Locale=de-de' target='_new'>Holen Sie sich Ihre Mails aufs Handy!</a></body>
</html>