On Mon, 27 Oct 2014, Dan Williams wrote:
> After reviewing the logs I think:
>
> cb94fe0a9e985647d0feb3637dabdeab56a650a1
> core: don't override external route metrics (bgo #738268)
>
> should fix this issue as well,
I built 0.9.10.0-3 with that commit included. It indeed seems to fix
the issu
After reviewing the logs I think:
cb94fe0a9e985647d0feb3637dabdeab56a650a1
core: don't override external route metrics (bgo #738268)
should fix this issue as well, since it actually doesn't just apply to
route metrics but also to addresses. The issue was that merging the
generated setting back i
On Mon, 27 Oct 2014, Michael Biebl wrote:
> Am 27.10.2014 um 15:27 schrieb Michael Biebl:
> > Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=739244
> >
> > Am 27.10.2014 um 15:18 schrieb Peter Palfrader:
> >> We discussed this briefly on IRC, and it might be caused by the connec
Am 27.10.2014 um 15:27 schrieb Michael Biebl:
> Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=739244
>
> Am 27.10.2014 um 15:18 schrieb Peter Palfrader:
>> We discussed this briefly on IRC, and it might be caused by the connection
>> assumption feature.
>
> Forwarded this upstr
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=739244
Am 27.10.2014 um 15:18 schrieb Peter Palfrader:
> We discussed this briefly on IRC, and it might be caused by the connection
> assumption feature.
Forwarded this upstream.
--
Why is it that all of the instruments seeking i
Package: network-manager
Version: 0.9.10.0-3
Severity: important
Hi,
I start a couple tun devices outside of network manager using openvpn.
For instance:
} 88: tun-n2-axon: mtu 1500 qdisc
pfifo_fast state UNKNOWN group default qlen 100
} link/none
} inet 172.22.126.18 peer 172.22.126.2
6 matches
Mail list logo
