On my Beryl 7, I configured a VPN tunnel with two profiles.
Profile A is listed first, followed by Profile B. However, the VPN automatically connects to Profile B instead.
I thought there might be an issue with Profile A, so I created another tunnel with exactly the same configuration, with Profile A listed first and Profile B second. In this second tunnel, the VPN connects to Profile A as expected.
I don’t understand why the two tunnels behave differently. Could you please help me investigate this issue?
In firmware v4.9, the tunnel should try the profiles according to their priority and connect to Profile B only if Profile A fails to connect.
Could you please temporarily disable the second tunnel, reconnect the original tunnel, and share the profile order screenshot and its connection log with us?
Could you also check whether the original tunnel can use Profile B stably, while the other tunnel can use Profile A stably when they are tested separately? Do they consistently select the same profiles after reconnecting?
I changed the profile order, saved the configuration, and then restored it to the original order. It is working correctly now.
I’ll let you know if the problem occurs again.
I have one question, though: if Profile A becomes unavailable and the VPN switches to Profile B, will it remain on Profile B until I restart the VPN, or will Profile A be tested again automatically at regular intervals?
