Upgrade to V5.15.8.12 - VPN Naming Issues (Caution)

dognose

3 weeks ago - last edited 2 weeks ago

Posts: 17

Helpful: 3

Solutions: 0

Stories: 0

Registered: 2022-03-24

Upgrade to V5.15.8.12 - VPN Naming Issues (Caution)

3 weeks ago - last edited 2 weeks ago

Tags: #Firmware Update #VPN #Controller

Model: OC200

Hardware Version: V1

Firmware Version: 1.0

When Upgrading the Omada-Firmware to V5.15.8.12, everyone should look at configured VPN Profiles, first.

Using a Hyphen ("-") in the Name is no longer supported after (at least) V5.15.8.12, so existing VPN Profiles using that
character then (apparently) fail to load and establish a connection after an successful upgrade.

(Becomes unhandy, when upgrading a remote side that is inaccessible without an established VPN Connection)

Ran into this issue on one side, renaming the profiles prior to upgrading on other sides avoided inaccessibility after the upgrade.

best,

dognose

1 Accepted Solution

Vincent-TP

2 weeks ago - last edited 2 weeks ago

Posts: 1624

Helpful: 191

Solutions: 656

Stories: 0

Registered: 2024-06-22

Re:Upgrade to V5.15.8.12 - VPN Naming Issues (Caution)-Solution

2 weeks ago - last edited 2 weeks ago

@dognose

Thank you for sharing this important information with the community! I appreciate your diligence in identifying and documenting this issue. It’s definitely something that others should be aware of before upgrading to V5.15.8.x.

Wish you a happy life and smooth network usage! >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<

Upgrade to V5.15.8.12 - VPN Naming Issues (Caution)

Upgrade to V5.15.8.12 - VPN Naming Issues (Caution)

Information

Voters 2

Tags