WAP in YSA Ward Clerk's Office

Discussions about Internet service providers (ISPs), the Meetinghouse Firewall, wired and wireless networking, usage, management, and support of Meetinghouse Internet
Post Reply
dougj
Member
Posts: 79
Joined: Sun Jan 22, 2012 10:00 am
Location: Provo, UT, USA

WAP in YSA Ward Clerk's Office

#1

Post by dougj »

Hi, we have a YSA ward in the stake. Since before the days of 'ldsaccess' wireless access, they have had a wap in their clerk's office that that has its own SSID and gives out ip addresses. The YSA clerk computer even gets its ip address from this wap. The wap is connected to the Cisco 881 and goes thru the Church content filter, etc., so that isn't being bypassed.

We also have another building where we have left the old waps so leadership is guaranteed wireless access while members have been directed to use 'ldsaccess'. It, too, goes thru the Cisco 881.

What is the Church's policy regarding this situation? Is it ok or should the wap be disabled/removed and the clerk computer be configured to get an ip from the cisco 881?
russellhltn
Community Administrator
Posts: 34422
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Re: WAP in YSA Ward Clerk's Office

#2

Post by russellhltn »

dougj wrote:What is the Church's policy regarding this situation? Is it ok or should the wap be disabled/removed and the clerk computer be configured to get an ip from the cisco 881?
You didn't identify your self, so I'll assume that you are the Stake Technology Specialist. If you're not, then you need to work with him.

I don't know as there is a policy about the older WAPs from before the church started supplying equipment. So at this point they can be left or they can be removed. I'd suggest talking with the FM Group. If they have the budget, it would probably be best to replace the WAP with a 1041 just to bring your buildings into the current standard while there is money to do so.
Have you searched the Help Center? Try doing a Google search and adding "site:churchofjesuschrist.org/help" to the search criteria.

So we can better help you, please edit your Profile to include your general location.
dougj
Member
Posts: 79
Joined: Sun Jan 22, 2012 10:00 am
Location: Provo, UT, USA

Re: WAP in YSA Ward Clerk's Office

#3

Post by dougj »

Yes, I am the Stake Technology Specialist. Who are you and do you speak for the Church or is that your opinion?

There are already 1041s that cover that area and the 881 is configured with plenty of ip addresses.
russellhltn
Community Administrator
Posts: 34422
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Re: WAP in YSA Ward Clerk's Office

#4

Post by russellhltn »

I do not speak for the church, but I have a good working knowledge of what has been sent to the STS.

I looked around and found the following on clerksupport.lds.org:
Other Wireless Solutions

If other wireless access points are already set up in meetinghouses and working well, they may continue to be used at the discretion of the stake or district president and the facilities management group.
So at this point it looks like it's your call if you want to keep it to toss it. I suspect if you were to ask CHQ they'd say toss it - because they'd want everything to conform to their standard.
Have you searched the Help Center? Try doing a Google search and adding "site:churchofjesuschrist.org/help" to the search criteria.

So we can better help you, please edit your Profile to include your general location.
User avatar
Mikerowaved
Community Moderators
Posts: 4734
Joined: Sun Dec 23, 2007 12:56 am
Location: Layton, UT

Re: WAP in YSA Ward Clerk's Office

#5

Post by Mikerowaved »

dougj wrote:...they have had a wap in their clerk's office that that has its own SSID and gives out ip addresses.
Just for clarification, what you are describing is a wireless router.
dougj wrote:We also have another building where we have left the old waps so leadership is guaranteed wireless access while members have been directed to use 'ldsaccess'.
Are these actually WAP's or are they also routers?
dougj wrote:What is the Church's policy regarding this situation? Is it ok or should the wap be disabled/removed and the clerk computer be configured to get an ip from the cisco 881?
With the extra subnet(s) created by the routers, the church might not be able to accurately monitor user statistics; a small part of which is available to you at tm.lds.org. If it were me, I would either pull them, or turn the routers into dumb WAP's by disabling the DHCP and NAT functions, then aligning the SSID and login with the other WAP's in the building.
So we can better help you, please edit your Profile to include your general location.
john84601
New Member
Posts: 47
Joined: Sun Mar 11, 2012 2:24 pm

Re: WAP in YSA Ward Clerk's Office

#6

Post by john84601 »

I agree with Mikerwaved. The biggest problem is that you said the clerk computer was connected to this Wireless Router. There is a possibility that some functionality (in the form of software / antivirus updates, etc.) will not work because it's on a private subnet.

For me, the bigger picture is that there is no benefit. It "complicates" support for you (now you have to support multiple brands and instances, etc.). Consequently, I would pull it out and ask them to use LDSAccess. (Unless someone could convice of a really good reason to keep it).
chmsant
Member
Posts: 51
Joined: Mon Sep 19, 2011 12:00 pm
Location: Elk Grove, CA, USA

Re: WAP in YSA Ward Clerk's Office

#7

Post by chmsant »

This one has K.I.S.S written all over it. Unless there is a verifiable need, I'd toss it in favor of using the devices that have been provided by the Church.
ryanwbrown
Church Employee
Church Employee
Posts: 5
Joined: Mon May 06, 2013 10:14 am

Re: WAP in YSA Ward Clerk's Office

#8

Post by ryanwbrown »

Just want to reiterate what others have said about getting onto the church standards (in this case replacing all non-standard WAP’s with the 1041N’s) as quickly as possible. We don’t support out of spec hardware nor will it fully support all of the church systems and applications at some point. It is highly recommended, always, to remain within CHQ-ICS standards.
Post Reply

Return to “Meetinghouse Internet”