Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Edmundo Carmona <eantoranz@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: Route packets from an interface to another
Date: Fri, 9 Sep 2005 16:35:33 -0400	[thread overview]
Message-ID: <65aa6af90509091335d964c45@mail.gmail.com> (raw)
In-Reply-To: <65aa6af905090913353e0d0150@mail.gmail.com>

Well.. routing in this case is not single point problem.... but both
points have to route correctly to make it "happen". You sure the other
machine is routing through the VPN tunnel when replying?

On 9/9/05, Jonathan <phonic@antisocial.nu> wrote:
> I have already set up routes exactly like that one. :-)
>
> The purpose is that I want to have a static IP on my home box. I have a
> /28 addressed on a box so I thought I could tunnel one of these addresses
> to my box home.
>
> And the problem; when I ping/ssh/whatever 192.121.234.213 from the /28-box
> (box1), the traffic goes through 10.1.0.1 to 10.1.0.2 and reaches my home
> box. But when I ping/ssh/whatever from outside the traffic goes to box1.
> That's why I think NATing the connections will solve the problem. But
> maybe I'm wrong?
>
> > IPTABLES? I think it's a routing problem, not a firewall one.
> >
> > ip route add 192.121.234.213 via 10.1.0.2
> > I think that would do the first part of your problem.
> >
> > But why do you have an IP address (not 127/8) set on a loopback interface?
> >
> > On 9/9/05, Jonathan <phonic@antisocial.nu> wrote:
> >> Hello,
> >> I have the following interface configuration on two boxes:
> >> box1: eth0:5 192.121.234.213 netmask 255.255.255.240 broadcast
> >> 192.121.234.223
> >> box2: lo:0 192.121.234.213 netmask 255.255.255.255
> >> between box1 and box2 I have a OpenVPN tunnel (endpoints 10.1.0.1 and
> >> 10.1.0.2).
> >>
> >> I want to forward all packages on box1 with destination 192.121.234.213
> >> to
> >> tun0 (10.1.0.1), so theWy pass through the tunnel and comes to box2. I
> >> also
> >> want to forward all packages from tun0 (10.1.0.1) to eth0:5
> >> (192.121.234.213). How do I do this with iptables?
> >>
> >> Regards
> >> Jonathan
> >>
> >>
> >>
> >
> >
>
>
>
>


  parent reply	other threads:[~2005-09-09 20:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09 19:15 Route packets from an interface to another Jonathan
2005-09-09 20:22 ` Edmundo Carmona
2005-09-09 19:32   ` Jonathan
     [not found]     ` <65aa6af905090913353e0d0150@mail.gmail.com>
2005-09-09 20:35       ` Edmundo Carmona [this message]
     [not found]       ` <1224.83.227.26.235.1126295454.squirrel@webmail.2lug.se>
2005-09-09 21:03         ` Edmundo Carmona
  -- strict thread matches above, loose matches on Subject: below --
2005-09-09 19:51 Jonathan
2005-09-09 21:36 ` /dev/rob0
2005-09-09 21:18   ` Jonathan
2005-09-10  4:45     ` /dev/rob0
2005-09-10  7:54       ` /dev/rob0
2005-09-12  7:56         ` Jonathan
2005-09-13  1:45           ` /dev/rob0
2005-09-12 13:36       ` Rudi Starcevic
2005-09-11 21:34         ` /dev/rob0
2005-09-12 14:47           ` Rudi Starcevic
2005-09-12 14:51           ` Rudi Starcevic
2007-09-10 12:18 vinod K D
2007-09-10 15:23 ` Grant Taylor

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=65aa6af90509091335d964c45@mail.gmail.com \
    --to=eantoranz@gmail.com \
    --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