search for: triv_proxi

Displaying 5 results from an estimated 5 matches for "triv_proxi".

Did you mean: triv_proxy
2017 Jul 03
2
Can't use proxy after client upgrade
Hello, After upgrading my client system from Debian jessie to Debian stretch (which includes an update from tinc 1.0.24 to tinc 1.0.31), I am having trouble with my VPN: As long as I let tinc connect directly (no "Proxy" configuration option on the client), everything works fine: # tincd -n rath -D -d tincd 1.0.31 starting, debug level 1 /dev/net/tun is a Linux tun/tap device (tun
2017 Jul 29
3
Can't use proxy after client upgrade
On Jul 11 2017, Guus Sliepen <guus-NnCthlHDAqpg9hUCZPvPmw at public.gmane.org> wrote: > On Mon, Jul 03, 2017 at 02:24:55PM +0200, Nikolaus Rath wrote: > >> After upgrading my client system from Debian jessie to Debian stretch >> (which includes an update from tinc 1.0.24 to tinc 1.0.31), I am >> having trouble with my VPN: > [...] >> Proxy = exec
2017 Jul 11
0
Can't use proxy after client upgrade
On Mon, Jul 03, 2017 at 02:24:55PM +0200, Nikolaus Rath wrote: > After upgrading my client system from Debian jessie to Debian stretch > (which includes an update from tinc 1.0.24 to tinc 1.0.31), I am > having trouble with my VPN: [...] > Proxy = exec /etc/tinc/rath/triv_proxy.sh Indeed, it seems like Proxy = exec was broken by a commit that fixed some issue with the other proxy
2017 Jul 29
0
Can't use proxy after client upgrade
On Sat, Jul 29, 2017 at 12:47:02PM +0200, Nikolaus Rath wrote: > >> Proxy = exec /etc/tinc/rath/triv_proxy.sh > > > > Indeed, it seems like Proxy = exec was broken by a commit that fixed > > some issue with the other proxy types. For now the workaround is to use > > 1.0.29 or earlier if you need this. I'll let you know when this is > > fixed. > >
2017 Jul 30
1
Can't use proxy after client upgrade
On Jul 29 2017, Guus Sliepen <guus-NnCthlHDAqpg9hUCZPvPmw at public.gmane.org> wrote: > On Sat, Jul 29, 2017 at 12:47:02PM +0200, Nikolaus Rath wrote: > >> >> Proxy = exec /etc/tinc/rath/triv_proxy.sh >> > >> > Indeed, it seems like Proxy = exec was broken by a commit that fixed >> > some issue with the other proxy types. For now the workaround is