-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
A new snapshot, `0.0.20181006`, has been tagged in the git repository.
Please note that this snapshot is, like the rest of the project at this point
in time, experimental, and does not consitute a real release that would be
considered
On Fri, Oct 05, 2018 at 06:32:44PM +0200, Matthias Urlichs wrote:
On 05.10.18 17:53, Konstantin Ryabitsev wrote:
But should the admin need to bring up the OpenVPN link
This may be a stupid question, but why do you need OpenVPN any more, if
you have Wireguard?
Because it's already there? :)
Hey Konstantin,
On Fri, Oct 5, 2018 at 5:53 PM Konstantin Ryabitsev
wrote:
> > Any reason why you can't just do
> >
> > ip rule add dport 22 lookup 2468
>
> Yeah, this works, too, and is quite a bit simpler. Jason, any reason why
> I wouldn't use this?
Definitely use that. A reason for
On 05.10.18 17:53, Konstantin Ryabitsev wrote:
> But should the admin need to bring up the OpenVPN link
This may be a stupid question, but why do you need OpenVPN any more, if
you have Wireguard?
I'd set up a simple server-side login page that allows people to use
their user+pass+TOTP to enable
On Fri, Oct 05, 2018 at 12:03:04PM +0200, Toke Høiland-Jørgensen wrote:
> > When you're doing policy routing with packets that are being forwarded
> > by the system -- a router, for example -- then the prerouting table is
> > sufficient. But for locally generated packets, you have to use the
> >
On Fri, Oct 5, 2018, 12:03 Toke Høiland-Jørgensen wrote:
> "Jason A. Donenfeld" writes:
>
> > Hey Konstantin,
> >
> > When you're doing policy routing with packets that are being forwarded
> > by the system -- a router, for example -- then the prerouting table is
> > sufficient. But for locally
"Jason A. Donenfeld" writes:
> Hey Konstantin,
>
> When you're doing policy routing with packets that are being forwarded
> by the system -- a router, for example -- then the prerouting table is
> sufficient. But for locally generated packets, you have to use the
> OUTPUT table and also probably
