https://bugs.kde.org/show_bug.cgi?id=414464
--- Comment #2 from daniel-other+kde...@dadosch.de --- (In reply to Bruce Anderson from comment #1) > (In reply to daniel-other+kdebug from comment #0) > > SUMMARY > > - default name contains spaces and thus results in cancellation when > > adding new VPN entry. (if name not changed) > > The default name will be changed to not include spaces. good, thank you. > > > > - entering a ipv6 ip in allowed ip text box leads to cancellation of > > editing the entry when trying to apply it, but ipv6 ip is a legal option in > > wireguard (for example 0.0.0.0, ::/0) > > I am unable to reproduce this problem, in fact I have used IPv6 in the > Allowed IPs in all the tests I have done. I notice that in the example > given, there is not a CIDR mask given on the IPv4 part though. It should > actually be: "0.0.0.0/0, ::/0" so this might be the problem. > > What is showing when you enter this string in the Allowed IPs field? That > field has an integrity check on it which should set the background color to > an error color (on mine it shows red but that is theme dependent) and the OK > button should be grayed out. Yes, I think I forgot the CIDR mask. However, if I try to add "0.0.0.0/0, ::/0" and then click apply and then ok, a notification comes up with wireguard.peers: Eigenschaft konnte nicht festgelegt werden: peer #1 has invalid allowed-ips setting which translates roughly to "Setting could not be set". > > So when you create a new WireGuard connection, you should see several fields > (Private Key in the initial window and Public Key and Allowed IPs in the > Peers window) should be highlighted with the error background and Save (or > OK on the Peer window) should be grayed out and as you enter a correct > value, the error background should go away and when all checked fields are > good, the Save button should become active. Is this what you are seeing? yes, I see this when I create a new wg connection. -- You are receiving this mail because: You are watching all bug changes.
