David Sommerseth, on Wed 10 Feb 2016 01:56:57 +0100, wrote:
> > 2 minutes after the client disconnected, which would probably be fine
> > enough for our use case.
>
> If you use --proto udp, then it can take up to --ping-reset $SEC to trigger
> (IIRC). You can use explicit-exit-notify to avoid th
On 09/02/16 13:45, Samuel Thibault wrote:
> Gert Doering, on Tue 09 Feb 2016 12:58:26 +0100, wrote:
>> On Tue, Feb 09, 2016 at 11:58:39AM +0100, Samuel Thibault wrote:
>>> I have tried putting
>>>
>>> iroute-ipv6 2a01:474:5:1100::/56
>>>
>>> in the ccd, but from the learn-address script the environ
Hello,
Gert Doering, on Tue 09 Feb 2016 10:28:21 +0100, wrote:
> Alternatively, using
> --learn-address might actually be much easier than --client-connect, as
> it will already tell you which networks are "new for this client" - from
> the description, I'm fairly sure it handles iroute/iroute-ipv
Gert Doering, on Tue 09 Feb 2016 12:58:26 +0100, wrote:
> On Tue, Feb 09, 2016 at 11:58:39AM +0100, Samuel Thibault wrote:
> > I have tried putting
> >
> > iroute-ipv6 2a01:474:5:1100::/56
> >
> > in the ccd, but from the learn-address script the environment does not
> > contain this route.
>
>
Hi,
On Tue, Feb 09, 2016 at 11:58:39AM +0100, Samuel Thibault wrote:
> I have tried putting
>
> iroute-ipv6 2a01:474:5:1100::/56
>
> in the ccd, but from the learn-address script the environment does not
> contain this route.
--learn-address cmd
Run command cmd to validate
Hi,
On Tue, Feb 09, 2016 at 11:55:44AM +0100, Jan Just Keijser wrote:
> > Could you test and report whether --learn-address does the job for you?
>
> a 'learn-address' script is an entirely different beast than a
> 'client-connect' script: you cannot write out new openvpn directives in
> a 'lear
Gert Doering, on Tue 09 Feb 2016 11:46:25 +0100, wrote:
> On Tue, Feb 09, 2016 at 11:15:33AM +0100, Samuel Thibault wrote:
> > Gert Doering, on Tue 09 Feb 2016 10:28:21 +0100, wrote:
> > > On Mon, Feb 08, 2016 at 10:39:29PM +0100, Samuel Thibault wrote:
> > > > Is there a reason for not being allow
Hi,
On 09/02/16 11:46, Gert Doering wrote:
On Tue, Feb 09, 2016 at 11:15:33AM +0100, Samuel Thibault wrote:
Gert Doering, on Tue 09 Feb 2016 10:28:21 +0100, wrote:
On Mon, Feb 08, 2016 at 10:39:29PM +0100, Samuel Thibault wrote:
Is there a reason for not being allowed to set route / route-ipv
Gert Doering, on Tue 09 Feb 2016 10:28:21 +0100, wrote:
> On Mon, Feb 08, 2016 at 10:39:29PM +0100, Samuel Thibault wrote:
> > Is there a reason for not being allowed to set route / route-ipv6
> > options in the ccd?
>
> "Nobody has implemented it yet" - plain and simple...
Ok :)
Samuel
Hi,
On Tue, Feb 09, 2016 at 11:15:33AM +0100, Samuel Thibault wrote:
> Gert Doering, on Tue 09 Feb 2016 10:28:21 +0100, wrote:
> > On Mon, Feb 08, 2016 at 10:39:29PM +0100, Samuel Thibault wrote:
> > > Is there a reason for not being allowed to set route / route-ipv6
> > > options in the ccd?
> >
Hi,
On Mon, Feb 08, 2016 at 10:39:29PM +0100, Samuel Thibault wrote:
> Is there a reason for not being allowed to set route / route-ipv6
> options in the ccd?
"Nobody has implemented it yet" - plain and simple...
So - someone would need to implement this (including route/route-ipv6
cleanup at c
Samuel Thibault, on Mon 08 Feb 2016 22:39:29 +0100, wrote:
> We could of course use the --up script to set the routes,
Oops, sorry, I didn't mean --up, but client-connect of course.
Samuel
Hello,
Is there a reason for not being allowed to set route / route-ipv6
options in the ccd?
Here is our need: we have two openvpn daemons running on the same
server, one in udp mode, the other in tcp mode. Both have the same
configuration, that setup is meant for our users to use whichever
happe
13 matches
Mail list logo
