Hello again:)
I don't know why this would be needed, but I noticed this can be worked around
by pushing
the route towards the server-ipv6 subnet from the openvpn server, with the
directive:
push "route-ipv6 2001:bc8:3d1d:1337::/64"
I can totally live with that, but is it the expected
On Thu, 2021-05-27 at 21:40 +0300, Emmanuel Grumbach via
networkmanager-list wrote:
>
> Disclaimer: This feature is available only on vPRO Platforms.
>
> Question to the NM maintainers:
> Would you consider merging patches that would implement this?
Definitely. The most important property for
Note: sorry for the potential duplicate email, I sent it before & after having
registered
to the list!
Hello all,
I have a working openvpn config (see below) which I can't get to fully work
with Network
Manager: the private IPv6 network is not accessible when connecting to the VPN
with NM(*).
Hello all,
Please, make sure to CC me in your replies so I'm sure to get them!
I have a working openvpn config (see below) which I can't get to fully work
with Network
Manager: the private IPv6 network is not accessible when connecting to the VPN
with NM(*).
Here is what I get for tun0 when
Hi,
First of all, as always: enable level=TRACE logging and look at the
logs and have them ready for inspection. Read [1] for hints about
logging.
[1]
On Tue, Jun 1, 2021 at 8:26 PM Thomas Haller wrote:
>
> On Thu, 2021-05-27 at 21:40 +0300, Emmanuel Grumbach via
> networkmanager-list wrote:
> >
> > Disclaimer: This feature is available only on vPRO Platforms.
> >
> > Question to the NM maintainers:
> > Would you consider merging patches that
