> If NM changed in a way that breaks old plugins, it's a bug. We might
> introduce new behaviors, but old plugins should continue to work
> without modification. -- unless the plugin did something unsupported.
NM definitely changed - my plugin used to work, that's a fact. As to
unsupported things,
On Thu, 2017-04-20 at 17:40 +0300, Dan Fruehauf wrote:
> Thanks Thomas for the reply.
>
> I'm en route to fix the problems with NetworkManager-ssh, yet I'm not
> quite sure what it doesn't do right. Or in other words - what changed
> in nm that makes the whole thing not work properly.
>
> Previou
Thanks Thomas for the reply.
I'm en route to fix the problems with NetworkManager-ssh, yet I'm not quite
sure what it doesn't do right. Or in other words - what changed in nm that
makes the whole thing not work properly.
Previously it would use ifconfig to configure the interface after the VPN
is
On Tue, 2017-04-11 at 09:17 +1000, Dan Fruehauf wrote:
> G'day,
>
> I hope that post will not be long, but I've spent a few hours trying
> to narrow down the problem so I can provide as much information
> without wasting anyone's time.
>
> I started to debug why NetworkManager-ssh (which I mainta
G'day,
I hope that post will not be long, but I've spent a few hours trying to
narrow down the problem so I can provide as much information without
wasting anyone's time.
I started to debug why NetworkManager-ssh (which I maintain) does not allow
traffic through interfaces (tun interfaces usually
