https://bugs.kde.org/show_bug.cgi?id=464380
--- Comment #3 from Volker Krause <vkra...@kde.org> --- This is reported correctly as a wishlist item, thank you! We recently started work on making use of train onboard APIs, which includes watching whether there is a Wifi connection to a well-known access point (see https://invent.kde.org/libraries/kpublictransport/-/blob/master/src/onboard/data/accesspoints.json for the currently supported systems). Using the same information and evolving this to also look for those access points while not connected to any Wifi network is indeed a possibility down the line, or optionally even also handling the "login" procedure automatically. The Docker problem is a rather special case, not impossible to handle here, but might be better placed on the NM level, and generalized to warn about any kind of address conflict (FritzBox VPNs allow you to easily end up in similar scenarios for example, without Docker or DB being involved at all). -- You are receiving this mail because: You are watching all bug changes.
