Hi @dbungert, Sadly the company decided to move out from pulse secure usage, so I can't help anymore with tests. But I can give some insights.
The main issue is that AVAHI_DAEMON_DETECT_LOCAL set as 0 isn't avoiding avahi to change routes. It shouldn't happen. My patch isn't this direction and it is much more specific for the use case I had that time. My suggestion for long term solution instead is to just call `return` or `exit 0` once the AVAHI_DAEMON_DETECT_LOCAL value is 0. What do you think? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886809 Title: Pulse connect VPN exists because unwanted avahi network starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1886809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
