Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VPN configuration is not parsed correctly #192

Closed
jamtur01 opened this issue Aug 31, 2018 · 1 comment
Closed

VPN configuration is not parsed correctly #192

jamtur01 opened this issue Aug 31, 2018 · 1 comment

Comments

@jamtur01
Copy link

jamtur01 commented Aug 31, 2018

I have a VPN configured like so:

[global]
Name = PN

[provider_l2tp]
Type = L2TP
Name = EL2TP
Host = 1.2.3.4
Domain = vpn.com
Networks =
L2TP.User = xxxx
L2TP.Password = xxxx

The VPN details are not displayed in the Details and VPN pages.

screenshot_20180831_003428

screenshot_20180831_003437

P.S. The VPN Editor creates a configuration with & scattered in various places. I can log a separate issue for that.

This is on Ubuntu 18.04 / KDE PLasma 5.13 / cmst 2018.01.06-3 amd64 package.

@andrew-bibb
Copy link
Owner

The VPN information seems to displaying mostly correctly now. Exception is the VPN Provider area which will only fill in if you close CMST then restart. Connman is not sending that information with their PropertiesChanged signal (I've spent a good deal of time with a dbus inspector to verify that). I am still trying to determine if there is a different signal I have inadvertently failed to connect to, or if it is a bug in Connman.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants