Lehi SSID

[jacobstimpson]

Is anyone aware if the lehi SSID has traffic shaping rules so it’s traffic is prioritized over Liahona?

Being that it is leaders only and no splash page it solves many issues while presenting a few new ones.

[russellhltn]

Not that has been revealed. Looking at the announcements, it appears the only advantage is to allow limited WiFi service while turning off Liahona.

Before, WiFi was all or nothing.

One of the usage cases was to allow the leadership of the 2nd ward to have WiFi while the 1st ward is streaming their sacrament meeting.

[drepouille]

Our STS has not yet installed a managed switch in our meetinghouse yet. So I don't know if Lehi magically appears when a managed switch is installed, or if that is totally unrelated. I know nothing about Lehi, since I've not seen it yet, and I have no idea how one connects to it and authenticates.

[Biggles]

The Lehi SSID is an additional SSID of the the existing AP’s. It is software controlled in the same way the Lehona is controlled. The STS is the only one who can enable it, done by adding a different password than used by the Lehona SSID. This password has a 90 day life before expiring. As long as the AP is correctly installed behind the managed switch the operation will be seemless.

[russellhltn]

From the webpage in TM:

The Lehi SSID is for local unit leaders only. The Lehi passphrase is set per meetinghouse, managed by the Stake Technology Specialist and must be changed every 90 days. The Lehi SSID will automatically be disabled if the passphrase expires.

The email sent to the STS indicates that the STS should only share the passphrase with leaders approved by the Stake President.

Previously, WiFi was "all or nothing". It was either on, with everyone knowing the access code, or completely off. Now there's an option for "chosen few".

With a per-building passphrase, and the requirement to change it every 90 days (it may be possible to change it more often - I haven't tried), that should keep the unauthorized spread down.

I'm not sure about it's relationship with managed switches. It could be a requirement. I'd think the MR33 access points would be more significant.

[lajackson]

(it may be possible to change it more often - I haven't tried)

You can change the Lehi passphrase any time you wish. You can also see how many days it has until it expires. You actually have to change it. You cannot reset the same passphrase.

A managed switch is not required. However, managed switches should be installed in all meetinghouses before the end of the year.

I have found it interesting that folks think Liahona and Lehi have nothing to do with the meetinghouse Internet bandwidth and so they should be left on all the time. This, of course, could not be further from the truth.

And if all three other bishops are running Zoom tithing settlement on Lehi while a ward is trying to Zoom sacrament meeting, there will be issues at the bandwidth with which I am provided.

[jacobstimpson]

Is anyone aware if the lehi SSID has traffic shaping rules so it’s traffic is prioritized over Liahona?

I'm interested to know what the "few new ones" issues are that you are experiencing?

We have not presently experienced any new issues.. However my expectation is that if all bishoprics from all wards and a zoom stream or 2 are going we could slaughter the internet..

So if hardwired has 1st priority and the laptop for zoom is hard wired at the podium... Solved
If 2nd priority is Lehi and so the bishopric in meetings etc can use the leftover bandwidth... Solved
If 3rd priority is Liahona so the ward can update tools and send ministering text messages....Solved

If it doesn't follow that order then I see people and systems getting frustrated

[russellhltn]

But not everyone is streaming using a hard-wired device.

And, I'm not sure how effectively the church can prioritize the traffic. They might be able to prioritize the upload, but I have doubts that they can prioritize the download - simply because they're at the narrow end of the bandwidth funnel.

[lajackson]

However my expectation is that if all bishoprics from all wards and a zoom stream or 2 are going we could slaughter the internet.

Currently, there are no traffic shaping or prioritization rules. There is only the option to turn off one or both of the WiFi networks.

Assuming bandwidth, a hardwire stream will work with minimal leader use (not Zoom meetings) by leaders over the Lehi WiFi. If the congregation overrides the bandwidth, Liahona goes away.

If hardwire is not available to stream, using Lehi for the stream allows turning off Liahona to give bandwidth to the webcast. Again, other leaders should not be Zooming.

Worst case, you turn off Liahona and you change the Lehi password, giving it only to the technologist who is streaming the sacrament meeting.

In an ideal world, the webcast can go hardwired or WiFi, and everyone else can play on Liahona and Lehi to their heart's content.

But we do not live in an ideal world at the moment.

[evancpugh]

Just a comment about allowing any traffic while another ward is streaming a sacrament meeting (YouTube Live). If they are using the other SSID (Lehi or Liahone) for streaming (e.g Zoom), it will definitely impact the Youtube Live (Sacrament meeting stream). @ 720 resolution which takes approx. 3 to 5 MBPS upload speed and @ 1080p 4 to 6 MBPS, the Zoom running on the Lehi WIFI would degrade the Youtube Live stream. I"m see a lot of buildings where they restrict any internet traffic when another ward's sacrament meeting is streaming. The issue isn't WIFI, it is internet traffic limitations! I'm guessing most building have an upload speed of around 5 to 5.5 MBPS.