Comment 3 for bug 1878887

Hi,
When the system is clear installed Network Manager uses eap-ttls with mschapv2 login/password authentication and there are no problems, but when the system is upgraded from previous versions like 18.04 it tries peap by default and fails, so you need manually configure strongswan.conf with the following lines
charon-nm {
        load_modular = yes
        plugins {
                include strongswan.d/charon/*.conf
        eap-peap {
                load = no
                        }
}
As a result all my colleagues, who upgraded their systems, got VPN service broken.
I guess eap-peap as much useful as eap-ttls and there is no point to remove it to save like 1 KB of package size.