From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Being selective about traffic and interfaces
Date: Mon, 8 Mar 2004 21:07:29 -0600 [thread overview]
Message-ID: <200403082107.29626.rob0@gmx.co.uk> (raw)
In-Reply-To: <20040308150758.GB16848@virgin.net>
On Monday 08 March 2004 09:07, Richard Bellamy wrote:
> I have just set up an ecrypted connection (with OpenVPN) between my
> laptop and router currently all traffic goes down the vpn. I would
> like to allow ssh traffic to bypass the vpn.
FWIW, if what you're seeking is a performance improvement, you would
probably do better by changing your sshd/ssh client to use something
faster than the default 3DES encryption. Blowfish (which of course is
openvpn's default) is a good choice: fast and not known to be weak.
> I would be very grateful for any assistance.
I am pretty sure that what you want can be done with MARK in the mangle
table and complex routing (iproute2). Unfortunately that's all a bit
beyond me. I hope the blowfish suggestion is helpful.
--
mail to this address is discarded unless "/dev/rob0"
or "not-spam" is in Subject: header
next prev parent reply other threads:[~2004-03-09 3:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 15:07 Being selective about traffic and interfaces Richard Bellamy
2004-03-09 3:07 ` /dev/rob0 [this message]
2004-03-09 11:46 ` Tarek W.
2004-03-09 15:25 ` Tarek W.
2004-03-10 18:18 ` Richard Bellamy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200403082107.29626.rob0@gmx.co.uk \
--to=rob0@gmx.co.uk \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox