<br><br><div class="gmail_quote">On Thu, Jul 2, 2009 at 12:19 AM, Andrew Fisk <span dir="ltr"><<a href="mailto:andy@spitcomp.com">andy@spitcomp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
How close are the buildings -- any chance you could get away with a<br>
couple of N routers and external antennas? If Google Maps are right<br>
you might even make it without the antennas.<br>
</blockquote></div><br>The one issue I can see with creating an internal network is that you are going to either need a unified address space in which case you probably want to drop FIOS from one site or use it as a backup internet connection because otherwise you are going to need a more advanced router to handle routing between locations. As this is a church they are unlikely to want to keep up the expertise on staff (paid) so a plug and play solution would just be better. A couple of the soho VPN routers that can be configured with a VPN tunnel will take care of deciding how to get the data from A to B. You just want to make sure that the two sites have unique address spaces so that it will know that 192.168.1 is building A and 192.168.2 is building B when connect to it. The single box will reestablish its' link as you tell it and reduce the number of times that you have to go down there to fiddle with the old 486 running package X.<br>
<br>Just make sure that whatever router you purchase is capable of handling the amount of traffic you are able to push over FIOS. many of the VPN routers have caps on the amount of bandwidth it can encrypt and it is usualy much lower than the line speed of the port. (even true for the PIX from Cisco) So even if it says it has a 10/100 port to connect to your modem it may only be able to handle 10 mb of traffic or 5mb of VPN traffic. Old DSL lines this was more than enough for but with Fios having options in the 25+ range you want to make sure you don't limit the solution just to save $20.<br>