>
>
>
> Hi Tim,
>
> I don't think there is a bug there.
>
> The modify command modifies an existing connection.
>
> Note that the name is not a unique ID, maybe you had multiple
> connections with "System eth0" name?
>
> Note that a connection can be in-memory only. If you modify a
> connect
I just noticed that I inserted that "Ping started to work" after wrong
message chain. That must have been pretty confusing. I'm not worried about
OpenVPN at the moment. It seems working quite well now. As I told before,
problem was triggered uncompressing cert archive so that it produced
/etc/openv
2016-12-15 18:41 GMT+02:00 Dan Williams :
> > *route add default dev eth0 metric 99*
> > So, everything is fine!
>
> That implies that the default route was not set up correctly
> beforehand. What's the output of "ip route" before you add that
> default route?
>
Yes, there was no default route se
On Thu, 2016-12-15 at 15:14 +0200, matti kaasinen wrote:
> Ping started to work after executing command:
>
>
> *route add default dev eth0 metric 99*
> So, everything is fine!
That implies that the default route was not set up correctly
beforehand. What's the output of "ip route" before you add
Ping started to work after executing command:
*route add default dev eth0 metric 99*
So, everything is fine!
Cheers,
Matti
2016-12-13 11:37 GMT+02:00 matti kaasinen :
> Lubomir, Dan,
> I found what triggers this issue. I don't know what the reason is, though!
> It has nothing to do with Networ
Hi Dan,
Story below is kind of follow up of my late query referenced:
https://mail.gnome.org/archives/networkmanager-list/2016-April/msg00055.html
2016-12-14 16:36 GMT+02:00 matti kaasinen :
> I used to have NM 0.9.8.10 together with dhclient. Now I upgraded to NM
> 1.0.10 together with internal
