Later that day, Yaesu posted a WiRES-X 2.0 webinar online, announcing and describing this significant software update. It’s an odd way to release information to a community of users (release it, publish update instructions, but don’t tell anyone until later) that feels like it was not well thought out or orchestrated.
The webinar video is about 45 minutes long, providing a thorough review of the major differences between the releases, including changes, limitations, and more. While I would have preferred to embed the video here as a convenience to you, Yaesu seems to have disabled embedding. Why? I have no idea. The link worked for a day and then the video was pulled and a replacement video was published. Note that it, too, won’t embed, so click the “Watch on YouTube” link to get to it. (Maybe this will have changed by the time RW 175 goes to press.)
A major change in WiRES-X 2.0 is it allows room owners to mute (or boot) individual users from the room. This desirable feature was requested by WiRES-X room owners.
An important consideration in deciding whether to update to version 2.0 is that the updated software requires IPv6 addressing. We’re all familiar with IPv4 addressing (you know, formats like 192.168.0.12). IPv6 is different and not all internet service providers (ISPs) provide IPv6 addresses to their customers. If you don’t have IPv6 and your ISP won’t provide it, don’t upgrade to WiRES-X 2.0, because it won’t work for you.
If you are running a WiRES-X system and are thinking about upgrading to 2.0, it will be worth your time to track down whether your ISP provides IPv6 addressing. The deployment is apparently not without other ssues. For example, KCWide (America's Kansas City Wide) has reverted to the 1.57 release of Wires-X due to problems in 2.0. Unfortunately, those who have updated their home Wires-X nodes to 2.0 will not be able to see KCWide. The only solution is to reinstall 1.57. (Note that these issues do not affect those connecting via YSF, DStar, DMR, etc.)
What does this mean? It means we haven’t heard the last of this update and what happens if you install it.
No comments:
Post a Comment