From: Jose Luis Domingo Lopez <lartc@24x7linux.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Private Address Routing via Tunnels
Date: Tue, 03 Feb 2004 00:19:16 +0000 [thread overview]
Message-ID: <20040203001916.GB10578@localhost> (raw)
In-Reply-To: <20040201170938.GC87073@newred.gradwell.net>
On Monday, 02 February 2004, at 11:26:48 +0000,
Alan Ford wrote:
> They can route from the public to the private blocks, because they get to
> the router and the router knows to send it down the IPIP tunnel. But how
> can I configure the router at the other end to know to send responses
> from the private block to the public block down the tunnel? I think that's
> what I am needing to do here, does that make sense?
>
Traditional routing is always based solely on the destination IP address
of packages arriving at a router. With Linux policy routing you can
route based on both destination and source IP address, and based on more
parameters, for example, any parameter selectable via iptables.
The router on the other end already has a working routing table based on
both information from IP addresses for each interface and static routes
you should have added manually. If the router on the other end doesn't
know how to route packets back to the other router , then the routing
table on the distant router is not correct.
As the two internal networks are far away and connected by a tunnel
using public IP addressing, I guess what is missing in the remote router
is a route that sends traffic directed to the other private network
through the tunnel. Exactly the same you seem to have done on your
"local" router to make traffic directed to the remote LAN be
encapsulated through the IPIP tunnel.
Just for completeness, in this setup I don't think policy routing (based
on source IP addresses) is the correct way to handle the problem.
Greetings.
--
Jose Luis Domingo Lopez
Linux Registered User #189436 Debian Linux Sid (Linux 2.6.2-bk3)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-02-03 0:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 17:09 [LARTC] Private Address Routing via Tunnels Alan Ford
2004-02-01 22:10 ` Jose Luis Domingo Lopez
2004-02-02 11:26 ` Alan Ford
2004-02-03 0:19 ` Jose Luis Domingo Lopez [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=20040203001916.GB10578@localhost \
--to=lartc@24x7linux.com \
--cc=lartc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.