Stuart McLachlan
stuart at lexacorp.com.pg
Sun Jun 12 08:26:19 CDT 2011
Yes, set up Router B in the church. Mask: Without going into the technicalities, a mask of 255.255.255.0 means that any machine with an IP address starting with the same three groups can see each other. So all 192.168.0.x machines can see each other and all 192.168.1.x machines can see each other. The tricky part is the 255.255.255.252 mask. That means than 192.168.0.2 can only see 192.168.0.1. It can't see any other 192.168.0.x address. So anything on 192.168.1.x which is routed through 192.168.1.1/192.168.0.2 can't see those other 192.168.0.x addresses. DHCP: The church people will be assigned a 192.168.1.x address by the DHCP server in the WAP/Router at that location. That WAP router will then route their internet requests to 192.168.0.1 which will in turn pass it on through it's own internet connection. (IP masks can be quite confusing but there are quite a few tutorials on the web which explain it in all of its gory details) -- Stuart On 12 Jun 2011 at 8:11, jwcolby wrote: > Stuart, > > Are you saying setup routerB down in the church and aim the cantenna > attached to RouterB back at the router up in the office which is on > the internet? > > I have never understood what the mask part does. > > The point of having the wireless down at the church is to allow the > "public", people who are at the church for classes, to get on the > internet. Don't they have to be assigned an IP address by the DHCP > server in order to talk to the router and thus out to the internet? > > John W. Colby > www.ColbyConsulting.com > > On 6/11/2011 5:44 PM, Stuart McLachlan wrote: > > Hi John, > > > > I've tried to send this to the list a couple of times, but it > > doesn't get through for some reason: > > > > > > > > Since they are out of range of each other, I would try: > > > > Router A > > DHCP on > > IP Address 192.168.0.1 > > IP Range 192.168.0.100- 150 > > Connect the cantenna to a LAN port on Router B > > > > Router B > > DHCP on > > IP Address 192.168.1.1 > > IP Range 192.168.1.100- 150 > > External IP Address 192.168.0.2 > > External Mask: 255.255.255.252 > > Connect the cantenna to the WAN port on Router B > > > > The Mask on Router B's external address should prevent anyone going > > through it from seeing anything other than 192.168.0.1 and > > 192.168.0.1 > > > > > > -- > > Stuart > > > > On 8 Jun 2011 at 9:09, jwcolby wrote: > > > >> A church that I do pro bono for has an internet connection which > >> currently is sent through a wireless router and shared in a simple > >> workgroup lan. They want to add a new lan segment which is > >> "public", i.e. can be used by classes they give, to get to the > >> internet, but they do not want those people to see or have access > >> to the existing LAN / computers. > >> > >> Am I correct that I can simply take two routers: > >> > >> RouterA attached to the cable modem. > >> RouterA is the DHCP Server. > >> RouterA is the "Public" network and its wireless interface serves > >> that part of the church. > >> > >> RouterB connects its WAN to one of the LAN ports. > >> RouterB DHCP Server is turned off > >> RouterB is the private network and it's wireless interface serves > >> that part of the church. > >> > >> The cable modem location is several hundred feet from the church > >> where the public network will be located. I will use a Cantenna to > >> beam the wireless down to the church. > >> > >> http://www.cantenna.com/ > >> > >> I am considering using a bridge to pick up the signal from the > >> Cantenna and retransmit the signal on another wifi channel. > >> > >> My parts list > >> > >> 1 existing router (wrt54g IIRC) > >> 2 new router (probably a wrt54g as well) > >> 1 (or possibly 2) Cantenna > >> > >> I am going to spend some time working with the system to see if I > >> need a bridge at the far end or whether the cantenna will allow > >> systems at the far end to see the internet directly through the > >> cantenna. I have no idea what the beam diameter will be a few > >> hundred yards away, but I suspect that a wireless bridge and > >> another wireless router at the far end will be required. > >> > >> If anyone has done this kind of system and has words of wisdom > >> please speak up. I will be setting this up soon. > >> > >> > >> -- > >> John W. Colby > >> www.ColbyConsulting.com > >> -- > >> AccessD mailing list > >> AccessD at databaseadvisors.com > >> http://databaseadvisors.com/mailman/listinfo/accessd > >> Website: http://www.databaseadvisors.com > >> > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >