|
Bugzilla – Full Text Bug Listing |
| Summary: | KDE Connect cannot go through firewalld anymore | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Yunhe Guo <i> |
| Component: | KDE Workspace (Plasma) | Assignee: | E-Mail List <opensuse-kde-bugs> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | firewalld configuration | ||
Solved. I switched to a new WiFi and forgot to config its firewall zone in NetworkManager. |
Created attachment 871401 [details] firewalld configuration KDE Connect used to work smoothly with firewalld if I add the service to whitelist. However, after recent Tumbleweed updates, it cannot connect anymore unless I manually shutdown firewalld. I guess it might be that kdeconnect's ports changed while firewalld didn't update its service configuration.