Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Richard Bellamy <richard.bellamy@virgin.net>
To: netfilter@lists.netfilter.org
Subject: Re: Being selective about traffic and interfaces
Date: Wed, 10 Mar 2004 18:18:11 +0000	[thread overview]
Message-ID: <20040310181811.GB3003@virgin.net> (raw)
In-Reply-To: <20040308150758.GB16848@virgin.net>

Thanks to all who responded.

Unfortunatley I still cannot get this working.

Does anyone know if the ROUTE target works under 2.6?

Richard

On Mon, Mar 08, 2004 at 03:07:59PM +0000, Richard Bellamy wrote:
> Hi
> 
> 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.
> 
> The situation is this:
> 
> Router:							Laptop:
> 192.168.0.1 - tun0					192.168.0.2 - tun0
> 	|							|
> 10.44.10.1 - eth0					10.44.10.2 - eth0
> 	|							|
> 	---------------------------------------------------------
> 
> The default route on the laptop is set to 192.168.0.1 so all traffic is automatically sent encrypted. I need to be able to send everything but ssh down the vpn(with the possibility for https later on). I beleive that this would have to happen before routing took place. OpenVPN is on udp/5000.
> 
> I would be very grateful for any assistance.
> 
> Richard 
> 


      parent reply	other threads:[~2004-03-10 18:18 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
2004-03-09 11:46 ` Tarek W.
2004-03-09 15:25   ` Tarek W.
2004-03-10 18:18 ` Richard Bellamy [this message]

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=20040310181811.GB3003@virgin.net \
    --to=richard.bellamy@virgin.net \
    --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